Minimserver manually stops

[nigelpsmith]

I recently moved back to the UK from abroad and my Synology DS214play was in storage for 6 months or so. Today, I started up my NAS and updated the operating system. Now I found that Minim Server starts and then stops after a few seconds. Others have described similar symptoms in other threads, but nothing I read there helped me fix this.

I did a complete reinstall of Minim Server, but that made no difference. I am running the latest version of DSM and minimserver.

In the Log Center no errors are flagged up (that I can see). Strangely, the last Info message in the Log Center says "System successfully started [MinimServer]" whereas the penultimate Info message says "System successfully stopped [MinimServer]". Shouldn't these order of these be swapped?

What should I do next?

[simoncn]

If you use Synology DSM File Station to view the MinimServer/appData folder after MinimServer has stopped unexpectedly, what do you see in the minimserver.log and mminimserver-out.log files?

[nigelpsmith]

(09-08-2024 10:28)simoncn Wrote:  If you use Synology DSM File Station to view the MinimServer/appData folder after MinimServer has stopped unexpectedly, what do you see in the minimserver.log and mminimserver-out.log files?

I don't see any of those files. All I see is what's in the attachment.

[simoncn]

The screenshot shows no appData folder, which means the MinimServer app did not start.

What version of DSM do you currently have installed? Also, did you reinstall MinimServer from the DSM Package Center or by doing a manual download from the MinimServer Downloads page?

[simoncn]

There is a posible solution for this problem described in this post and subsequent discussion on the thread. As described on the thread, you might be able to work around the "manually stopped" error by installing MinimServer on a different volume.

Thre was a fix for this problem in MinimServer 2.0.18-2004 (released on 30th October 2021). Perhaps the fix is not working correctly in your situation for some reason.

Please let me know whether installing MinimServer on a different volume solved the problem. Also, please confirm which version of DSM you are running.

[nigelpsmith]

(11-08-2024 16:16)simoncn Wrote:  The screenshot shows no appData folder, which means the MinimServer app did not start.

What version of DSM do you currently have installed? Also, did you reinstall MinimServer from the DSM Package Center or by doing a manual download from the MinimServer Downloads page?

I am running DSM 7.1.1-42962, which I believe is the latest version and I installed Minim from the package centre.

If I remember correctly, Minim worked fine the first time I powered up my NAS after the six months' storage. The current problem appears to have occurred only after I updated DSM.

[nigelpsmith]

(12-08-2024 08:18)nigelpsmith Wrote:  

(11-08-2024 16:16)simoncn Wrote:  The screenshot shows no appData folder, which means the MinimServer app did not start.

What version of DSM do you currently have installed? Also, did you reinstall MinimServer from the DSM Package Center or by doing a manual download from the MinimServer Downloads page?

I am running DSM 7.1.1-42962, which I believe is the latest version and I installed Minim from the package centre.

If I remember correctly, Minim worked fine the first time I powered up my NAS after the six months' storage. The current problem appears to have occurred only after I updated DSM.

I just tried a manual install over the top of the existing install and there was no difference. Later today I'll try to install Minim on a different volume.

[simoncn]

(12-08-2024 08:18)nigelpsmith Wrote:  I am running DSM 7.1.1-42962, which I believe is the latest version and I installed Minim from the package centre.

If I remember correctly, Minim worked fine the first time I powered up my NAS after the six months' storage. The current problem appears to have occurred only after I updated DSM.

Thanks for this very helpful information. What version of DSM were you running when MinimServer started correctly the first time? Was it DSM 6 or a previous version of DSM 7?

Also, would you be able to login to the NAS using a Terminal window (ssh, putty) and run some diagnostic commands from there?

[nigelpsmith]

(12-08-2024 09:24)simoncn Wrote:  

(12-08-2024 08:18)nigelpsmith Wrote:  I am running DSM 7.1.1-42962, which I believe is the latest version and I installed Minim from the package centre.

If I remember correctly, Minim worked fine the first time I powered up my NAS after the six months' storage. The current problem appears to have occurred only after I updated DSM.

Thanks for this very helpful information. What version of DSM were you running when MinimServer started correctly the first time? Was it DSM 6 or a previous version of DSM 7?

Also, would you be able to login to the NAS using a Terminal window (ssh, putty) and run some diagnostic commands from there?

I don't know if I was running DSM 6 or 7 before the upgrade - as I said, the NAS was in storage for 6 months, which is quite a long time ago. Also, I wasn't paying close attention last year because everything worked.

I should be able to run some diagnostic commands for you, however I'm not a software expert, so the procedures will need to be fairly simple for me to follow.

[simoncn]

The first step is to enable SSH connections on your NAS. To do this, select Control Panel in DSM and then select Terminal & SNMP and enable the SSH service.

After this, do the following if you have a Windows PC:

1) Download the putty program
2) Open a command prompt window
3) Use putty to login to the NAS with a connection type of SSH (you need to know the IP address of your NAS)
4) Enter your Synology username and password
5) Type this command exactly as shown:
tail -n 30 /var/log/packages/MinimServer.log
6) Post the output from this command here

If you have a Mac or a Linux PC, do the following:
1) Open a Terminal window
2) Type this command: ssh x.x.x.x (where x.x.x.x is the IP address of your NAS)
3) Continue from step 4) above

The output from the tail command should provide information about what is causing the problem.