Home of the Squeezebox™ & Transporter® network music players.
Results 1 to 8 of 8
  1. #1
    Junior Member
    Join Date
    Aug 2008
    Posts
    15

    Squeezebox on Arch Linux Crashes perl

    I'm on Arch Linux, and I've tried installing several versions of squeezebox server both manually and via AUR builds... The furthest I've gotten is this:

    The web interface starts up, I put in my mysqueezebox.com login, choose music and playlist folders, then once I click the "Finish" button, I get the messages about missing tables. Of course they're missing, squeezebox! But it seems they get created at this point anyway. Then slimserver.pl just exits and I get my prompt back.

    When I try again, I get about the same thing except no message about the missing tables, so I guess they were created fine... but at some point right after this, the server just exits! No error message, no "Segmentation Fault".. just an exit.

    Anyone have any idea what this could be or how I could get some more information?

    The output snip doesn't really add much to the description of my issue, but here it is anyway:

    http://snipt.org/kgknk
    Last edited by thread; 2010-08-31 at 19:09.

  2. #2
    Junior Member
    Join Date
    Aug 2008
    Posts
    15
    Tried again with the latest nightly MANUALLY (not using the arch PKGBUILD). Not sure why, but this time, I actually saw the segfault. This was the second run. The first one gave me all the messages about missing tables which obviously get created. I get the segfault right after I click "Finish" on the initial setup screens.

    [mythtv@therver squeezeboxserver]$ ./slimserver.pl
    [10-08-31 15:22:12.4755] main::init (323) Starting Squeezebox Server (v7.5.2, r31264, Mon Aug 30 03:03:47 MDT 2010) perl 5.012001
    Segmentation fault
    [mythtv@therver squeezeboxserver]$

    I've never had this much trouble with this stuff...

  3. #3
    Senior Member snarlydwarf's Avatar
    Join Date
    Jul 2005
    Location
    Oregon
    Posts
    3,675
    Quote Originally Posted by thread View Post
    [mythtv@therver squeezeboxserver]$ ./slimserver.pl
    [10-08-31 15:22:12.4755] main::init (323) Starting Squeezebox Server (v7.5.2, r31264, Mon Aug 30 03:03:47 MDT 2010) perl 5.012001
    Segmentation fault
    [mythtv@therver squeezeboxserver]$

    I've never had this much trouble with this stuff...
    Don't do that.

    SBS should be started by an init script, usually this is done as root, and then privileges are dropped.

    Doesn't whatever package you installed provide an init script?

    (SBS is, by default, going to want to write files in places your user id can not write to... those will fail. A proper package should create these areas, set the ownership correctly, and launch SBS with a specific userid that can write to these files. It will also correctly set up MySQL so that SBS can talk to it, etc...)

  4. #4
    Junior Member
    Join Date
    Aug 2008
    Posts
    15
    Thanks for the reply, snarlydwarf. The same thing happens when I use the proper init scripts. In this instance, I was installing it manually. Everything was owned by the mythtv user, so permissions shouldn't be the problem. Nor is db access since I can see all the tables are created.

    vesath over on this thread suggested that there's something funky with my system. This seems possible... but how do I narrow it down?

  5. #5
    Administrator andyg's Avatar
    Join Date
    Jan 2006
    Location
    Pittsburgh, PA
    Posts
    7,395
    You could try debugging the segfault so we could see where it's crashing:

    Code:
    ulimit -c unlimited
    perl slimserver.pl
    gdb perl <corefile>
    bt

  6. #6
    Junior Member
    Join Date
    Aug 2008
    Posts
    15
    Thanks Andy. The full listing is here: http://snipt.org/kglL

    Abridged version follows. Bedtime for now...

    Code:
    [mythtv@therver squeezeboxserver]$ gdb perl core
    
    ...
    
    Core was generated by `/usr/bin/perl -w ./slimserver.pl'.
    Program terminated with signal 11, Segmentation fault.
    #0  0x0000000000000000 in ?? ()
    (gdb) bt
    #0  0x0000000000000000 in ?? ()
    #1  0x00007f030c24ee30 in Perl_runops_standard () from /usr/lib/perl5/core_perl/CORE/libperl.so
    #2  0x00007f0309febe65 in XS_List__Util_first () from /usr/lib/perl5/vendor_perl/auto/List/Util/Util.so
    #3  0x00007f030c257880 in Perl_pp_entersub () from /usr/lib/perl5/core_perl/CORE/libperl.so
    #4  0x00007f030c24ee30 in Perl_runops_standard () from /usr/lib/perl5/core_perl/CORE/libperl.so
    #5  0x00007f030c1f16ff in Perl_call_sv () from /usr/lib/perl5/core_perl/CORE/libperl.so
    #6  0x00007f0309b24bfa in ?? ()
       from /opt/squeezeboxserver-7.5.2-31264/CPAN/arch/5.12/x86_64-linux-thread-multi/auto/EV/EV.so
    #7  0x00007f0309b1e934 in ev_invoke_pending ()
       from /opt/squeezeboxserver-7.5.2-31264/CPAN/arch/5.12/x86_64-linux-thread-multi/auto/EV/EV.so
    #8  0x00007f0309b3bf22 in ev_loop ()
       from /opt/squeezeboxserver-7.5.2-31264/CPAN/arch/5.12/x86_64-linux-thread-multi/auto/EV/EV.so
    #9  0x00007f0309b3ca4d in XS_EV_loop ()
       from /opt/squeezeboxserver-7.5.2-31264/CPAN/arch/5.12/x86_64-linux-thread-multi/auto/EV/EV.so
    #10 0x00007f030c257880 in Perl_pp_entersub () from /usr/lib/perl5/core_perl/CORE/libperl.so
    #11 0x00007f030c24ee30 in Perl_runops_standard () from /usr/lib/perl5/core_perl/CORE/libperl.so
    #12 0x00007f030c1f73ee in perl_run () from /usr/lib/perl5/core_perl/CORE/libperl.so
    #13 0x0000000000400f54 in main ()
    (gdb)

  7. #7
    Administrator andyg's Avatar
    Join Date
    Jan 2006
    Location
    Pittsburgh, PA
    Posts
    7,395
    One thing I notice is that you are running 5.12.1 but at least one of the modules being loaded is from 5.10.1:

    Loaded symbols for /usr/lib/perl5/site_perl/5.10.1/auto/Term/ReadKey/ReadKey.so

    You should try running the server under 5.10.1 since you seem to have it installed. 5.12.1 is new and hasn't had much testing yet.

  8. #8
    Junior Member
    Join Date
    Aug 2008
    Posts
    15
    I don't think reverting to perl 5.10 is really an option for me at this point because I have too many dependencies etc. It is mega bogus, but my approach is now to set up a virtualbox VM and attempt to run the server from there. At least until this issue blows over with an update.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •