+- MinimServer Forum (https://forum.minimserver.com)
+-- Forum: MinimServer (/forumdisplay.php?fid=1)
+--- Forum: Support (/forumdisplay.php?fid=4)
+--- Thread: minimserver did crash (/showthread.php?tid=2551)
minimserver did crash - tarnkappe - 12-07-2015 11:58
Just for the notes as it only happened once yet and I do not have hope to find the reason for this easily:
When listening to some music, it suddenly did stop and minimserver was gone. From the log:
MinimServer 0.8.3 update 66, Copyright © 2012-2015 Simon Nash. All rights reserved.
MinimStreamer 0.5.13, Copyright © 2012-2015 Simon Nash. All rights reserved.
Java™ SE Embedded Runtime Environment (build 1.8.0-b132)
Java HotSpot™ Embedded Client VM (build 25.0-b70, mixed mode)
Platform default charset is UTF-8
Language setting is 'ger'
...
MinimServer[JO] is running
ohNet fatal error: Unhandled exception AssertionFailed at OpenHome/Timer.cpp:253 in thread TimerManager
- end of file -
It is running on a Synology DS213+.
Music Renderer: naim uniti 1.
Control: naim app.
RE: minimserver did crash - simoncn - 12-07-2015 19:29
(12-07-2015 11:58)tarnkappe Wrote: Just for the notes as it only happened once yet and I do not have hope to find the reason for this easily:
When listening to some music, it suddenly did stop and minimserver was gone. From the log:
MinimServer 0.8.3 update 66, Copyright © 2012-2015 Simon Nash. All rights reserved.
MinimStreamer 0.5.13, Copyright © 2012-2015 Simon Nash. All rights reserved.
Java™ SE Embedded Runtime Environment (build 1.8.0-b132)
Java HotSpot™ Embedded Client VM (build 25.0-b70, mixed mode)
Platform default charset is UTF-8
Language setting is 'ger'
...
MinimServer[JO] is running
ohNet fatal error: Unhandled exception AssertionFailed at OpenHome/Timer.cpp:253 in thread TimerManager
- end of file -
It is running on a Synology DS213+.
Music Renderer: naim uniti 1.
Control: naim app.
This is the same problem that you reported in this post. It is a problem in ohNet and it would be necessary to have an ohNet debug log (as described in this post) to investigate it further.
It would be very helpful if you could run MinimServer with ohNet debug logging enabled and save the ohNet debug log if this happens again.
RE: minimserver did crash - tarnkappe - 12-07-2015 20:47
Oops, you are right. I had in mind that I had a minimserver crash before, but a quick search did not find this thread.
The last crash was at the end of january. So if it only occurs every half year, it is not that big show stopper. The problem is when activating the ohnet-Log my DS will never go to sleep (as I found when checking out the IGMP problematic). But on the other hand I would be very interested in getting this crash fixed and glad if I could help on this.
Maybe I activate the log anyway and start the server manually before listening to music and stopping it afterwards. So the DS can enter standby, IGMP on startup should be no problem, and if the error happens again, I had a log file. The question is if the crash happens with a freshly started minimserver, too.
btw. regarding the start up time: It seems that minimserver checks all files again that had a scan error on last scan (e.g. wrong date formats in meta fields, etc.) even if the file's timestamp did not change. All these errors are reported on every server start. Shouldn't minimserver only check added and modified files?
RE: minimserver did crash - tarnkappe - 12-07-2015 21:25
I do not have set the ohnet.debug property to something special?
RE: minimserver did crash - simoncn - 12-07-2015 21:27
(12-07-2015 20:47)tarnkappe Wrote: Oops, you are right. I had in mind that I had a minimserver crash before, but a quick search did not find this thread.
The last crash was at the end of january. So if it only occurs every half year, it is not that big show stopper. The problem is when activating the ohnet-Log my DS will never go to sleep (as I found when checking out the IGMP problematic). But on the other hand I would be very interested in getting this crash fixed and glad if I could help on this.
Maybe I activate the log anyway and start the server manually before listening to music and stopping it afterwards. So the DS can enter standby, IGMP on startup should be no problem, and if the error happens again, I had a log file. The question is if the crash happens with a freshly started minimserver, too.
You could do this or you could wait to see how often you get this crash in the future. If it starts to happen more frequently, perhaps it would make sense to capture log files for a few days.
Quote:btw. regarding the start up time: It seems that minimserver checks all files again that had a scan error on last scan (e.g. wrong date formats in meta fields, etc.) even if the file's timestamp did not change. All these errors are reported on every server start. Shouldn't minimserver only check added and modified files?
This is by design. If MinimServer didn't do this, the user would not be aware of library errors and warnings if he/she didn't see the log output from the first scan of the faulty file(s).
RE: minimserver did crash - simoncn - 12-07-2015 21:28
(12-07-2015 21:25)tarnkappe Wrote: I do not have set the ohnet.debug property to something special?
See this post for the required setting of ohnet.debug.