Synology DSM 4.2 is incompatible with MinimServer

[Rairwave]

I just did a reboot of the nas (without reinstalling or removing anything) and that helped. MinimServer is running again. Thanks!

In my situation 0.63.3 wasn't working anymore. I upgraded to DSM 4.2 before I saw this thread.

What I still see is that the Synology Package Center shows 'Stopped' as the status of MinimServer. But I checked with MinimWatch that it is indeed running. Will this wrong status information be solved in a future version?

[winxi]

(08-03-2013 10:02)Rairwave Wrote:  I've installed the 0.63.4 version but it gives this error message:

starting MinimServer
HTTPService: error creating server socket: Address already in use
MinimServer error: now stopped, use 'restart' or 'exit'

I had installed MinimServer 0.63.3 on DSM 4.1 and upgraded to DSM 4.2 with the new java manager.

Hi, this sounds like a known issue with the package center which is not specific to MinimServer. It has also been reported for other packages when they have been uninstalled and subsequently reinstalled and I also experienced it myself some time ago. For some reason, the package center 'thinks' that the required port is in use although it obiously isn't. For the reported related problems, the solution always was just to wait a few minutes and then the installation worked flawlessly.

[winxi]

(08-03-2013 10:40)Rairwave Wrote:  What I still see is that the Synology Package Center shows 'Stopped' as the status of MinimServer. But I checked with MinimWatch that it is indeed running. Will this wrong status information be solved in a future version?

This is quite unusal and may be related to the problem reported before which may have confused the package center.
Try pressing 'refresh' in the package center, also refresh the browser. If it still shows the wrong status for MinimServer, please completely uninstall Minimserver, reboot the NAS and reinstall MinimServer. Please report back if the problem persists. Thanks!

[simoncn]

(08-03-2013 14:46)winxi Wrote:  Hi, this sounds like a known issue with the package center which is not specific to MinimServer. It has also been reported for other packages when they have been uninstalled and subsequently reinstalled and I also experienced it myself some time ago. For some reason, the package center 'thinks' that the required port is in use although it obiously isn't. For the reported related problems, the solution always was just to wait a few minutes and then the installation worked flawlessly.

This message is from MinimServer, not from the package center. Perhaps the problem is that the package center is not stopping the previous instance of MinimServer before starting the new instance. This might be a timing issue with the package center not waiting for the stop to complete before initiating the start.

[Rairwave]

(08-03-2013 14:54)winxi Wrote:  Try pressing 'refresh' in the package center, also refresh the browser. If it still shows the wrong status for MinimServer, please completely uninstall Minimserver, reboot the NAS and reinstall MinimServer. Please report back if the problem persists. Thanks!

Refresh doesn't help.
I am willing to uninstall but don't want to reconfigure. Where can I find the configuration file as backup to restore after reinstall?

[Rairwave]

(08-03-2013 15:12)simoncn Wrote:  This message is from MinimServer, not from the package center. Perhaps the problem is that the package center is not stopping the previous instance of MinimServer before starting the new instance. This might be a timing issue with the package center not waiting for the stop to complete before initiating the start.

Another synology package had a similar problem. They changed the exit code from 1 to 0 for the status command in the start/stop/status script. Maybe that can help here as well?
Apparantly all the package center does is a status request call or command to the package, everytime the package center is opened. As MinimServer itself works fine I guess this should be that simple.

[simoncn]

(08-03-2013 16:17)Rairwave Wrote:  Refresh doesn't help.
I am willing to uninstall but don't want to reconfigure. Where can I find the configuration file as backup to restore after reinstall?

There should be an option to uninstall without deleting the configuration data. To be 100% safe, I recommend that you take a copy of the file /homes/minimserver/appData/minimserver.config before you do the uninstall.

[winxi]

(08-03-2013 16:24)simoncn Wrote:  

(08-03-2013 16:17)Rairwave Wrote:  Refresh doesn't help.
I am willing to uninstall but don't want to reconfigure. Where can I find the configuration file as backup to restore after reinstall?

There should be an option to uninstall without deleting the configuration data. To be 100% safe, I recommend that you take a copy of the file /homes/minimserver/appData/minimserver.config before you do the uninstall.

this option is only available when upgrading, not when uninstalling.

please do the following using the 0.63.4 package:
1) backup minimserver.config
2) uninstall minimserver
3) reboot the nas
4) install minimserver without the option to start it afterwards
5) restore minimserver.config
6) start/stop the package a few times and observe the status in the package center. also make use of the refresh button.

thanks!

[winxi]

(08-03-2013 16:23)Rairwave Wrote:  Another synology package had a similar problem. They changed the exit code from 1 to 0 for the status command in the start/stop/status script. Maybe that can help here as well?

Do you mean that Synology changed this to the opposite for DSM 4.2? This would be quite surprising. If so, please give some reference.

[Rairwave]

(08-03-2013 16:50)winxi Wrote:  

(08-03-2013 16:23)Rairwave Wrote:  Another synology package had a similar problem. They changed the exit code from 1 to 0 for the status command in the start/stop/status script. Maybe that can help here as well?

Do you mean that Synology changed this to the opposite for DSM 4.2? This would be quite surprising. If so, please give some reference.

Yes, the dependancy of the python package had similar issue going to DSM 4.2. See:
https://github.com/SynoCommunity/spksrc/issues/376
By changing the exit 1 to exit 0, the package center showed 'running', which allowed dependent packages to install. This wasn't happing in earlier version of DSM. Because MinimServer is running fine (only the reported status is wrong) I though about as a similar issue.