Synology

[simoncn]

(06-06-2013 21:42)mbovaird Wrote:  still no luck. The MiniWatch just hangs on "starting MinimServer" when I check the logs.

Please do the following:

1) From the MinimWatch minim icon, select 'Show log'
2) From the log window, change the logging level to Debug
3) Leave the log window open
4) From the minim icon, select 'Restart'

What do you see in the log window?

[mbovaird]

(06-06-2013 21:59)simoncn Wrote:  

(06-06-2013 21:42)mbovaird Wrote:  still no luck. The MiniWatch just hangs on "starting MinimServer" when I check the logs.

Please do the following:

1) From the MinimWatch minim icon, select 'Show log'
2) From the log window, change the logging level to Debug
3) Leave the log window open
4) From the minim icon, select 'Restart'

What do you see in the log window?

MinimServer 0.72, Copyright © 2012, 2013 Simon Nash. All rights reserved.
Platform default charset is UTF-8
starting MinimServer
13:33:12.352 Thread-9: Monitor response: SaveProperty
13:33:12.352 Thread-9: ErrorMsg=
13:33:28.443 Thread-12: Monitor action: StartContext
13:33:28.443 Thread-12: version=1, adapter=192.168.1.22, uriPrefix=http://192.168.1.22:35090/e52fc371-16ca-4c49-8dc3-6856b19634a2/Upnp/resource/, clientEndpoint=192.168.1.19:52966
13:33:28.443 Thread-12: ContextName=context0
13:33:28.444 Thread-12: Runtime: scheduling action: org.jminim.lib.MonitorService$MonitorProvider$1@4a5ab2
13:33:28.446 Thread-12: Monitor action complete: StartContext

[simoncn]

(06-06-2013 22:35)mbovaird Wrote:  MinimServer 0.72, Copyright © 2012, 2013 Simon Nash. All rights reserved.
Platform default charset is UTF-8
starting MinimServer
13:33:12.352 Thread-9: Monitor response: SaveProperty
13:33:12.352 Thread-9: ErrorMsg=
13:33:28.443 Thread-12: Monitor action: StartContext
13:33:28.443 Thread-12: version=1, adapter=192.168.1.22, uriPrefix=http://192.168.1.22:35090/e52fc371-16ca-4c49-8dc3-6856b19634a2/Upnp/resource/, clientEndpoint=192.168.1.19:52966
13:33:28.443 Thread-12: ContextName=context0
13:33:28.444 Thread-12: Runtime: scheduling action: org.jminim.lib.MonitorService$MonitorProvider$1@4a5ab2
13:33:28.446 Thread-12: Monitor action complete: StartContext

If this is the complete output, it doesn't look healthy. The MinimServer process appears to be deadlocked or hung.

Please do the following:

1) Leave the logging level set to Debug
2) Disable MinimServer from the Synology Package Center and re-enable it
3) When MinimServer restarts (the yellow icon appears in MinimWatch), use 'Show log' to open the log window
4) You should see quite a lot of debug output in the log window
5) When the debug output stops, click 'Save as' to save the log file
6) Zip the log file and post it here

Many thanks!

[mbovaird]

I cleared it and ran it again and....
14:11:49.570 Thread-9: Monitor action: SaveProperty
14:11:49.570 Thread-9: version=1, adapter=192.168.1.22, uriPrefix=http://192.168.1.22:35090/e52fc371-16ca-4c49-8dc3-6856b19634a2/Upnp/resource/, clientEndpoint=192.168.1.19:53349
14:11:49.570 Thread-9: ComponentName= PropertyName=logLevel PropertyValue=info
14:11:49.570 Thread-9: saveProperty: compName=null propName=logLevel propValue=info
14:11:54.242 Thread-8: Monitor response: SaveProperty
14:11:54.242 Thread-8: ErrorMsg=

[mbovaird]

(06-06-2013 23:19)mbovaird Wrote:  I cleared it and ran it again and....
14:11:49.570 Thread-9: Monitor action: SaveProperty
14:11:49.570 Thread-9: version=1, adapter=192.168.1.22, uriPrefix=http://192.168.1.22:35090/e52fc371-16ca-4c49-8dc3-6856b19634a2/Upnp/resource/, clientEndpoint=192.168.1.19:53349
14:11:49.570 Thread-9: ComponentName= PropertyName=logLevel PropertyValue=info
14:11:49.570 Thread-9: saveProperty: compName=null propName=logLevel propValue=info
14:11:54.242 Thread-8: Monitor response: SaveProperty
14:11:54.242 Thread-8: ErrorMsg=

Done. Please see attached.

[simoncn]

(06-06-2013 23:23)mbovaird Wrote:  Done. Please see attached.

Thanks for the quick response!

It looks like the content directory setting may be missing. If you select 'Properties' from the minim icon, what do you see in the contentDir field?

[mbovaird]

uhhh...blank. What should it be?

[mbovaird]

I tried to click something to bring up a list (like Windows Explorer) showing the various locations and drives and nothing worked. I'm not sure exactly how I should write the menu path.

[simoncn]

(07-06-2013 00:03)mbovaird Wrote:  I tried to click something to bring up a list (like Windows Explorer) showing the various locations and drives and nothing worked. I'm not sure exactly how I should write the menu path.

I will defer to winxi to answer this question. It shouldn't be possible for this field to be blank, because the MinimServer Synology installation package should inspect your disk volume configuration and insert a valid path.

We need to find out what went wrong with the installation process that allowed this to happen, and also find out why MinimServer is hanging during startup instead of producing an error message for this blank value.

Thanks for all your help with tracking down the problem!

[mbovaird]

(07-06-2013 00:24)simoncn Wrote:  

(07-06-2013 00:03)mbovaird Wrote:  I tried to click something to bring up a list (like Windows Explorer) showing the various locations and drives and nothing worked. I'm not sure exactly how I should write the menu path.

I will defer to winxi to answer this question. It shouldn't be possible for this field to be blank, because the MinimServer Synology installation package should inspect your disk volume configuration and insert a valid path.

We need to find out what went wrong with the installation process that allowed this to happen, and also find out why MinimServer is hanging during startup instead of producing an error message for this blank value.

Thanks for all your help with tracking down the problem!

Thank you guys!