After upgrade to SBS 7.4.2 server starts with strange screen and dies. Reproducible: Always Steps to Reproduce: 1. Upgraded from 7.4.1 to SBS 7.4.2. Package builds correctly (pulls in about 70 perl packages). Good job. 2. Fire it up /etc/init.d/SBS start 3. Server starts as a perl item and has a PID 4. Using browser pointed to SBS:9000 does not produce the familiar server screen; Instead produces a login SB.com, with a next to another screen to select where music is located, and a finish button. 5. Doing this an selecting finish kills SBS. Now, stuck in PID hell since start/stop daemon is hosed with no PID. Note: Starting SBS as /usr/sbin/SBS produces nirvana, everything works as before (7.4.1) and as expected. My guess is something in the SBS init.d is hosed. Not sure if this is just me though. I re-emerged SBS 7.4.2 and it made no difference in the foregoing. Actual Results: Server will not run using the init.d start Expected Results: Should run
You should check: http://bugs.gentoo.org/show_bug.cgi?id=307119 Seems the same to me. I'm also troubled by that bug.
This doesn't sound quite like the report in bug#307119 since in this case the server isn't starting. Did you definitely run dispatch-conf following this installation, and re-run the "emerge --config" step highlighted at the end of the installation? The 7.4.1-->7.4.2 upgrade has moved things around a bit to better fit in with the Gentoo standards and this may have caused some trouble. If so, and you're still having trouble, you could try cleaning things out as described here (although be aware that this will lose settings): http://bugs.gentoo.org/show_bug.cgi?id=307119#c11 Note that if the process falls over and "/etc/init.d/squeezeboxserver restart" won't fix it because it thinks it's already running, then if you're definitely sure it isn't a "/etc/init.d/squeezeboxserver zap" will reset the state so that Gentoo knows it's not running.
*** Bug 315529 has been marked as a duplicate of this bug. ***
OK. As recommended I deleted /var/lib/squeezeboxserver and /etc/squeezeboxserver. In addition, I deleted SBS from /etc/init.d and /etc/conf.d. I did emerge -C SBS and the emerge SBS. Then ran the SBS config to set up a new database. After this, /etc/init.d/SBS start gives: * Caching service dependencies ... [ ok ] * Starting Squeezebox Server ... dirsFor: Didn't find a match request: [scprefs] Use of uninitialized value $olddir in -d at /usr/lib/perl5/vendor_perl/5.10.1/Slim/Utils/OS/Unix.pm line 122. According to SystemMonitor, a perl process for SBS is running and I get the expected SBS screen. In addition, SBS is automatically scanning my music folder. A subsequent application of /etc/init.d/SBS start no longer issues the perl complaints and things work as expected, although it appears I will need to re-configure my SBS settings. So, I needed to read/heed the package notes more closely. I therefore suggest you mark this bug as resolved. Stuart, the Perl stuff works great as the emerge went perfectly. Thanks for you work, I enjoy the music.
I'm getting this in squeezeboxserver 7.5.0. I found this article last time I upgraded and it helped, however this time it was a fresh install (as in formatted drives) and same bug. So I'm not sure it's to do with pre-existing data. Just thought someone should know. :)
Running the steps below referenced by the link from Stuart (but for 7.5) make it work for me. Which I believe means that the default install is at fault, though I'm certainly no expert on that! :) OK for me it's working now - I get this errors in logs but now sbs don't dies. Here's what I've done: emerge -C squeezeboxserver rm -rf /var/lib/squeezeboxserver rm -rf /etc/squeezeboxserver emerge squeezeboxserver (7.4.2 ebuild from Stuart git hub)
(In reply to comment #0) I had similar trouble with 7.4.2-r1. SBS would crash after clicking the finish button. In my case I found that the password was not always set in /etc/squeezeboxserver/squeezeboxserver.prefs and/or /etc/squeezeboxserver/prefs/server.prefs . Sometimes it would be set in one and not the other. This could be related to not running emerge --config =media-sound/squeezeboxserver-7.4.2-r1 .
Created attachment 234911 [details] Squeezebox error log
I've gotten so tired of this one I've actually written scripts to remove it all and re-add it all which seems to be the only way to actually get it to install. However after running successfully for some time it has decided today to be 'crashed' again. At least that's what the service says. I checked the db password locations mentioned prior and mine is set fine. I have attached my squeezebox server log incase that helps someone in resolving this.
(In reply to comment #9) > I've gotten so tired of this one I've actually written scripts to remove it all > and re-add it all which seems to be the only way to actually get it to install. > However after running successfully for some time it has decided today to be > 'crashed' again. At least that's what the service says. I checked the db > password locations mentioned prior and mine is set fine. I have attached my > squeezebox server log incase that helps someone in resolving this. > Just a note for the bug, but looking at the log you're now running 7.5.0 rather than 7.4.2 (which this bug covers). No problem with that - I'm just noting it for the record. Sorry you're having trouble. Looking at the log it appears to be having trouble connecting to the MySQL instance on your local machine - are you sure that MySQL isn't failing (eg due to lack of space on /var/lib/mysql)? A test could be, *after SBS has failed*, to see if you can connect to MySQL in the same way that SBS will. Try the following command: mysql --socket=/var/run/mysqld/mysqld.sock --protocol=SOCKET --user=<dbusername> --password=<dbpassword> squeezeboxserver Where 'user' and 'password' are the 'dbusername' and 'dbpassword' settings from /etc/squeezeboxserver/squeezeboxserver.prefs If that connects and you get a MySQL prompt, try a simple query like "select count(*) from tracks;" and see if that gets a result. Not running emerge --config following an upgrade should be OK in general usage since your old configuration should be protected, but the preference files moved recently which meant that the --config step was necessary on the upgrade to 7.5.0.
All: is this still an issue, or has it been resolved? If still an issue, what versions are affected?
Sorry, seems I missed the last two comments. Yes it still persists. I haven't noticed any upgrades to squeezebox if that's what you mean. Perhaps I missed something. I've actually not bothered fixing it until now as it just seems pointless. However am more than happy to work through it all with someone if they can give me some pointers. Will try the database suggestion in a sec.
I see 7.5.1 is out, though while there is one very needed feature in there (wake up server 5 minutes before alarm starts) doesn't seem to be too much in the way of fixing this. But perhaps a new build will resolve whatever this erronous issue is.
Looks like I'll have to wait til it breaks next as my reinstall before this has worked for now. It won't be long though I'm sure.... :)
It happened again, but I found out I'd forgotten to put mysql into the init scripts on this build and once I started that all was OK. I've had to re-do the squeezebox config in a rush a couple of times but just sat down with it now. I'll keep my eye on it.
OK, sounds good. Let me know if you see the problem again, otherwise we'll close this out in a bit.
Package has been masked for removal - please reopen for: media-sound/logitechmediaserver-bin if still an issue there.
