Okay, I understand the issue, so I'll try to make it as clear as possible:
Squeezebox Server comes as a Frontview plugin for the ReadyNAS units. Frontview uses its own scripts (namely /etc/rc3.d/S99rc3, /etc/rc0.d/K99powerdown and /etc/rc6.d/S99reboot) to start and stop services related to plugins, and is as such normally responsible for starting up and shutting down Squeezebox Server. The problem is that the SBS 7.4.0 addon also installs - by the mean of the squeezeboxserver debian archive it comes with - its own initialization scripts on the system. One of them, causing most of the hassle, is /etc/rc3.d/S20squeezeboxserver. The way UNIX systems work at boot time, the S20squeezeboxserver script is called before the S99rc3 one, and launches a first instance of Squeezebox Server. But, since the MySQL database server is not already started at this time (it will be launched later by the S99rc3 script), this first instance of Squeezebox Server may not be working properly (in my very own case, SBS was running, but didn't give me access to my local library). I think unavailability of the database made 7.3.3 dying, but I'm not sure anymore. Later, when the S99rc3 is called by the system, the MySQL database server is started and another instance of Squeezebox Server is launched. But this second SBS instance detects that another process is using the network ports normally used by the service (indeed, the first SBS instance is using them), and aborts (because it requires these ports to operate correctly). Because SBS is started through a "watchdog"-like script, the second SBS instance is restarted immediately, dies again because the network port are still used by the first instance, is restarted, dies ... over and over. This is what happens if you reboot your ReadyNAS. Now, deleting the S20squeezeboxserver (or renaming it to s20squeezeboxserver) prevents the first SBS instance to be started, and let the one started by Frontview bind the network ports. It's not clear to me whether/why some people had problems when no reboot was involved. As said in another post, upgrade from 7.3.3 to beta 7.4.0 went fine for me, and SBS worked like a charm... until I rebooted my ReadyNAS. What's next? I attached 2 patches to the bug report: - the first one should prevent future SBS addon builds from installing its own initialization scripts (the S20squeezeboxserver thingies) - the second one should, when the newer release of the addon (that doesn't come with these initialization scripts) is installed, take care of removing the ones that may have been installed previously Testing is needed (I don't have all the tools required to roll my own ReadyNAS build and try it on my NV+), but I'm quite confident these patches should help (or at least give good clues for) solving the problems. Other oddities would also need to be understood/corrected, like the fact that - although the SBS debian package declares it replaces and conflicts with SC - some SqueezeCenter file are still present after the SBS addon installation. -- sebp System : Mac Mini for ripping to FLAC (XLD) > Squeezebox Server 7.4 running on a ReadyNAS NV+ Living room : Transporter > NuForce IA-7 v2 > KEF iQ9 Bedroom : Squeezebox 3 > Beresford DAC > NAD C315BEE > KEF iQ3 Kitchen : SB Receiver > Trends Audio TA10.1 > Celestion F10 Bathroom : SB Boom 'Last.fm' (http://www.last.fm/user/sebp) ------------------------------------------------------------------------ sebp's Profile: http://forums.slimdevices.com/member.php?userid=11768 View this thread: http://forums.slimdevices.com/showthread.php?t=68406 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
