+- MinimServer Forum (https://forum.minimserver.com)
+-- Forum: MinimServer (/forumdisplay.php?fid=1)
+--- Forum: Support (/forumdisplay.php?fid=4)
+--- Thread: minimserver 2.2 update 247 crashed (/showthread.php?tid=7197)
minimserver 2.2 update 247 crashed - tarnkappe - 15-03-2024 19:07
Hello Simon,
MinimServer 2.2 update 247 on Synology NAS DS418play crashed some days ago when browsing the folder view via the lumin app. Maybe it had to do with waking up the NAS hard discs from stand by? I cannot find a crash log file. The only thing that looks interesting is the last line in the minimserver-out.log that I copied away before restarting minimserver:
java: Os/Posix/Os.c:1225: CreateHandle: Assertion `aSocket >= 0 && aSocket < MAX_FILE_DESCRIPTOR' failed.
But I do not know if this leads to a crash?
The last 2 entries in the minimserver.log were:
Browse request from 192.168.178.53: incorrect format for container ID ''
Browse request from 192.168.178.53: incorrect format for container ID ''
I guess this is not of great help and I cannot find more information somewhere regarding the crash reason? (On restart the minimserver update 248 came in.)
RE: minimserver 2.2 update 247 crashed - simoncn - 15-03-2024 23:39
This MAX_FILE_DESCRIPTOR message has been reported previously (see this post). Are you doing something regularly that could be causing MinimServer to open a large number of network connections or files?
The other message 'incorrect format for container ID' is caused by the control point sending an incorrect Browse or Search request to MinimServer.
RE: minimserver 2.2 update 247 crashed - tarnkappe - 17-03-2024 15:05
(15-03-2024 23:39)simoncn Wrote: Are you doing something regularly that could be causing MinimServer to open a large number of network connections or files?
I do not have an idea what this could be. I am using the NAS as file server (NFS and SMB) and for minimserver. Also backups are written each night to another synology NAS via Hyperbackup. And I am using the replication manager for writing snapshots.
docker and mail server packages are installed but not running currently. Audio and Video Station are running but currently not used.
In the moment when it did crash, the lumin app was waiting for the covers of all artist sub folder in one genre folder. Maybe this did open many network connections?
Is there a synology command to check open network connections? "lsof" seems to not being installed.
RE: minimserver 2.2 update 247 crashed - simoncn - 17-03-2024 18:59
A MinimServer debug log would show how many connections the LUMIN app is opening. If you could repeat what you were doing and capture a debug log, I will look at it and tell you what I find. Please zip the log file and post it as a forum attachment, not as inline text.
RE: minimserver 2.2 update 247 crashed - tarnkappe - 17-03-2024 19:09
I think it will be hard to reproduce it. But if I find a way, I will answer back.
RE: minimserver 2.2 update 247 crashed - simoncn - 17-03-2024 22:55
It is not necesary to reproduce the crash, just to enable debug logging and repeat what you were doing before the crash (the lumin app was waiting for the covers of all artist sub folder in one genre folder).
RE: minimserver 2.2 update 247 crashed - tarnkappe - 14-04-2024 16:19
After nearly a month it did stop again:
MinimServer 2.2 update 248, Copyright © 2012-2024 Simon Nash. All rights reserved.
MinimStreamer 2.0.12, Copyright © 2012-2023 Simon Nash. All rights reserved.
starting MinimServer[troken]
MinimServer[troken] is running
restarting MinimServer[troken]
starting MinimServer[troken]
MinimServer[troken] is running
restarting MinimServer[troken]
starting MinimServer[troken]
MinimServer[troken] is running
java: Os/Posix/Os.c:1225: CreateHandle: Assertion `aSocket >= 0 && aSocket < MAX_FILE_DESCRIPTOR' failed.
Will it be a problem somehow (because of big log files, deactivated standby, etc.?) if I enable debug logging and I have to wait 4 weeks again until the next crash?
Since the last crash nothing did change. I only updated the minimserver license for the next 12 months.
I do not know what I did that could have led to the max-file-descriptor-problem...
RE: minimserver 2.2 update 247 crashed - simoncn - 14-04-2024 22:03
When this happened previously, the LUMIN app was waiting for the covers of all artist sub folder in one genre folder. Were you doing something similar when the crash happened this time? If so, it is likely that the LUMIN app is opening too many network connections and exceeding the Linux limit of 1024 connections.
RE: minimserver 2.2 update 247 crashed - tarnkappe - 15-04-2024 18:52
The only thing that I remember is that I had to wait for minimserver to respond because the NAS was sleeping in standby and the discs had to spin up. So maybe the problem is related to the standby situation somehow?
Do you know a command to list all opened files on synology similar to the linux command "lsof"?
Otherwise it probably is the best if I try to activate the debug logging and hope for a soon crash again. I now did set the ".loglevel" property from "info" to "Debug" in the web frontend. I hope this is the correct setting.
RE: minimserver 2.2 update 247 crashed - tarnkappe - 15-04-2024 18:55
btw. the the first letter of the values for the property in the manual https://minimserver.com/ug-running.html#MinimServer%20logging are written in upper case. The web frontend only seems to accept a lower case "debug".