PDA

View Full Version : Softsqueeze brought down my server?



coldslabs
2010-04-21, 18:27
This morning I started using softsqueeze for the first time connecting from work to my server at home. After a few minutes of listening, when I tried to pause the music, I lost the connection. When I got home my server was off but there was no apparent house-wide power cycle (my clock radio wasn't blinking).

I am running Ubuntu Server 9.04 and my /var/log/message file contained this line before the power off:
"Apr 21 08:39:10 music kernel: [1177207.654935] perl[9574]: segfault at 0 ip 08118e13 sp bfa76520 error 4 in perl[8048000+134000]"

Googling got me no where. Was this a softsqueeze issue or just a conincidence?

Squeezebox Server 7.5
Ubuntu 9.04
Softsqueeze 3.9 (I think, whichever one I would have downloaded today via the plugins interface)

snarlydwarf
2010-04-21, 19:40
I am running Ubuntu Server 9.04 and my /var/log/message file contained this line before the power off:
"Apr 21 08:39:10 music kernel: [1177207.654935] perl[9574]: segfault at 0 ip 08118e13 sp bfa76520 error 4 in perl[8048000+134000]"

Googling got me no where. Was this a softsqueeze issue or just a conincidence?

That's perl (which probably means SBS in your case) dying. A segfault is when a pointer starts pointing at things it shouldn't. It could be a bug in perl, it's HIGHLY unlikely to be a bug in SBS (since Perl itself handles the dirty work of dereferencing pointers and making sure you don't do bad things with them). But.. considering the shutdown of your system, I would actually guess it is something entirely different like a memory error.

(Back in the olden days, the correct answer to "why does gcc give me a segfault when I build the kernel?" was "because you have a memory error, replace your memory.")

Just as deliberately or accidentally setting a pointer to point where it shouldn't point... having a bit get stuck in RAM would have the same effect.) And a memory error may eventually take down your system if it corrupts kernel memory.

If you can deal without your computer for a few hours, try installing memtest86 to see if it finds something.

coldslabs
2010-04-21, 20:10
Thanks for the information and the suggestion. I'll give it a try.

epoch1970
2010-04-22, 00:41
I'd advise to broaden the search. On my machines, I often see a segfault message just when stopping the SBS service. (and I have no idea why.)
So it is possible the machine was shutting down for some reason, everything stops including SBS, which logged the message.