Minim not accessible

[simoncn]

Thanks for clarifying this.

Somebody else had a problem like this when the router was rebooted. Is it possible that this (or something similar) has happened?

How long after starting MinimServer does the problem occur?

To debug this, I think I will need to send you a test build that produces additional diagnostic information when there is a forced kill. It will take me a day or two to do this.

[SoundAdikt]

It was me Simon (router reboot), this looks similar to the problem I am having. Minimserver only visible for a shortish period of time (usually no more than two hours) after which, it is not discoverable by any control points although the http status interface remains available as does the ability to play from MinimServer if a playlist is still listed on the control point.

SoundAdikt.

[simoncn]

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 | grep -v grep | 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!

Edit: updated step 2)

[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$

[simoncn]

(27-06-2016 14:10)SoundAdikt Wrote:  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$

I have an idea about what might have happened. For step 2, please do the following instead:

ps -ef | grep mserver | grep -v grep | tr -s " " | cut -f 2 -d " "

[Kochmeister]

OK I will gather the info.
In my case the time it takes before minim is "gone" can be like a day or 2, 3 of even a week.
I can not link it to any events yet (router reboot or actions on the NAS.).

I can try to force the situation by a router reboot.

[simoncn]

(28-06-2016 09:43)Kochmeister Wrote:  OK I will gather the info.
In my case the time it takes before minim is "gone" can be like a day or 2, 3 of even a week.
I can not link it to any events yet (router reboot or actions on the NAS.).

I can try to force the situation by a router reboot.

The router reboot scenario is very difficult to solve. It would be better to let the problem occur in normal usage and gather the information when it happens. Many thanks!

[SoundAdikt]

Quote:I have an idea about what might have happened. For step 2, please do the following instead:

ps -ef | grep mserver | grep -v grep | tr -s " " | cut -f 2 -d " "

Hi Simon, please find the attached. Thanks.

[simoncn]

(29-06-2016 08:21)SoundAdikt Wrote:  Hi Simon, please find the attached. Thanks.

Thanks! This looks like the partial crash of ohNet that we have discussed previously. Was it caused by a router reboot?

[SoundAdikt]

(29-06-2016 10:59)simoncn Wrote:  

(29-06-2016 08:21)SoundAdikt Wrote:  Hi Simon, please find the attached. Thanks.

Thanks! This looks like the partial crash of ohNet that we have discussed previously. Was it caused by a router reboot?

No, I've stopped my router doing this, as far as I am aware, it just happens without any external elements.