PDA

View Full Version : SlimServer Stop/Start Issue



Mike Reeve
2004-05-05, 08:07
Dean

Something that I have been meaning to mention for a while now ...

Normally I have SlimServer (always the latest nightly) start
when I boot my system (OS X 10.2.8)
but if I later stop SlimServer from System Preferences
I can't restart it from System Preferences
- I reboot the system to get it restarted.

Here are the contents of slimserver.log,
the boot-up start & the attempted restart ...

2004-05-05 10:55:56.8853 SlimServer OSDetect init...
2004-05-05 10:55:56.8855 SlimServer Strings init...
2004-05-05 10:55:57.0943 SlimServer OS Specific init...
2004-05-05 10:55:57.0952 SlimServer settings init...
2004-05-05 10:55:57.1494 SlimServer setting language...
2004-05-05 10:55:57.1498 SlimServer IR init...
2004-05-05 10:55:57.1954 SlimServer Buttons init...
2004-05-05 10:55:57.4776 SlimServer starting up...
2004-05-05 10:55:57.4778 SlimServer daemonizing...
2004-05-05 10:55:57.4867 SlimServer saving pid file.
2004-05-05 10:55:57.4884 Got to the END.
2004-05-05 10:55:57.4890 Got sigint.
2004-05-05 10:55:57.4892 SlimServer cleaning up.
2004-05-05 10:55:57.4890 Old SLIMP3 Protocol init...
2004-05-05 10:55:57.5031 Slimproto Init...
2004-05-05 10:55:57.5086 SlimServer Info init...
2004-05-05 10:55:57.5428 SlimServer HTTP init...
2004-05-05 10:55:57.5627 SlimServer CLI init...
2004-05-05 10:55:57.5956 SlimServer History load...
2004-05-05 10:55:57.6807 Source conversion init..
2004-05-05 10:55:57.7005 SlimServer Plugins init...
2004-05-05 10:55:57.7053 SlimServer persist playlists...
2004-05-05 10:55:57.7058 SlimServer iTunes init...
2004-05-05 10:56:03.0721 SlimServer done start...
2004-05-05 10:58:26.3540 Got sigterm.
2004-05-05 10:58:26.3543 SlimServer cleaning up.
2004-05-05 10:58:26.3583 Got to the END.
2004-05-05 10:58:26.3586 Got sigint.
2004-05-05 10:58:26.3588 SlimServer cleaning up.
2004-05-05 10:58:48.8519 SlimServer OSDetect init...
2004-05-05 10:58:48.8521 SlimServer Strings init...
2004-05-05 10:58:48.9982 SlimServer OS Specific init...
2004-05-05 10:58:48.9990 SlimServer settings init...
2004-05-05 10:58:49.0322 SlimServer setting language...
2004-05-05 10:58:49.0325 SlimServer IR init...
2004-05-05 10:58:49.0407 SlimServer Buttons init...
2004-05-05 10:58:49.1550 SlimServer starting up...
2004-05-05 10:58:49.1561 SlimServer daemonizing...
2004-05-05 10:58:49.1659 SlimServer saving pid file.
2004-05-05 10:58:49.1688 Got to the END.
2004-05-05 10:58:49.1692 Got sigint.
2004-05-05 10:58:49.1694 SlimServer cleaning up.
2004-05-05 10:58:49.1707 Old SLIMP3 Protocol init...
2004-05-05 10:58:49.1831 Slimproto Init...
2004-05-05 10:58:49.1883 SlimServer Info init...
2004-05-05 10:58:49.1996 SlimServer HTTP init...
can't setup the listening port 9000 for the HTTP server:
Address already in use at
/Library/PreferencePanes/SlimServer.prefPane/Contents/server/Slim/Web/HTTP.pm
line 149.
2004-05-05 10:58:49.2034 Got to the END.
2004-05-05 10:58:49.2037 Got sigint.
2004-05-05 10:58:49.2039 SlimServer cleaning up.

Regards

Mike

Mike Reeve
2004-05-05, 08:36
Mike Reeve <reeve_mike@...> writes:

> Normally I have SlimServer (always the latest nightly) start
> when I boot my system (OS X 10.2.8)
> but if I later stop SlimServer from System Preferences
> I can't restart it from System Preferences
> - I reboot the system to get it restarted.

And of course this problem occurs every morning when I update with
the latest nightly ...

Dave Nanian
2004-05-05, 08:51
Mike, it sounds like the server's running under a different user, and
can't be killed by the current one. I'd suggest turning off the startup
at boot with the combo, then turning it back on. Reboot, and see if
that solves the issue.

On May 5, 2004, at 11:07 AM, Mike Reeve wrote:

