Bugzilla – Bug 13664
rpm build does not autostart after an upgrade (or an install ) on all systems.
Last modified: 2012-04-19 11:34:34 UTC
See our discussion here: http://forums.slimdevices.com/showthread.php?p=451411#post451411 Install with yum it starts. Install with rpm you have to manually restart. No real problems as start-up after bot is ok and works after that. Just the initial start after install.
Exactly what OS are you running, and which rev did this happen with. Does it happen with todays? (we've tested this on a few systems without this problem)
My OS: ClarkConnect 4.2 community edition Kernel version 2.6.18-53.1.13.2.cc (SMP) squeezebox server: Version: 7.4 - r28286 @ Wed Aug 26 07:38:14 PDT 2009 Hostname: hal.home.lan Server IP Address: 192.168.1.5 Server HTTP Port Number: 9000 Operating system: Red Hat - EN - utf8 Platform Architecture: i686-linux Perl Version: 5.8.8 - i686-linux-thread-multi MySQL Version: 4.1.20 Total Players Recognized: 4 This problem started with the first build i managed to install after you fixed bug 13485 . >28235 ?
More info everytime i stop the server i get this in my shell: Last login: Mon Aug 31 20:50:45 2009 from mikael.home.lan [root@hal ~]# service squeezeboxserver stop /sbin/service: line 68: 3180 Terminated env -i LANG="$LANG" PATH="$PATH" TERM="$TERM" "${SERVICEDIR}/${SERVICE}" ${OPTIONS} [root@hal ~]# This has not been the case with 7.1 to early 7.4 beta running on the same OS and Hardware.
Ross can you set up a ClarkConnect vmware image and test this... if you get it replicated, let me know via IM and I'll see what the fix is.
Ok Starting to think a little you don't have to reinstall to get this error It's the restart command that does not work [root@hal ~]# service squeezeboxserver restart /sbin/service: line 68: 31506 Terminated env -i LANG="$LANG" PATH="$PATH" TERM="$TERM" "${SERVICEDIR}/${SERVICE}" ${OPTIONS} Stop and Start works for some reason. [root@hal ~]# service squeezeboxserver start Starting Squeezebox Server: [ OK ] [root@hal ~]# Note that i'm on CC4.2 not 4.3 (which sends my hardware into kernel panic) . I have not dared to try CC5.0 yet CC5.0 uses yum so it seems tempting to do that.
Bump, it's still the same nothing changed regarding this.
Can someone update this bug. The [root@hal ~]# service squeezeboxserver restart command is not working "stop" and "start" works, stop gives you fault messages. And thus autostart after install is not working. But there is news, the restart prompt from within the web-UI when you install plugin or something, don't work either ! So it must use the same flawed method.
The option --full-restart works but not restart. Is this something with the CC.4.2 service script ?
I'm running a CentOS 4 relative myself (SME aka. e-smith). restart is working fine here. Are you running the startup script as provided by the RPM?
i certainly hope soo, I have not modified the startup script myself ? There is a related issue, normaly the deamon runs as "squeezeboxserver" but after a plugin has updated and LMS demands a restart via the web-UI, when i click restart in the web-UI I notice that the process when restarted is now called "perl" instead of "squeezeboxserver" . and it is no longer possible to stop with the stop command. the web-UI is capable of restarting multiple times. I'm on my iPad now I could attach my startup script later ? Does not the installer give me a new one every now and then ? i reported the bug 2009 ? where do i find it init somewhere ?
Created attachment 7482 [details] startup script from my system My startup script. Looks unmodified to me . Also. cat redhat-release CentOS release 4.4 (Final)
The problem here seems to be that the init script relies on the executable name to stop the server. But SBS is restarting the server using the perl executable. Not sure how to fix this. We could disable server restarts from the server side, or make them smarter.
(In reply to comment #12) > The problem here seems to be that the init script relies on the executable name > to stop the server. But SBS is restarting the server using the perl executable. > Not sure how to fix this. We could disable server restarts from the server > side, or make them smarter. yes , but thats not this bug ( there is another bug for that ) but it is related Even if it's running as squeezeboxserver "restart" would not work on my system start and stop does work which in itself is wierd as restart only seems to be stop and start with a time delay, but as the stop command gives you some error output ( but it is stopping ) it looks like it's not following the script anymoore after that ? Wonder why it's terminating at line 68 in the service script. Disabling restart would break it for far to many other user who don't see this problem. The situation is "stable" i know what to do in different situations.
Unassigned bugs cannot have a priority.
(In reply to comment #12) > The problem here seems to be that the init script relies on the executable name > to stop the server. But SBS is restarting the server using the perl executable. > Not sure how to fix this. We could disable server restarts from the server > side, or make them smarter. See analysis in https://bugs-archive.lyrion.org/show_bug.cgi?id=17729
(In reply to comment #15) > (In reply to comment #12) > > The problem here seems to be that the init script relies on the executable name > > to stop the server. But SBS is restarting the server using the perl executable. > > Not sure how to fix this. We could disable server restarts from the server > > side, or make them smarter. > > See analysis in https://bugs-archive.lyrion.org/show_bug.cgi?id=17729 Ok but in this bug I have already sucesfully stoped the server and are manually installing a server upgrade, SBS is not running at all yet ? I'll try to find another related bug the restart command is broken to . "#service squeezeboxserver restart" does not work either on my machine
*** This bug has been marked as a duplicate of bug 17729 ***
Mikael - how did you update your perl? I installed CC 4.2 and it's still using 5.8.5.
Not a dupe.
(In reply to comment #18) > Mikael - how did you update your perl? I installed CC 4.2 and it's still using > 5.8.5. That was a long time ago I used these instructions http://www.ulverston.myzen.co.uk/mini-itx/old_stuff/perl.htm To build my own perl .
It works with a never version of my OS , I'm building a server based on ClearOS6.2 rc1 right now on that server I don't see this problem. So I close this bug for now. I'm probably the last person that had a CC4.2 server, can't imagine that anyone else are interested . Logitech Media Server Version: 7.8.0 - r33939 @ Wed Apr 18 04:06:49 MDT 2012 Hostname: nostromo.home.lan Server IP Address: 192.168.1.50 Server HTTP Port Number: 9000 Operating system: Red Hat - EN - utf8 Platform Architecture: i686-linux Perl Version: 5.10.1 - i386-linux-thread-multi Database Version: DBD::SQLite 1.34_01 (sqlite 3.7.7.1) Total Players Recognized: 1