PDA

View Full Version : Help! SlimServer appears to have totally crashed



max.spicer
2005-05-06, 13:47
I was listening to all my music on random when I decided to delete a track from the coming list by pressing add. At this point, the display on my SB2 froze and it stopped responding to any buttons on the remote. After several minutes, I had a look at the server and found that slimserver was using 99.9% of my cpu. I killed slimserver, at which point the sb2 immediately said that it was trying to connect to the server. I then restarted the server and it went straight back to 99%. The SB2 display went black and it didn't respond to anything. In addition, the web interface never returns - Firefox just sits there saying Connecting. I stopped and restarted the server, but just got the same. In desperation, I cleared out my cache directory (/var/cache/slimserver) and restarted the server, but I still get no response from the SB2 or the web interface. The cpu usage is now only 85%, but nothing else.

What do I do now??

SlimServer running on Debian Sarge. I'm running 6.0.x at Revision 3121. The SB2 is Firmware 11 and is a wireless model. My wireless network is absolutely fine - I can connect to the router's web interface and the slim forums from the same browser that I am trying to connect to the slimserver web interface.

max.spicer
2005-05-06, 13:53
Having left the server running and to its own devices for about ten minutes, the SB2 has just started playing and the web interface has returned. Is there some known issue with deleting tracks from a shuffled playlist with many items in? It surely shouldn't do what it did! Bizarrely, it's now playing a single album rather than the random shuffle, but that could be in response to some of the blind keypresses I did when it wasn't responding, I guess.

My library contains 4145 songs by the way, so we're not talking a crazy sized random shuffle by any means.

max.spicer
2005-05-06, 13:58
Woops, there it goes again. Whilst it was still playing the single album, I pressed shuffle once to turn off shuffle and then once again. At this point the display froze and the server is now back to 99.9%.

It's just come back very briefly and the display is now frozen saying Shuffle By Song.

kdf
2005-05-06, 13:58
wipe the __*.m3u files from your playlists folder

kdf
2005-05-06, 14:08
http://bugs.slimdevices.com/show_bug.cgi?id=1160

max.spicer
2005-05-06, 14:16
wipe the __*.m3u files from your playlists folder
Thanks, it's okay again now, but I'll be ready with that one if it happens again. Any idea what happened? I forgot that it created m3u's on the fly.

max.spicer
2005-05-06, 14:25
http://bugs.slimdevices.com/show_bug.cgi?id=1160
This sounds a bit like what happened, except that the main trigger seemed to be deleting a track from an already shuffled playlist. I didn't switch the shuffle mode in doing this and it only took a few seconds to do the initial shuffle.

kdf
2005-05-06, 14:26
large playlists hammer the db like crazy. server runs and hides.

max.spicer
2005-05-06, 14:33
large playlists hammer the db like crazy. server runs and hides.
But I've been playing my music on random via SoftSqueeze for a few weeks ago and have never had this happen before. It seems strange that it triggers the moment I use a real SB2 although correlation does not imply causality, as my old stats lecturer used to tell us repeatedly.

shaboyi
2005-05-15, 14:25
Hi - has this been addressed in any of the nightlies? one of the sb
owners i support reports that ss crashes any time he tries to save a
playlist of 100+ songs. thx.

On 5/6/05, kdf <slim-mail (AT) deane-freeman (DOT) com> wrote:
> large playlists hammer the db like crazy. server runs and hides.
>

kdf
2005-05-15, 14:52
Quoting Charles Stanton <shaboyi (AT) gmail (DOT) com>:

> Hi - has this been addressed in any of the nightlies? one of the sb
> owners i support reports that ss crashes any time he tries to save a
> playlist of 100+ songs. thx.
>
this was a known problem and should be fixed in the nightlies post 04/28. it
involved stale data in the current playlist.
http://bugs.slimdevices.com/show_bug.cgi?id=1266

-kdf

DrNic
2005-05-15, 16:40
large playlists hammer the db like crazy. server runs and hides.


Hang on a moment...
I thought the idea of developing the ss version 6 db backend was to enable large playlists without the old problem seen with the ver 5.x 's??
I really like the idea of being able to "shuffle" my entire library once in a while (admitedly this is smaller than most on here - around 2000 songs at present) especially when I am feeling lazy!!
Just as a reference - that bag'o'shite netgear MP101 thing can quite happily shuffle its whole library...

Nic

Dan Sully
2005-05-15, 16:53
* DrNic shaped the electrons to say...

>kdf Wrote:
>> large playlists hammer the db like crazy. server runs and hides.
>
>Hang on a moment...
>I thought the idea of developing the ss version 6 db backend was to
>enable large playlists without the old problem seen with the ver 5.x's??

Playlists themselves aren't stored in the database yet.

-D
--
There was supposed to be a big kaboom.

shaboyi
2005-05-15, 18:39
thanks. but is the fix in 6.0.x or 6.1? the bug report says its
target resolution is 6.1. i'll ask the customer to upgrade, but have
not recommended 6.1 yet.

On 5/15/05, kdf <slim-mail (AT) deane-freeman (DOT) com> wrote:
> Quoting Charles Stanton <shaboyi (AT) gmail (DOT) com>:
>
> > Hi - has this been addressed in any of the nightlies? one of the sb
> > owners i support reports that ss crashes any time he tries to save a
> > playlist of 100+ songs. thx.
> >
> this was a known problem and should be fixed in the nightlies post 04/28. it
> involved stale data in the current playlist.
> http://bugs.slimdevices.com/show_bug.cgi?id=1266
>
> -kdf
>

kdf
2005-05-15, 22:29
Quoting Charles Stanton <shaboyi (AT) gmail (DOT) com>:

> thanks. but is the fix in 6.0.x or 6.1? the bug report says its
> target resolution is 6.1. i'll ask the customer to upgrade, but have
> not recommended 6.1 yet.
>
you failed to read down to the bottom, in the comments:

patch committed to 6.1 builds: change 3100
patch committed to 6.0.x builds: change 3101

These were done April 28, thus are part of the nightly builds. The next
official release is likely not to be another 6.0.x so the choice is yours how
you want to support your customers.

-kdf