MinimServer and Simaudio Moon

[simoncn]

(20-07-2013 14:11)baconbrain Wrote:  Ok, left it with the address you specified and yes I have restarted the service from the Synology control panel a couple of times. (This time no error message as compared to yesterday!) Here the log file. Really appreciate the incredible amount of effort you are putting into this!!!!

This log file shows a huge number of extra directories being scanned. For example, at the start of the log:

Scanning directory 06 - Judas Priest - Night Crawler.mp3
14:15:36.301 main: no cache entry for folder 'Classic Rock/Judas Priest - Discography/(1990)(320kbps) Judas Priest - Painkiller/@eaDir/06 - Judas Priest - Night Crawler.mp3/'

What is the @eaDir directory? Why does this directory contain a subdirectory named '06 - Judas Priest - Night Crawler.mp3?' This looks like it should be the name of a file, not the name of a directory.

See this thread for some information on what causes this and some suggestions for how to remove these @eadir directories.

Regarding the main problem, there is no Browse request in the log. The log that you sent yesterday showed two Browse requests after the GetSortCapabilities request, but having looked at this log again I see now that the GetSortCapabilities request was sent from IP address 192.168.178.62 (presumably the iPad running MiND) and the Browse requests were both sent from IP address 192.168.178.23 (presumably some other control point such as the OPPO). Can you confirm this?

The missing Browse request from MiND gives me a strong clue about what is causing the problem. Please run another test by doing the following:

1) From the minim icon, restart MinimServer
2) Use MinimWatch to set the ohnet.debug property to the value All-Timer
3) From the MinimWatch log window, set the logging level to Debug
4) Restart the MiND app and browse to the top-level MinimServer container (once only)
5) Copy the minimserver.log file in the MinimServer 'data' directory to a new file minim1.log
6) From the log window, set the logging level back to Info
7) Zip the minim1.log file and attach it here

I'm very grateful for all your help with finding this problem. I think we are closing in on it now. It is looking likely to be a bug in the ohNet UPnP stack that MinimServer uses.