MinimServer and Simaudio Moon

[baconbrain]

(19-07-2013 16:59)baconbrain Wrote:  simoncn,

I have changed the ohnet subnet property field as described and it did not change the behaviour. Moving between the different views in the app brings inconsistent results. Sometimes I see the results of the query for the next sublevel and sometimes it is just blank. Also the navigation is erradic. Sometimes it just jumps all the way back to the top level although I just want to back up one. I have attached the log file for your reference. Hope you see something which is reflecting the cause of the problem. Thx, BB

Update: I have tested accessing the Minim Server via a PC based Foobar control point and it works without a glitch. Speed is very high and all views are populated. An indication for me that the problem lies more with the interaction between the moon app and server ...

[simoncn]

(19-07-2013 16:59)baconbrain Wrote:  simoncn,

I have changed the ohnet subnet prperty field as described and it did not change the behaviour. Moving between the different views in the app brings inconsistent results. Sometimes I see the results of the query for the next sublevel and sometimes it is just blank. Also the navigation is erradic. Sometimes it just jumps all the way back to the top level although I just want to back up one. I have attached the log file for your reference. Hope you see something which is reflecting the cause of the problem. Thx, BB

The attached zip file is corrupt. Please attach the correct file.

Please restart MinimServer from the Synology Package Center and confirm the value of ohnet.subnet. What do you see for this value?

What is the subnet value and netmask for the audio devices on your LAN?

Do you have both of the Synology LAN ports connected, or just one of them? What IP addresses do these ports have?

[baconbrain]

(19-07-2013 21:56)simoncn Wrote:  

(19-07-2013 16:59)baconbrain Wrote:  simoncn,

I have changed the ohnet subnet prperty field as described and it did not change the behaviour. Moving between the different views in the app brings inconsistent results. Sometimes I see the results of the query for the next sublevel and sometimes it is just blank. Also the navigation is erradic. Sometimes it just jumps all the way back to the top level although I just want to back up one. I have attached the log file for your reference. Hope you see something which is reflecting the cause of the problem. Thx, BB

The attached zip file is corrupt. Please attach the correct file.

Please restart MinimServer from the Synology Package Center and confirm the value of ohnet.subnet. What do you see for this value?

What is the subnet value and netmask for the audio devices on your LAN?

Do you have both of the Synology LAN ports connected, or just one of them? What IP addresses do these ports have?

Ok, I started Minimwatch this morning and the first message it gave me was that subnet 10.0.1.0 was not found ... This was the value that I plugged into the field ohnet subnet in the advanced properties yesterday. Yes, I have a bond configued in the Network Settings of the DS412+ using both Ethernet ports with the subnet 255.255.255.0 and an ip address of 192.168.178.xx. All of my devices are using the same subnet. I have reattached the log from yesterday, hopefully you can now open it. Thx, BB

  Minim Watch Log File 190713 Bacon.zip (Size: 937 bytes / Downloads: 2)

[simoncn]

(20-07-2013 08:38)baconbrain Wrote:  Ok, I started Minimwatch this morning and the first message it gave me was that subnet 10.0.1.0 was not found ... This was the value that I plugged into the field ohnet subnet in the advanced properties yesterday. Yes, I have a bond configued in the Network Settings of the DS412+ using both Ethernet ports with the subnet 255.255.255.0 and an ip address of 192.168.178.xx. All of my devices are using the same subnet. I have reattached the log from yesterday, hopefully you can now open it. Thx, BB

You need to change the ohnet.subnet setting to 192.168.178.0. This should resolve the problems you are having.

I can view the log file now. I think I did something wrong when opening it the previous time. The log tells me that MinimServer has the IP address 192.168.178.20. When the LAN ports are bonded, does this mean that only this single IP address is used by both LAN ports?

[simoncn]

(20-07-2013 08:38)baconbrain Wrote:  Yes, I have a bond configued in the Network Settings of the DS412+ using both Ethernet ports with the subnet 255.255.255.0 and an ip address of 192.168.178.xx.

