+- MinimServer Forum (https://forum.minimserver.com)
+-- Forum: MinimServer (/forumdisplay.php?fid=1)
+--- Forum: Support (/forumdisplay.php?fid=4)
+--- Thread: Minim server regular crash (/showthread.php?tid=7240)
Pages: 1 2
Minim server regular crash - TeeJayPee - 24-05-2024 09:22
MinimServer 2.2 update 250
Hello,
This is my first post.
I have Minim server 2.2 running on a fairly old QNAP NAS 410 running firmware 4.2.6,
firmware dated 2024/01/31.
Minim server suffered regular crashes during the night for a period, then the crashes stopped, I am not aware of any reason for the crashes nor why they stopped.
I saved the log files from last nights crash, the error is:
ERROR: Lock attempted on uninitialised mutex DSb2 from thread UpnpSession 3
ohNet fatal error: Unhandled exception AssertionFailed at OpenHome/Thread.cpp:90 in thread UpnpSession 3
Here is a list fo the crash files from this year, to give an idea of the frequency:
minimserver-crash-20240123-144922.log
minimserver-crash-20240131-091217.log
minimserver-crash-20240201-145904.log
minimserver-crash-20240202-152550.log
minimserver-crash-20240202-153049.log
minimserver-crash-20240202-153459.log
minimserver-crash-20240202-153553.log
minimserver-crash-20240202-154137.log
minimserver-crash-20240203-030612.log
minimserver-crash-20240204-030634.log
minimserver-crash-20240205-030534.log
minimserver-crash-20240206-010024.log
minimserver-crash-20240206-154219.log
minimserver-crash-20240206-155112.log
minimserver-crash-20240207-010020.log
minimserver-crash-20240209-103254.log
minimserver-crash-20240209-103430.log
minimserver-crash-20240214-010017.log
minimserver-crash-20240225-093938.log
minimserver-crash-20240428-010022.log
minimserver-crash-20240507-092803.log
minimserver-crash-20240520-010021.log
minimserver-crash-20240522-010019.log
Thanks and best regards,
Trevor
RE: Minim server regular crash - simoncn - 24-05-2024 10:52
Thanks for letting me know about this problem.
I notice that the last two crashes happened just after 01:00 am. Does your NAS restart automatically at this time or run some scheduled task? Does any other device on your network restart or run a scheduled task at this time?
Please attach the last crash file as a file attachment to a post here. Don't copy the text inline into a post. I will take a look at this to see if it provides any clues.
The crash is coming from the ohNet component used by MinimServer for UPnP network communications. It is likely that something on your network is triggering this ohNet problem. Because the crash isn't happening in MinimServer, it might be difficult for me to find the cause of the problem.
RE: Minim server regular crash - TeeJayPee - 25-05-2024 09:43
Hi Simon,
Thanks for the rapid response.
The last crash file is attatched.
The NAS does not have a scheduled restart, it runs constantly. Sometimes I restart it manually.
No other device on the network has a scheduled restart.
There is a Windows pc backup that runs each night at 01:00 except Saturday, the files are saved on the NAS to a separate Backup directory under /share, not to where the music files are nor where MinimServer is.
The backup is incremental each week day, differential on Sunday each week.
Both types take around one hour to complete, the pc is not heavily used so few changes.
The pc backup software is Macrium Reflect, a paid "profesional" product.
[attachment=3160]
Best regards,
Trevor
RE: Minim server regular crash - simoncn - 25-05-2024 20:39
Thanks for this log. The problem is not related to writing the files to the NAS disk but appears to be related to network communication between the PC and NAS when the backup is starting. Does Macrium Reflect install some software on the NAS as well as on the PC?
RE: Minim server regular crash - TeeJayPee - 25-05-2024 20:56
Thanks for the response.
No, Macrium does not do anything on the NAS during the backup, as far as I know.
I simply have to define the NAS IP and directory in Macrium.
I am not sure I am convinced that the backup is the cause, the MinimServer crashes are not always around 01:00, although several are.
Best regards,
Trevor
RE: Minim server regular crash - simoncn - 25-05-2024 22:19
Thanks for this. I will contact the ohNet developers and ask whether they have seen this problem or can suggest what might be causing it.
RE: Minim server regular crash - simoncn - 26-05-2024 07:26
If the PC is waking up at 01:00 to start the backup, it might be sending a message across the network that causes ohNet to crash. The other times (09:28, 09:39, 10:34, etc.) look as though they might correspond to when you are waking up the PC in the morning to start using it.
RE: Minim server regular crash - TeeJayPee - 26-05-2024 09:07
Thank you for the thought you are giving this, much appreciated.
The pc is not woken up every day to be used, it is not used for work, we are retired.
It can be woken up in the morning but I have no record of which days.
The music NAS and pc are in the spare bedroom, connected to the same switch. Also connected to the switch is a second NAS holding video files, so the second NAS has Twonky (UPnP) running.
Devolo home plugs provide the LAN connection to the room with a Linn streamer and a Panasonic tv.
It is a fairly “normal” home network, no regular tasks have been configured by us for e.g. work purposes.
The UPnP communication is via wired LAN, no wi-fi is involved; we do have wi-fi active for general use.
Does that detail help you?
Best regards,
Trevor
RE: Minim server regular crash - TeeJayPee - 26-05-2024 11:05
A couple more details that might help.
The whole network is on the same, self-defined sub-net, LAN and wi-fi; we do not use the delivered, pre-configured sub-net of the Internet router. There is a second router to manage our network.
Twonky is also running on the music NAS, being an OEM install on QNAP NAS.
RE: Minim server regular crash - simoncn - 26-05-2024 18:16
Thanks for this information. You didn't mention how the music NAS is connected to your router. This might be significant because UPnP multicast messages go via the router rather than directly from one device to another. If the router connection is via Devolo homeplugs, there is a possibility that the homeplugs might be doing something that is causing ohNet to produce this error.