Minim not accessible

[SoundAdikt]

(27-06-2016 11:53)simoncn Wrote:  Please do the following after the problem occurs and before trying to stop MinimServer with a forced kill.

1) Login to the NAS using SSH

2) Run the command:
ps -ef | grep mserver | head -1 | tr -s " " | cut -f 2 -d " "

3) This wil display the process ID (PID) of the MinimServer process

4) Run the command:
sudo kill -quit PID
where PID is the output from step 2. (Note: This produces a Java thread dump. It does not kill or quit MinimServer.)

5) When prompted, enter your login password

6) Use File Station to view the appData/minimserver-out.log file. This should contain a thread dump.

7) Post the minimserver-out.log file here as a file attachment (not inline text)

Many thanks!

Confused.com - it finds the process but then claims it does not kill it, but then appears as a different process. Nothing gets sent to the log file either...

admin@nas:~$ cd /volume1/MinimServer/appData/
admin@nas:/volume1/MinimServer/appData$ ps -ef | grep mserver | head -1 | tr -s " " | cut -f 2 -d " "
9037
admin@nas:/volume1/MinimServer/appData$ sudo kill -quit 9037
Password:
kill: sending signal to 9037 failed: No such process
admin@nas:/volume1/MinimServer/appData$ ps -ef | grep mserver | head -1 | tr -s " " | cut -f 2 -d " "
9134
admin@nas:/volume1/MinimServer/appData$ sudo kill -quit 9134
kill: sending signal to 9134 failed: No such process
admin@nas:/volume1/MinimServer/appData$ cat minimserver-out.log
MinimServer 0.8.4 update 88, Copyright © 2012-2016 Simon Nash. All rights reserved.
starting Music Server
Enter command (? for help):
Music Server is running
>admin@nas:/volume1/MinimServer/appData$