> Normally I have SlimServer (always the latest nightly) start
> when I boot my system (OS X 10.2.8)
> but if I later stop SlimServer from System Preferences
> I can't restart it from System Preferences
> - I reboot the system to get it restarted.
--
Dave Nanian

Mike Reeve
2004-05-05, 09:38
Dave Nanian <dnanian@...> writes:

>
> Mike, it sounds like the server's running under a different user, and
> can't be killed by the current one. I'd suggest turning off the startup
> at boot with the combo, then turning it back on. Reboot, and see if
> that solves the issue.

Dave

Thanks but this doesn't seem to be the issue
(1) SlimServer is definitely running under my userid
and (2) even if I do not start it at boot time
but start it manually later I still get the same problem.

Mike

dean
2004-05-05, 10:19
Hi Mike,

I can't reproduce this behavior on my 10.2.8 system here. I can start
and stop the SlimServer without problem.

After you stop it, can you use 'top' or the Process Viewer utility and
see if the perl slimserver process is running?

-dean

On May 5, 2004, at 9:38 AM, Mike Reeve wrote:

> Dave Nanian <dnanian@...> writes:
>
>>
>> Mike, it sounds like the server's running under a different user, and
>> can't be killed by the current one. I'd suggest turning off the
>> startup
>> at boot with the combo, then turning it back on. Reboot, and see if
>> that solves the issue.
>
> Dave
>
> Thanks but this doesn't seem to be the issue
> (1) SlimServer is definitely running under my userid
> and (2) even if I do not start it at boot time
> but start it manually later I still get the same problem.
>
> Mike
>
>
>

Mike Reeve
2004-05-05, 11:09
dean blackketter <dean@...> writes:

>
> Hi Mike,
>
> I can't reproduce this behavior on my 10.2.8 system here. I can start
> and stop the SlimServer without problem.
>
> After you stop it, can you use 'top' or the Process Viewer utility and
> see if the perl slimserver process is running?
>
> -dean

Dean

I had already looked at this,
the perl process disappears as soon as you hit Stop,
it reappears again when you hit Start but
then vanishes again within a second or so.

As I think I mentioned a couple of weeks ago,
the issue is bizarrely intermittent:
if you persist with pressing Start over and over again,
SlimServer eventually starts up OK and thereafter you can stop/start it at will
- WEIRD!

[I don't know whether it is related but there was an issue a while ago where
after installing a new nightly I would have to hit Start at least twice
before SlimServer would re-start - I think that some Linux users saw it also ...]

Mike

dean
2004-05-05, 11:21
Mike,

Do you have softsqueeze running or a MP3 streaming player connected?

From the log, it appears that the old process may be hanging around
waiting for the web server/streaming socket to close or something like
that.


On May 5, 2004, at 11:09 AM, Mike Reeve wrote:

> dean blackketter <dean@...> writes:
>
>>
>> Hi Mike,
>>
>> I can't reproduce this behavior on my 10.2.8 system here. I can start
>> and stop the SlimServer without problem.
>>
>> After you stop it, can you use 'top' or the Process Viewer utility and
>> see if the perl slimserver process is running?
>>
>> -dean
>
> Dean
>
> I had already looked at this,
> the perl process disappears as soon as you hit Stop,
> it reappears again when you hit Start but
> then vanishes again within a second or so.
>
> As I think I mentioned a couple of weeks ago,
> the issue is bizarrely intermittent:
> if you persist with pressing Start over and over again,
> SlimServer eventually starts up OK and thereafter you can stop/start
> it at will
> - WEIRD!
>
> [I don't know whether it is related but there was an issue a while ago
> where
> after installing a new nightly I would have to hit Start at least twice
> before SlimServer would re-start - I think that some Linux users saw
> it also ...]
>
> Mike
>
>
>

Mike Reeve
2004-05-05, 11:31
dean blackketter <dean@...> writes:

> Do you have softsqueeze running or a MP3 streaming player connected?
>
> From the log, it appears that the old process may be hanging around
> waiting for the web server/streaming socket to close or something like that.

Dean, Nothing but one [for now - there will be more :-)] SqueezeBox. Mike

Mike Reeve
2004-05-06, 15:59
> dean blackketter <dean@...> writes:
>
> I can't reproduce this behavior on my 10.2.8 system here. I can start
> and stop the SlimServer without problem.

More observations on the 'intermittent' nature of the 'bug' ...

(1) Reboot the system
(2) Start SlimServer from SystemPreferences (or have it start on boot),
all goes well
(3) Stop SlimServer
(4A) Immediately start SlimServer, it fails (as described in my original post)
(4B) Wait a minute or so before starting SlimServer, it succeeds

After this first-time-you-do-it-after-boot Start/Stop Issue
you can stop and then start SlimServer immediately without a problem
- BIZARRE!

This is probably why you could not reproduce it,
try it immediately after a boot ...

Mike