PDA

View Full Version : Lockup problem



Dave Horoschak
2005-03-30, 08:55
I've been having lockup problems since 6.0b2 and continue to have them
with the 6.0 release. On a Mandrake 9.0 dedicated (Samba) file server,
I installed SlimServer. Previously, the system had been up & running
with a problems for about 2 years. Now that I installed SlimServer, it
dsoesn't stay up for more than 24 hours. It locks up hard so that I
can't Telnet in, the webserver doesn't work, etc.

What's the best way of troubleshooting this problem? slimserver.log
doesn't have any data in it. After a reboot, everything seems to run
fine until it crashes again.

Indidentally, this occurs without any Slim clients ever connecting to
the server.

Any thoughts?
- Dave

Paul Wisneskey
2005-03-30, 09:18
Ditto for me too. Only I'm running on Windows XP (Service Pack 2) and
hadn't had enough time to devote to looking at the logs to make me feel
justified in complaining. But I did want to at least chime in with
another datapoint and if necessary, I can try to carve out some time to
run tests as long as the wife is not trying to listen to music at the time.

In my case, I have slimserver running as a service as a particular user
so that it can access my large music archive shared from NSLU2 with the
index information in Itunes on the PC the server is running on (a
dual-Xeon with 2 gigs of RAM). With the latest release, the server
would just stop responding at a random time during song playback. The
display on the client would be blank and the server would not serve up
web pages. I'd have to stop and restart the service to get things going
again.

Since I didn't have time to play with it, I rolled back to the 3/26
build which was the build I was using successfully before I upgraded to
the release version.

- Paul


Dave Horoschak wrote:
> I've been having lockup problems since 6.0b2 and continue to have them
> with the 6.0 release. On a Mandrake 9.0 dedicated (Samba) file server,
> I installed SlimServer. Previously, the system had been up & running
> with a problems for about 2 years. Now that I installed SlimServer, it
> dsoesn't stay up for more than 24 hours. It locks up hard so that I
> can't Telnet in, the webserver doesn't work, etc.
>
> What's the best way of troubleshooting this problem? slimserver.log
> doesn't have any data in it. After a reboot, everything seems to run
> fine until it crashes again.
>
> Indidentally, this occurs without any Slim clients ever connecting to
> the server.
>
> Any thoughts?
> - Dave

Jess Askey
2005-03-30, 13:43
Is your Linux box leaving any messages in /var/log?

My slimserver was crashing on my MDK 9.1 box during a rescan. I will try
letting it run without scanning to see if I have the same problems. In
my case however, I think it may be a hardware issue. But look in
/var/log/messages to see if slimserver posted anything strange. My
slimserver.log always empty unless I turn on debugging flags.

Dave Horoschak wrote:

> I've been having lockup problems since 6.0b2 and continue to have them
> with the 6.0 release. On a Mandrake 9.0 dedicated (Samba) file
> server, I installed SlimServer. Previously, the system had been up &
> running with a problems for about 2 years. Now that I installed
> SlimServer, it dsoesn't stay up for more than 24 hours. It locks up
> hard so that I can't Telnet in, the webserver doesn't work, etc.
>
> What's the best way of troubleshooting this problem? slimserver.log
> doesn't have any data in it. After a reboot, everything seems to run
> fine until it crashes again.
>
> Indidentally, this occurs without any Slim clients ever connecting to
> the server.
>
> Any thoughts?
> - Dave
>

Paul Wisneskey
2005-04-02, 06:41
FWIW, I just installed the latest nightly and my problems seem to have
disappeared. Though I did notice that every time I install a new
version I have to reset the login information on the service so that it
runs under my account (so that it can access the network share). I
doubt there is anything that can be done to fix this, but it might be
prudent to display a warning if the old service that is being removed
was set up with login information. This was definitely not the problem
I was having before - just something else I noticed during installation.

- Paul

Paul Wisneskey wrote:
> Ditto for me too. Only I'm running on Windows XP (Service Pack 2) and
> hadn't had enough time to devote to looking at the logs to make me feel
> justified in complaining. But I did want to at least chime in with
> another datapoint and if necessary, I can try to carve out some time to
> run tests as long as the wife is not trying to listen to music at the time.
>
> In my case, I have slimserver running as a service as a particular user
> so that it can access my large music archive shared from NSLU2 with the
> index information in Itunes on the PC the server is running on (a
> dual-Xeon with 2 gigs of RAM). With the latest release, the server
> would just stop responding at a random time during song playback. The
> display on the client would be blank and the server would not serve up
> web pages. I'd have to stop and restart the service to get things going
> again.
>
> Since I didn't have time to play with it, I rolled back to the 3/26
> build which was the build I was using successfully before I upgraded to
> the release version.
>
> - Paul
>
>
> Dave Horoschak wrote:
>
>> I've been having lockup problems since 6.0b2 and continue to have them
>> with the 6.0 release. On a Mandrake 9.0 dedicated (Samba) file
>> server, I installed SlimServer. Previously, the system had been up &
>> running with a problems for about 2 years. Now that I installed
>> SlimServer, it dsoesn't stay up for more than 24 hours. It locks up
>> hard so that I can't Telnet in, the webserver doesn't work, etc.
>>
>> What's the best way of troubleshooting this problem? slimserver.log
>> doesn't have any data in it. After a reboot, everything seems to run
>> fine until it crashes again.
>>
>> Indidentally, this occurs without any Slim clients ever connecting to
>> the server.
>>
>> Any thoughts?
>> - Dave