Bug 12427 - SqueezeCenter fails to auto-start when configured as a service
: SqueezeCenter fails to auto-start when configured as a service
Status: RESOLVED WORKSFORME
Product: Logitech Media Server
Classification: Unclassified
Component: Windows Service
: 7.3.2
: PC Windows Home Server
: -- normal (vote)
: Investigating
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-06-17 13:36 UTC by blevidow
Modified: 2011-05-30 00:24 UTC (History)
0 users

See Also:
Category: ---


Attachments
Screenshot of service registratoin and startup (39.94 KB, image/png)
2009-06-17 13:36 UTC, blevidow
Details
Registry dump for MySQL service (5.79 KB, text/plain)
2009-06-17 21:25 UTC, blevidow
Details
Registry dump for Squeeze service (5.86 KB, text/plain)
2009-06-17 21:26 UTC, blevidow
Details
Event log of service failure after reboot (3.49 KB, text/plain)
2009-06-17 21:48 UTC, blevidow
Details

Note You need to log in before you can comment on or make changes to this bug.
Description blevidow 2009-06-17 13:36:42 UTC
Created attachment 5342 [details]
Screenshot of service registratoin and startup

I've installed SqueezeCenter 7.3.2 and selected the startup item to make it start as a service.  The service control manager says that it is a startup service.

Expected behavior:
When a reboot happens, both services start up automatically so that I can continue to play my music

Actual Behavior:
When a reboot happens, the services do not start automatically.  Starting the services manually from the command line using Net Start initially fails but eventually succeeds.
Comment 1 Michael Herger 2009-06-17 15:07:25 UTC
The windows event log might tell you the reason why it's failing. How didyou configure the service? I am not sure whether the admin is allowed to run as a service.
Comment 2 blevidow 2009-06-17 21:25:28 UTC
Created attachment 5346 [details]
Registry dump for MySQL service

Here is the export of the MySQL service information from the registry
Comment 3 blevidow 2009-06-17 21:26:42 UTC
Created attachment 5347 [details]
Registry dump for Squeeze service

Here is the registry dump of the SqueezeSvc from the machine.
Comment 4 blevidow 2009-06-17 21:48:14 UTC
Created attachment 5348 [details]
Event log of service failure after reboot

From the event log, it appears that the two instances of the SqueezeCenter are starting up and one is failing, then the MySql service stops and the second instance of SqueezeCenter fails.

Part of the problem is that the SqueezeCenter service is not registered as dependent on the MySql service so that their startup order isn't guaranteed.  I've attached the relevant eventlog entries.
Comment 5 Michael Herger 2009-06-18 00:03:55 UTC
I don't see any sign of failure. The service control as well as the log file says that SC was running. Why would you think it didn't start?

You should probably contact support. SC is running as a service perfectly fine on hundreds if not thousands of installations. It rather looks as if some of your system's configuration would block access to it or similar. Support should be able to sort this out for you.
Comment 6 James Richardson 2009-06-22 10:15:04 UTC
To get in contact with our support team:

Support phone: 1-877-887-8889
Support e-mail: support@slimdevices.com
Support hours: 6am - 8pm Pacific time

Please let them know that you have an open Bug Report and provide them with the bug number.
Comment 7 Anoop Mehta 2009-10-08 13:36:46 UTC
Blevidow,

Have you contacted support?

If so what is your Incident #?
Comment 8 blevidow 2009-10-08 16:02:47 UTC
No, I have not but this problem seems to be fixed with 7.4.  Thanks!

Bj�rn


-----Original Message-----
From: bugs@bugs.slimdevices.com [mailto:bugs@bugs.slimdevices.com] 
Sent: Friday, October 09, 2009 4:37 AM
To: blevidow@hotmail.com
Subject: [Bug 12427] SqueezeCenter fails to auto-start when configured as a
service

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



--- Comment #7 from Anoop Mehta <anoop@slimdevices.com> 2009-10-08 13:36:46
PDT ---
Blevidow,

Have you contacted support?

If so what is your Incident #?
Comment 9 Anoop Mehta 2009-10-08 16:22:50 UTC
Excellent...thanks for sharing. 

Closing this bug as fixed. 

If you see this issue please re open the bug.