PDA

View Full Version : Slimserver segmentation fault



Jason Rimmer
2004-08-08, 09:13
I've recently installed Slimserver v5.3b1 on a RedHat Fedora Core 2
Linux machine for a new Squeezeboxen that's on the way. Everything
works fine until I scan my music collection where upon I get a
'segmentation fault'. While I don't see anything too helpful the last
few entries of the '--d_scan' log are...

2004-08-08 02:52:31.8754 directory entry:
file:///mnt/music/music/808%20State/Don%20Solaris/Mooz.mp3
2004-08-08 02:52:31.8772 adding 14 to playlist cache:
file:///mnt/music/music/808%20State/Don%20Solaris
2004-08-08 02:52:31.8784 Descending into
file:///mnt/music/music/808%20State/Don%20Solaris, contains 14 items
2004-08-08 02:52:31.8797 numitems: 126
2004-08-08 02:52:31.8806 index: 0
2004-08-08 02:52:31.8825 itempath: 808 state-Don Solaris.m3u and
file:///mnt/music/music/808%20State/Don%20Solaris made
file:///mnt/music/music/808%20State/Don%20Solaris/808%20state-Don%20Solaris.m3u
2004-08-08 02:52:31.8848
isList(file:///mnt/music/music/808%20State/Don%20Solaris/808%20state-Don%20Solaris.m3u)
== m3u
2004-08-08 02:52:31.8867 numitems: 126
2004-08-08 02:52:31.8877 index: 1
2004-08-08 02:52:31.8895 itempath: Azura.mp3 and
file:///mnt/music/music/808%20State/Don%20Solaris made
file:///mnt/music/music/808%20State/Don%20Solaris/Azura.mp3
Segmentation fault

iTunes and Winamp don't appear to have issues with the file nor its
metadata so perhaps the issue lies elsewhere.
Something similar happens with v5.2.1 though at a different
location. Here are the last few lines...

2004-08-08 03:09:11.6258 numitems: 83
2004-08-08 03:09:11.6267 index: 11
2004-08-08 03:09:11.6286 itempath: Lifes on the Line (Bonus).mp3 and
file:///mnt/music/music/50%20Cent/Get%20Rich%20or%20Die%20Tryin' made
file:///mnt/music/music/50%20Cent/Get%20Rich%20or%20Die%20Tryin'/Lifes%20on%20the%20Line%20(Bonus).mp3
2004-08-08 03:09:11.6950
isList(file:///mnt/music/music/50%20Cent/Get%20Rich%20or%20Die%20Tryin'/Lifes%20on%20the%20Line%20(Bonus).mp3)
==
2004-08-08 03:09:11.6961 not a list:
file:///mnt/music/music/50%20Cent/Get%20Rich%20or%20Die%20Tryin'/Lifes%20on%20the%20Line%20(Bonus).mp3
2004-08-08 03:09:11.6971 adding single item:
file:///mnt/music/music/50%20Cent/Get%20Rich%20or%20Die%20Tryin'/Lifes%20on%20the%20Line%20(Bonus).mp3,
type mp3
2004-08-08 03:09:11.6986 numitems: 84
2004-08-08 03:09:11.6995 index: 12
2004-08-08 03:09:11.7014 itempath: Like my Style (Featuring Tony
Yayo).mp3 and
file:///mnt/music/music/50%20Cent/Get%20Rich%20or%20Die%20Tryin' made
file:///mnt/music/music/50%20Cent/Get%20Rich%20or%20Die%20Tryin'/Like%20my%20Style%20(Featuring%20Tony%20Yayo).mp3
Segmentation fault

Any suggestions for what can be done to resolve this?

--
Jason Rimmer
jrimmer at irth dot net

Jack Coates
2004-08-08, 09:24
> I've recently installed Slimserver v5.3b1 on a RedHat Fedora Core 2
> Linux machine for a new Squeezeboxen that's on the way. Everything
> works fine until I scan my music collection where upon I get a
> 'segmentation fault'. While I don't see anything too helpful the last
> few entries of the '--d_scan' log are...
>
> 2004-08-08 02:52:31.8754 directory entry:
> file:///mnt/music/music/808%20State/Don%20Solaris/Mooz.mp3
> 2004-08-08 02:52:31.8772 adding 14 to playlist cache:
> file:///mnt/music/music/808%20State/Don%20Solaris
> 2004-08-08 02:52:31.8784 Descending into
> file:///mnt/music/music/808%20State/Don%20Solaris, contains 14 items
> 2004-08-08 02:52:31.8797 numitems: 126
> 2004-08-08 02:52:31.8806 index: 0
> 2004-08-08 02:52:31.8825 itempath: 808 state-Don Solaris.m3u and
> file:///mnt/music/music/808%20State/Don%20Solaris made
> file:///mnt/music/music/808%20State/Don%20Solaris/808%20state-Don%20Solaris.m3u
> 2004-08-08 02:52:31.8848
> isList(file:///mnt/music/music/808%20State/Don%20Solaris/808%20state-Don%20Solaris.m3u)
> == m3u
> 2004-08-08 02:52:31.8867 numitems: 126
> 2004-08-08 02:52:31.8877 index: 1
> 2004-08-08 02:52:31.8895 itempath: Azura.mp3 and
> file:///mnt/music/music/808%20State/Don%20Solaris made
> file:///mnt/music/music/808%20State/Don%20Solaris/Azura.mp3
> Segmentation fault
>
> iTunes and Winamp don't appear to have issues with the file nor its
> metadata so perhaps the issue lies elsewhere.
> Something similar happens with v5.2.1 though at a different
> location. Here are the last few lines...
>
> 2004-08-08 03:09:11.6258 numitems: 83
> 2004-08-08 03:09:11.6267 index: 11
> 2004-08-08 03:09:11.6286 itempath: Lifes on the Line (Bonus).mp3 and
> file:///mnt/music/music/50%20Cent/Get%20Rich%20or%20Die%20Tryin' made
> file:///mnt/music/music/50%20Cent/Get%20Rich%20or%20Die%20Tryin'/Lifes%20on%20the%20Line%20(Bonus).mp3
> 2004-08-08 03:09:11.6950
> isList(file:///mnt/music/music/50%20Cent/Get%20Rich%20or%20Die%20Tryin'/Lifes%20on%20the%20Line%20(Bonus).mp3)
> ==
> 2004-08-08 03:09:11.6961 not a list:
> file:///mnt/music/music/50%20Cent/Get%20Rich%20or%20Die%20Tryin'/Lifes%20on%20the%20Line%20(Bonus).mp3
> 2004-08-08 03:09:11.6971 adding single item:
> file:///mnt/music/music/50%20Cent/Get%20Rich%20or%20Die%20Tryin'/Lifes%20on%20the%20Line%20(Bonus).mp3,
> type mp3
> 2004-08-08 03:09:11.6986 numitems: 84
> 2004-08-08 03:09:11.6995 index: 12
> 2004-08-08 03:09:11.7014 itempath: Like my Style (Featuring Tony
> Yayo).mp3 and
> file:///mnt/music/music/50%20Cent/Get%20Rich%20or%20Die%20Tryin' made
> file:///mnt/music/music/50%20Cent/Get%20Rich%20or%20Die%20Tryin'/Like%20my%20Style%20(Featuring%20Tony%20Yayo).mp3
> Segmentation fault
>
> Any suggestions for what can be done to resolve this?
>

could be difference between id3v1 and id3v2 tags, maybe one is corrupt and
the other media players are just ignoring it. I'd take a look with
easytag, which will do both tags.

--
Jack At Monkeynoodle.Org: It's A Scientific Venture...
"Believe what you're told; there'd be chaos if everyone thought for
themselves." -- Top Dog hotdog stand, Berkeley, CA

Jason Rimmer
2004-08-08, 15:53
Fixing up the ID3V1 tags appeared to resolve the issue at first but now
it's happening all over the place. Every scan results in a segmentation
fault and not at the same files. Files it passed at one time will cause
a segmentation fault the very next run and vice versa.
Heck, restarting SlimServer from the command like and simply clicking
on 'SqueezeBox Home' link at the top of the webpage sometimes results in
a segmentation fault.
I'm running on a just installed vanilla Fedora Core 2 with all updates
installed.

Jack Coates wrote:

>> I've recently installed Slimserver v5.3b1 on a RedHat Fedora Core 2
>>Linux machine for a new Squeezeboxen that's on the way. Everything
>>works fine until I scan my music collection where upon I get a
>>'segmentation fault'. While I don't see anything too helpful the last
>>few entries of the '--d_scan' log are...
>>
>>2004-08-08 02:52:31.8754 directory entry:
>>file:///mnt/music/music/808%20State/Don%20Solaris/Mooz.mp3
>>2004-08-08 02:52:31.8772 adding 14 to playlist cache:
>>file:///mnt/music/music/808%20State/Don%20Solaris
>>2004-08-08 02:52:31.8784 Descending into
>>file:///mnt/music/music/808%20State/Don%20Solaris, contains 14 items
>>2004-08-08 02:52:31.8797 numitems: 126
>>2004-08-08 02:52:31.8806 index: 0
>>2004-08-08 02:52:31.8825 itempath: 808 state-Don Solaris.m3u and
>>file:///mnt/music/music/808%20State/Don%20Solaris made
>>file:///mnt/music/music/808%20State/Don%20Solaris/808%20state-Don%20Solaris.m3u
>>2004-08-08 02:52:31.8848
>>isList(file:///mnt/music/music/808%20State/Don%20Solaris/808%20state-Don%20Solaris.m3u)
>>== m3u
>>2004-08-08 02:52:31.8867 numitems: 126
>>2004-08-08 02:52:31.8877 index: 1
>>2004-08-08 02:52:31.8895 itempath: Azura.mp3 and
>>file:///mnt/music/music/808%20State/Don%20Solaris made
>>file:///mnt/music/music/808%20State/Don%20Solaris/Azura.mp3
>>Segmentation fault
>>
>> iTunes and Winamp don't appear to have issues with the file nor its
>>metadata so perhaps the issue lies elsewhere.
>> Something similar happens with v5.2.1 though at a different
>>location. Here are the last few lines...
>>
>>2004-08-08 03:09:11.6258 numitems: 83
>>2004-08-08 03:09:11.6267 index: 11
>>2004-08-08 03:09:11.6286 itempath: Lifes on the Line (Bonus).mp3 and
>>file:///mnt/music/music/50%20Cent/Get%20Rich%20or%20Die%20Tryin' made
>>file:///mnt/music/music/50%20Cent/Get%20Rich%20or%20Die%20Tryin'/Lifes%20on%20the%20Line%20(Bonus).mp3
>>2004-08-08 03:09:11.6950
>>isList(file:///mnt/music/music/50%20Cent/Get%20Rich%20or%20Die%20Tryin'/Lifes%20on%20the%20Line%20(Bonus).mp3)
>>==
>>2004-08-08 03:09:11.6961 not a list:
>>file:///mnt/music/music/50%20Cent/Get%20Rich%20or%20Die%20Tryin'/Lifes%20on%20the%20Line%20(Bonus).mp3
>>2004-08-08 03:09:11.6971 adding single item:
>>file:///mnt/music/music/50%20Cent/Get%20Rich%20or%20Die%20Tryin'/Lifes%20on%20the%20Line%20(Bonus).mp3,
>>type mp3
>>2004-08-08 03:09:11.6986 numitems: 84
>>2004-08-08 03:09:11.6995 index: 12
>>2004-08-08 03:09:11.7014 itempath: Like my Style (Featuring Tony
>>Yayo).mp3 and
>>file:///mnt/music/music/50%20Cent/Get%20Rich%20or%20Die%20Tryin' made
>>file:///mnt/music/music/50%20Cent/Get%20Rich%20or%20Die%20Tryin'/Like%20my%20Style%20(Featuring%20Tony%20Yayo).mp3
>>Segmentation fault
>>
>>Any suggestions for what can be done to resolve this?
>>
>
>
> could be difference between id3v1 and id3v2 tags, maybe one is corrupt and
> the other media players are just ignoring it. I'd take a look with
> easytag, which will do both tags.
>

--
Jason Rimmer
jrimmer at irth dot net

jacobdp
2004-08-08, 15:59
On Sun, 08 Aug 2004 18:53:35 -0400, Jason Rimmer <jrimmer (AT) irth (DOT) net> wrote:
> Fixing up the ID3V1 tags appeared to resolve the issue at first but now
> it's happening all over the place. Every scan results in a segmentation
> fault and not at the same files. Files it passed at one time will cause
> a segmentation fault the very next run and vice versa.
> Heck, restarting SlimServer from the command like and simply clicking
> on 'SqueezeBox Home' link at the top of the webpage sometimes results in
> a segmentation fault.
> I'm running on a just installed vanilla Fedora Core 2 with all updates
> installed.

Sounds like a problem with your RAM to me. Is Slimserver the only
memory-intensive thing running on that computer?

I'd try running something like memtest86 and see if it picks up
anything, or just swap the DIMM with another computer for a while. You
could also try compiling something large, like the kernel, and see if
that causes segfaults as well.

- Jacob

Jason Rimmer
2004-08-08, 16:03
As I finished typing my message I was beginning to think the same
thing. As the errors I reported got crazier and crazier...

Jacob Potter wrote:

> On Sun, 08 Aug 2004 18:53:35 -0400, Jason Rimmer <jrimmer (AT) irth (DOT) net> wrote:
>
>> Fixing up the ID3V1 tags appeared to resolve the issue at first but now
>>it's happening all over the place. Every scan results in a segmentation
>>fault and not at the same files. Files it passed at one time will cause
>>a segmentation fault the very next run and vice versa.
>> Heck, restarting SlimServer from the command like and simply clicking
>>on 'SqueezeBox Home' link at the top of the webpage sometimes results in
>>a segmentation fault.
>> I'm running on a just installed vanilla Fedora Core 2 with all updates
>>installed.
>
>
> Sounds like a problem with your RAM to me. Is Slimserver the only
> memory-intensive thing running on that computer?
>
> I'd try running something like memtest86 and see if it picks up
> anything, or just swap the DIMM with another computer for a while. You
> could also try compiling something large, like the kernel, and see if
> that causes segfaults as well.
>
> - Jacob
>

Robin Bowes
2004-08-09, 04:23
On Sun, August 8, 2004 23:53, Jason Rimmer said:
> Fixing up the ID3V1 tags appeared to resolve the issue at first but now
> it's happening all over the place. Every scan results in a segmentation fault and not at
> the same files. Files it passed at one time will cause a segmentation fault the very
> next run and vice versa. Heck, restarting SlimServer from the command like and simply
> clicking on 'SqueezeBox Home' link at the top of the webpage sometimes results in a
> segmentation fault. I'm running on a just installed vanilla Fedora Core 2 with all
> updates installed.

Segmentation faults are often due to bad RAM which becomes apparent when you perform a RAM-hungry task, e.g. gcc compilation or re-scanning a large music collection (how big is yours?).

It might be worth runnign some checks on your RAM. At the very least it would eliminate that as a possible cause of the problem.

R.
--
http://robinbowes.com

Jason Rimmer
2004-08-14, 16:55
Latest news: ran memtest86 overnight with no errors encountered and did
an fsck with no bad sectors found. Slimserver's still segmentation
fault'ing when scanning my music collection.
Could it be because of odd character sets on some artist names such as
Bjork or as my mp3 collection has it with an umlauted o?

Robin Bowes wrote:

> On Sun, August 8, 2004 23:53, Jason Rimmer said:
>
>>Fixing up the ID3V1 tags appeared to resolve the issue at first but now
>>it's happening all over the place. Every scan results in a segmentation fault and not at
>>the same files. Files it passed at one time will cause a segmentation fault the very
>>next run and vice versa. Heck, restarting SlimServer from the command like and simply
>>clicking on 'SqueezeBox Home' link at the top of the webpage sometimes results in a
>>segmentation fault. I'm running on a just installed vanilla Fedora Core 2 with all
>>updates installed.
>
>
> Segmentation faults are often due to bad RAM which becomes apparent when you perform a RAM-hungry task, e.g. gcc compilation or re-scanning a large music collection (how big is yours?).
>
> It might be worth runnign some checks on your RAM. At the very least it would eliminate that as a possible cause of the problem.
>
> R.

--
Jason Rimmer
jrimmer at irth dot net

dean
2004-08-15, 15:20
On Aug 14, 2004, at 4:55 PM, Jason Rimmer wrote:

> Latest news: ran memtest86 overnight with no errors encountered and
> did an fsck with no bad sectors found. Slimserver's still
> segmentation fault'ing when scanning my music collection.
> Could it be because of odd character sets on some artist names such
> as Bjork or as my mp3 collection has it with an umlauted o?
It's possible, but unlikely, as Perl is what's crashing, not
SlimServer, and Perl's pretty good about this. Are you sure it's
segfaulting? Is there any diagnostic output when it happens?


>
> Robin Bowes wrote:
>
>> On Sun, August 8, 2004 23:53, Jason Rimmer said:
>>> Fixing up the ID3V1 tags appeared to resolve the issue at first but
>>> now
>>> it's happening all over the place. Every scan results in a
>>> segmentation fault and not at
>>> the same files. Files it passed at one time will cause a
>>> segmentation fault the very
>>> next run and vice versa. Heck, restarting SlimServer from the
>>> command like and simply
>>> clicking on 'SqueezeBox Home' link at the top of the webpage
>>> sometimes results in a
>>> segmentation fault. I'm running on a just installed vanilla Fedora
>>> Core 2 with all
>>> updates installed.
>> Segmentation faults are often due to bad RAM which becomes apparent
>> when you perform a RAM-hungry task, e.g. gcc compilation or
>> re-scanning a large music collection (how big is yours?).
>> It might be worth runnign some checks on your RAM. At the very least
>> it would eliminate that as a possible cause of the problem.
>> R.
>
> --
> Jason Rimmer
> jrimmer at irth dot net
>

Jason Rimmer
2004-08-15, 20:34
Noo diagnostic information other than the "Segmentation Fault" message.
I ran the following way: './slimserver.pl --d_scan --d_info --d_paths'
and it appears the fault is either happening at a cache insert or
whatever happens directly after it.

....
2004-08-15 15:07:04.0147 Converting
file:///mnt/music/music/ABC/Absolutely%20ABC/That%20Was%20Then%20But%20This%20Is%20Now.mp3
to /mnt/music/music/ABC/Absolutely ABC/That Was Then But This Is Now.mp3
2004-08-15 15:07:04.0158 mp3 file type for
file:///mnt/music/music/ABC/Absolutely%20ABC/That%20Was%20Then%20But%20This%20Is%20Now.mp3
2004-08-15 15:07:04.0167 Updating cache for:
file:///mnt/music/music/ABC/Absolutely%20ABC/That%20Was%20Then%20But%20This%20Is%20Now.mp3
Segmentation fault

dean blackketter wrote:

>
> On Aug 14, 2004, at 4:55 PM, Jason Rimmer wrote:
>
>> Latest news: ran memtest86 overnight with no errors encountered
>> and did an fsck with no bad sectors found. Slimserver's still
>> segmentation fault'ing when scanning my music collection.
>> Could it be because of odd character sets on some artist names
>> such as Bjork or as my mp3 collection has it with an umlauted o?
>
> It's possible, but unlikely, as Perl is what's crashing, not SlimServer,
> and Perl's pretty good about this. Are you sure it's segfaulting? Is
> there any diagnostic output when it happens?
>
>
>>
>> Robin Bowes wrote:
>>
>>> On Sun, August 8, 2004 23:53, Jason Rimmer said:
>>>
>>>> Fixing up the ID3V1 tags appeared to resolve the issue at first but now
>>>> it's happening all over the place. Every scan results in a
>>>> segmentation fault and not at
>>>> the same files. Files it passed at one time will cause a
>>>> segmentation fault the very
>>>> next run and vice versa. Heck, restarting SlimServer from the
>>>> command like and simply
>>>> clicking on 'SqueezeBox Home' link at the top of the webpage
>>>> sometimes results in a
>>>> segmentation fault. I'm running on a just installed vanilla Fedora
>>>> Core 2 with all
>>>> updates installed.
>>>
>>> Segmentation faults are often due to bad RAM which becomes apparent
>>> when you perform a RAM-hungry task, e.g. gcc compilation or
>>> re-scanning a large music collection (how big is yours?).
>>> It might be worth runnign some checks on your RAM. At the very least
>>> it would eliminate that as a possible cause of the problem.
>>> R.
>>
>>
>> --
>> Jason Rimmer
>> jrimmer at irth dot net
>>