MinimServer starts then stops

[simoncn]

(03-11-2023 08:54)Andrea Wrote:  I don't have any error messages. I will try to install DSM 7.2 maybe I will get some improvements

Your earlier post said you have the same problem. As you don't have these messages, it seems your problem is caused by something different. What exactly do you see when you try to start MinimServer?

[Andrea]

(03-11-2023 12:09)simoncn Wrote:  

(03-11-2023 08:54)Andrea Wrote:  I don't have any error messages. I will try to install DSM 7.2 maybe I will get some improvements

Your earlier post said you have the same problem. As you don't have these messages, it seems your problem is caused by something different. What exactly do you see when you try to start MinimServer?

The "same problem" refers to the fact that minimserver crashes but i don't have any error message; the Synology log says "minim server manually stopped"

[simoncn]

Have you checked the minimserver.log and minimserver-out.log files in the MinimServer/appData shared folder to see if there are any messages there?

[Andrea]

(03-11-2023 18:24)simoncn Wrote:  Have you checked the minimserver.log and minimserver-out.log files in the MinimServer/appData shared folder to see if there are any messages there?

I send you the last miniserver.log but since I installed the minimiserver update 244 now it works regularly

[simoncn]

This crash log file is very old (4th September) and the error in the file wouldn't cause MinimServer to stop, so it isn't related to the problem you were having recently.

If you see the startup problem again, please save the minimserver.log and minimserver-out.log files (before trying to restart MinimServer) so that I can investigate further.

The error in the crash log file is caused by the control point having out of date information about the MinimServer library and attempting to browse the library using this information. It isn't really a crash and it shouldn't create a crash log file. I will change this in the next MinimServer update.

[Andrea]

(08-11-2023 19:52)simoncn Wrote:  This crash log file is very old (4th September) and the error in the file wouldn't cause MinimServer to stop, so it isn't related to the problem you were having recently.

If you see the startup problem again, please save the minimserver.log and minimserver-out.log files (before trying to restart MinimServer) so that I can investigate further.

The error in the crash log file is caused by the control point having out of date information about the MinimServer library and attempting to browse the library using this information. It isn't really a crash and it shouldn't create a crash log file. I will change this in the next MinimServer update.

The minimserver.log is 2.2GB !!!

[simoncn]

This is because you are running MinimServer with the logging level set to Trace. You should be running with this set to Info. The Trace and Debug logging levels should be used only when you have been asked to produce a log with one of these settings.

[Andrea]

(09-11-2023 12:14)simoncn Wrote:  This is because you are running MinimServer with the logging level set to Trace. You should be running with this set to Info. The Trace and Debug logging levels should be used only when you have been asked to produce a log with one of these settings.

Now the problem is coming back....
I send the minimserver-out.log (set to Trace)
Is it a Java error ?

[simoncn]

This isn't a Java error. The message is coming from ohNet (the UPnP networking stack used by MinimServer). It looks like the MinimServer process has exceeded the maximum number of file descriptors supported on Synology DSM. Are you doing something either in MinimServer or in some other application on your NAS that might be using a lot of file descriptors?

Edit: If you are still running MinimServer with Trace enabled all the time, try removing this setting to see if it helps.