Did you enable LACP before creating the bond (as described in this post)? I'm not sure whether setting ohnet.subnet will help if the LAN ports are bonded. If this doesn't help, please try enabling LACP if you haven't already done so.

Update 1: Do you have the link aggregation mode set to 'IEEE 802.3ad Dynamic Link Aggregation' or 'Network Fault Tolerance only'?

Update 2: I found some more information about Synology link aggregation on this page. What type of switch are you using?

[baconbrain]

(20-07-2013 09:00)simoncn Wrote:  

(20-07-2013 08:38)baconbrain Wrote:  Ok, I started Minimwatch this morning and the first message it gave me was that subnet 10.0.1.0 was not found ... This was the value that I plugged into the field ohnet subnet in the advanced properties yesterday. Yes, I have a bond configued in the Network Settings of the DS412+ using both Ethernet ports with the subnet 255.255.255.0 and an ip address of 192.168.178.xx. All of my devices are using the same subnet. I have reattached the log from yesterday, hopefully you can now open it. Thx, BB

You need to change the ohnet.subnet setting to 192.168.178.0. This should resolve the problems you are having.

I can view the log file now. I think I did something wrong when opening it the previous time. The log tells me that MinimServer has the IP address 192.168.178.20. When the LAN ports are bonded, does this mean that only this single IP address is used by both LAN ports?

Yes, when bonded both ports have the same address. I made the change you recommended but the result is still the same. The Server is visable in the app but after accessing I see no results in the app browser window. Btw. accessing the Minim Server via my Oppo Player also works without a problem. Could it be that I need to enter the gateway address instead of the one you referenced? The Link Aggregation Setting is 'Network Fault Tolerance only' as my switch (TP-Link) does not Support IEEE Dynamic Link Aggregation.

[simoncn]

(20-07-2013 12:59)baconbrain Wrote:  Yes, when bonded both ports have the same address. I made the change you recommended but the result is still the same. The Server is visable in the app but after accessing I see no results in the app browser window. Btw. accessing the Minim Server via my Oppo Player also works without a problem. Could it be that I need to enter the gateway address instead of the one you referenced? The Link Aggregation Setting is 'Network Fault Tolerance only' as my switch (TP-Link) does not Support IEEE Dynamic Link Aggregation.

You should use the subnet address that I gave you, not the gateway address.

Did you restart MinimServer from the Synology control panel after making the latest ohnet.subnet property change? This is important. If you have done this, please create a debug log as follows:

1) From the MinimWatch log window, set the logging level to Debug
2) From the minim icon, restart MinimServer
3) From the log window, set the logging level to Trace
4) Restart the MiND app and browse to the top-level MinimServer container (once only)
5) From the log window, click "Save as" to save the log
6) From the log window, set the logging level back to Info
7) Zip the log file and attach it here

While you are doing this, please avoid accessing MinimServer from any other client devices such as the OPPO.

Many thanks!

[baconbrain]

(20-07-2013 13:56)simoncn Wrote:  You should use the subnet address that I gave you, not the gateway address.

Did you restart MinimServer from the Synology control panel after making the latest ohnet.subnet property change? This is important. If you have done this, please create a debug log as follows:

1) From the MinimWatch log window, set the logging level to Debug
2) From the minim icon, restart MinimServer
3) From the log window, set the logging level to Trace
4) Restart the MiND app and browse to the top-level MinimServer container (once only)
5) From the log window, click "Save as" to save the log
6) From the log window, set the logging level back to Info
7) Zip the log file and attach it here

While you are doing this, please avoid accessing MinimServer from any other client devices such as the OPPO.

Many thanks!

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!!!!

[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.

[baconbrain]

(20-07-2013 16:55)simoncn Wrote:  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.

OK. The 23 IP address is the Ipad and the 62 is the mind unit itself. Sorry about the clutter at the beginning of the log but I still have not quite finished cleaning up my library ..... Followed your instructions and have attached the log file. Should I Change the ohnet.debug property back to its Default Setting? (Can't remember so maybe you can give me a hint ...)
Thx.