Waversa Mini Nas

[geekuix]

(01-12-2016 21:12)simoncn Wrote:  This means that MinimServer has identified your version of Linux as supporting System V init and has configured System V init to start MinimServer. For more information on System V init, see this page.

There are two possibilities:

1) MinimServer is starting but the startup is failing for some reason. You can check this by looking at the files minimserver/data/minimserver-out.log and minimserver/data/minimserver.log to see if there are any startup error messages.

2) MinimServer is not starting because your NAS doesn't fully support System V init. You would need to contact the NAS manufacturer to ask about this.

It seems like i have trouble with java:

root@W-MINI-NAS:~# cat java/minimserver/data/minimserver-out.log
/home/root/java/minimserver/bin/startd: line 184: exec: java: not found

[simoncn]

(02-12-2016 03:45)geekuix Wrote:  It seems like i have trouble with java:

root@W-MINI-NAS:~# cat java/minimserver/data/minimserver-out.log
/home/root/java/minimserver/bin/startd: line 184: exec: java: not found

You need to have the java executable on your PATH when the system starts. The usual way to do this is to create a symbolic link to the java executable as /usr/local/bin/java or /usr/bin/java. Alternatively, you can create a file named minimstart.conf in the minimserver/etc directory containing the full path to where you have installed java, in the following format:

java = /full/path/to/where/you/have/installed/java

[geekuix]

Do i need to add something for minimstart.conf on the minimserver script?

[simoncn]

(02-12-2016 10:58)geekuix Wrote:  Do i need to add something for minimstart.conf on the minimserver script?

No, just do what I said.

[geekuix]

Thank you Simon, i've found the problem. The update-rc.d was not updated properly so i've launched the command:
# update-rc.d minimserver defaults
Now minimserver start at boot as root privilege.

Thank you very much for your help.

Best regards,
Geekuix

[simoncn]

I don't understand why this would make a difference. The minimserver/bin/setup command runs the "update-rc.d minimserver defaults" command when you enable automatic startup. If you have run minimserver/bin/setup as the root user, MinimServer would have been started with root privilege. It seems that automatic startup was already working because you were seeing MinimServer starting up but not finding java on the PATH.

[geekuix]

(02-12-2016 12:42)simoncn Wrote:  I don't understand why this would make a difference. The minimserver/bin/setup command runs the "update-rc.d minimserver defaults" command when you enable automatic startup. If you have run minimserver/bin/setup as the root user, MinimServer would have been started with root privilege. It seems that automatic startup was already working because you were seeing MinimServer starting up but not finding java on the PATH.

It seems not working here, so i did it manually.

[simoncn]

(02-12-2016 14:32)geekuix Wrote:  It seems not working here, so i did it manually.

You were getting a startup error message in minimserver-out.log and this could not have happened if the update-rc.d setup had not been done. In any case, I am pleased you have found a solution.