Bug 3875 - Slimserver 6.5 8806 and squeezbox lockup when running slimserver in the background.
: Slimserver 6.5 8806 and squeezbox lockup when running slimserver in the back...
Status: RESOLVED WONTFIX
Product: Logitech Media Server
Classification: Unclassified
Component: Streaming From SlimServer
: 6.5b1
: Other SuSE Linux
: P2 normal (vote)
: ---
Assigned To: Chris Owens
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-08-05 17:13 UTC by mike
Modified: 2006-08-09 14:15 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments
transcript of terminal dump (66.29 KB, text/plain)
2006-08-08 03:39 UTC, mike
Details
log file as per email prior (62.07 KB, text/plain)
2006-08-09 06:03 UTC, mike
Details
as per email prior (failure case (28.55 KB, text/plain)
2006-08-09 06:03 UTC, mike
Details
as per email prior with daemon switch (77.69 KB, text/plain)
2006-08-09 06:05 UTC, mike
Details
as per email with daemon switch and & (89.25 KB, text/plain)
2006-08-09 06:07 UTC, mike
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mike 2006-08-05 17:13:24 UTC
Gents, a summary of the problem below.

I have 6.5b 8806 installed along with Alien BBC on Linux Suse10. I had been having a problem playing M4a using Mplayer to transcode to Mp3.

Basically when I run slimserver in the background /usr/local/slimserver/slimserver.pl & and I select a track which is an M4a and press play the squeezebox locks up as does the slimserver software. Note the lock up doesnt occur when trying to play other file types.

If I run slimserver as follows there is no problem /usr/local/slimserver/slimserver.pl 

PS if your wondering why I was running slimserver in the background its because the startup scripts provided in the rpm are redhat centric and dont work on suse linux.

Hope the above helps.

Regards

Mike
Comment 1 KDF 2006-08-05 20:24:44 UTC
the only scripts that come from the rpm are for /etc/init.d/slimserver.

if you are running /usr/local/slimserver/slimserver.pl & 
it is exactly the same as running /usr/local/slimserver/slimserver.pl

in fact, just run as it works for you, press CTRL-C then type 'bg' and press enter.
then you have done exactly what the & does.
Comment 2 mike 2006-08-06 00:48:34 UTC
(In reply to comment #1)
> the only scripts that come from the rpm are for /etc/init.d/slimserver.

Well dont you mean etc/rc.d/init.d/slimserver ? this is where the files end up and this is what is quoted in the Installation.txt that comes with the svn where it quotes "/etc/rc.d/init.d/slimserver" start as the command

> if you are running /usr/local/slimserver/slimserver.pl & 
> it is exactly the same as running /usr/local/slimserver/slimserver.pl
> in fact, just run as it works for you, press CTRL-C then type 'bg' and press
> enter.
> then you have done exactly what the & does.

Thats what I thought but is obviously produces a different response!!!

Comment 3 KDF 2006-08-06 09:25:58 UTC
ok, just to be clear.  you are not running the init.d scripts?
(btw, on redhat systems /etc/init.d and etc/rc.d/init.d are links to the same thing.)
Comment 4 mike 2006-08-07 01:54:45 UTC
(In reply to comment #3)
> ok, just to be clear.  you are not running the init.d scripts?
> (btw, on redhat systems /etc/init.d and etc/rc.d/init.d are links to the same
> thing.)
> 

Yes the problem occurs when I dont use the startup scripts.

The etc/rc.d/init.d/slimserver start commands dont work on suse, best I can work out this is because suse expect the script to be in et/init.d and suse doesnt have either a . /etc/rc.d/init.d/functions and . /etc/sysconfig/network directory both of which are called via the starup scripts.

I used to use a hacked startup script as per http://forums.slimdevices.com/showthread.php?t=22156&highlight=starting+automatically+linux which worked with 6.31 but with all changes in 6.5b appears not to work.

Regards

Mike
Comment 5 KDF 2006-08-07 10:28:38 UTC
ok, try turning on d_source and d_slimproto in server settings->debugging.  when you start slimserver, start watching the log ( tail -f /tmp/slimserver.log) and try playing your m4a file.  
Comment 6 mike 2006-08-08 03:39:14 UTC
Created attachment 1401 [details]
transcript of terminal dump

as per beg repot
Comment 7 mike 2006-08-08 03:40:09 UTC
(In reply to comment #5)
> ok, try turning on d_source and d_slimproto in server settings->debugging. 
> when you start slimserver, start watching the log ( tail -f
> /tmp/slimserver.log) and try playing your m4a file.  
> 

OK Sorry for the delay ...different time zone/work etc.

Bottom line I have no log file ;(

Anyway I capture the dump to the terminal of the bad session started /usr/local/slimserver/slimserver.pl & and it crashed see below. I then captured the dump to the terminal screen for the good session I didn't catch the first bit however I think the info you need to compare is there, (Note I turned off the squeezebox at the end so I could capture the good screen dump). The good version is after the ********************** below.

Hope this helps.

PS slimserver web interface is permanently display "Note: SlimServer is still scanning your music library. Please be patient as this may take a while." and has been for days.





Comment 8 KDF 2006-08-08 10:28:57 UTC
On the version that crashes, is that where the log simply stops or did you cut it off there?  Howe long was it stuck with that as the last thing?

Notice that in the working case (would have been nice to have been the EXACT same steps, including the same song) there is a "error on socket" message, as well as a Mplayer crash later in the log.  I'm curious about the state of your "working" case.

Maybe Andy has some ideas?
Comment 9 Andy Grundman 2006-08-08 10:34:30 UTC
Does it work any different if you run with the --daemon switch instead of &?  You might try running something like --d_source --daemon --logfile=/var/log/slimserver.log 
Comment 10 mike 2006-08-09 06:00:42 UTC
(In reply to comment #9)
> Does it work any different if you run with the --daemon switch instead of &? 
> You might try running something like --d_source --daemon
> --logfile=/var/log/slimserver.log 
> 

OK Chaps next try. I created a slimserver.log file in /var them chmod 7777 /var/slimserver.log just to be sure

I ran /usr/local/slimserver/slimserver.pl --d_source --d_slimproto --logfile=/var/slimserver.log
Above ran ok as normal see slimserver.logOK (to follow)

I ran /usr/local/slimserver/slimserver.pl --d-source --d-slimprot --logfile=/var/slimserver.log &
locked up as usual see slimserver.log2 (to follow). Note waited 1 min before holding down the power button to reboot squeezebox. the log file ends where it ends.

I ran /usr/local/slimserver/slimserver.pl --d-source --d-slimprot --daemon --logfile=/var/slimserver.log
Above ran ok see slimserver.logd

I ran /usr/local/slimserver/slimserver.pl --d-source --d-slimprot --daemon --logfile=/var/slimserver.log &
Above ran ok see slimserver.logd& (to follow)

Note for all cases where it ran ok I paused the track and shutdown the squeezbox.
Comment 11 mike 2006-08-09 06:03:27 UTC
Created attachment 1406 [details]
log file as per email prior

as per eamil prior
Comment 12 mike 2006-08-09 06:03:58 UTC
Created attachment 1407 [details]
as per email prior (failure case
Comment 13 mike 2006-08-09 06:05:02 UTC
Created attachment 1408 [details]
as per email prior with daemon switch
Comment 14 mike 2006-08-09 06:07:36 UTC
Created attachment 1409 [details]
as per email with daemon switch and &
Comment 15 Andy Grundman 2006-08-09 07:04:32 UTC
So --daemon solves the problem?
Comment 16 mike 2006-08-09 07:23:56 UTC
(In reply to comment #15)
> So --daemon solves the problem?
> 

Well I might be playing with words here but using the --daemon switch and & works but 

/usr/local/slimserver/slimserver.pl & doesn't which was the orig problem reported!!!
Comment 17 Andy Grundman 2006-08-09 07:26:08 UTC
But --daemon is better than using &.  There is no point to running with both --daemon and &.
Comment 18 mike 2006-08-09 07:32:32 UTC
Subject: RE:  Slimserver 6.5 8806  and squeezbox lockup when running slimserver in the background.

Ok no problem!!!

6.5 looking good now...still no suse startup scritps tho :(

-----Original Message-----
From: Slim Devices Bugzilla [mailto:bugs@bugs.slimdevices.com] 
Sent: Wednesday, 9 August 2006 10:26 PM
To: mjpine@gmail.com
Subject: [Bug 3875] Slimserver 6.5 8806 and squeezbox lockup when running
slimserver in the background.

https://bugs-archive.lyrion.org/show_bug.cgi?id=3875


andy@slimdevices.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX




------- Comment #17 from andy@slimdevices.com  2006-08-09 07:26 ------- But
--daemon is better than using &.  There is no point to running with both
--daemon and &.




------- You are receiving this mail because: ------- You reported the bug,
or are watching the reporter.

Comment 19 Chris Owens 2006-08-09 14:00:39 UTC
Looks like the Suse startup script is bug 1906, for anyone's information stumbling acros this bug.
Comment 20 KDF 2006-08-09 14:15:06 UTC
there are some scripts on the wiki?  are none of them valid with 6.5?  of not, might be worth adding a note on those pages.