Bugzilla – Bug 12299
Starting SqueezeCenter fails
Last modified: 2009-06-08 06:52:07 UTC
Started since 7.4-26846 also on 7.4-26930. I'm runningon SC on a Synology Disk Station 107+ / 2.1.0-0844 (2009/04/21) with SSODS 3.17. The error message from the logfile: 0001: [09-06-04 21:21:24 ] ssctrl Starting SqueezeCenter 7.4-26846. 0002: [09-06-04 21:21:31 ] ssctrl Enabled work-around for bug #4615 (MySQL errmsg.sys). 0003: [09-06-04 21:21:31 ] ssctrl Enabled work-around for bug #4615 (MySQL errmsg.txt). 0004: [09-06-04 21:21:31 ] ssctrl Command line = /volume1/SSODS/sbin/start-stop-daemon --start --chuid admin --exec /volume1/SqueezeCenter/slimserver.pl -- --daemon --pidfile /volume1/SqueezeCenter/Cache/squeezecenter.pid --cachedir /volume1/SqueezeCenter/Cache --logdir /volume1/SqueezeCenter/Logs --prefsdir /volume1/SqueezeCenter/prefs --noupnp 0005: The following CPAN modules were found but cannot work with SqueezeCenter: 0006: Audio::Scan: 0007: Audio::Scan object version 0.13 does not match bootstrap parameter 0.15 at /volume1/SSODS/lib/perl5/5.8.8/armv5tejl-linux-thread-multi/DynaLoader.pm line 253. 0008: Compilation failed in require at (eval 32) line 2. 0009: BEGIN failed--compilation aborted at (eval 32) line 2. 0010: 0011: 0012: To fix this problem you have several options: 0013: 1. Install the latest version of the module(s) using CPAN: sudo cpan Some::Module 0014: 2. Update the module's package using apt-get, yum, etc. 0015: 3. Run the .tar.gz version of SqueezeCenter which includes all required CPAN modules. 0016: 0017: [09-06-04 21:21:39 ] ssctrl failed to start SqueezeCenter.
Please get in touch with flipflip - he'll have to updated SSODS in order to support the latest SC.
You need to update the Audio::Scan module. The log file is pretty clear about that. I think that this report does not belong here. It's not a SC bug. It's a SSODS "bug". And I wouldn't even count it as an SSODS bug since users should only use the official stable release with SSODS, which runs fine. If they want to use the trunk they should be able to read and understand the error messages and act accordingly, which in in this case is: download and install the updated module or wait until SSODS is updated. The latter will not happen before a stable release of SC is released.