Bugzilla – Bug 10040
SqueezeCenter 7.x.x doesn't start as service
Last modified: 2009-02-24 15:35:17 UTC
Currently running SqueezeCenter 7.2.1 to start as a service, on Windows XP Pro SP3 (with all updates). Sometimes SqueezeCenter doesn't start when the machine boots up. This problem began after updateding from SlimServer 6 to SqueezeCenter 7.0. This was a clean install, i.e., uninstalled SlimServer 6 and deleted all related folders. The problem reappears with each SqueezeCenter upgrade, thru 7.2.1. I've gone to the service Recovery tab on both the SqueezeMySQL and SqeezeCenter services and set failures to “Restart the Service.” That improved the reliability of SqueezeCenter starting properly on boot up, but it still occasionally failed. When SqueezeCenter failed to start, I noticed that the SqueezeMySQL service was hung. As installed, neither the SqueezeCenter service nor the SqueezeMySQL service have any dependencies. They start whenever. I figured that some other startup program was occasionally interfering. To solve the problem, I make the SqueezeCenter service dependent on the SqueezeMySQL service, and make SqueezeMySQL service dependent on the Messenger service. This way, SqueezeCenter starts after SqueezeMySQL starts, and SqueezeMySQL starts after most other start up services have started. Consequently, SqueezeMySQL and SqueezeCenter don't getting interrupted by some other startup program (e.g., by my anti-virus) and don't hang. Here are the procedures I follow: • Run Regedit and go to HKLM\system\currentcontrolset\services\ • Click on squeezesvc. Right click and select NEW -> Multi-String Value. Name it DependOnService. Double click on the item and in the Value Data box SqueezeMySQL. • Click on SqueezeMySQL. Right click and select NEW -> Multi-String Value. Name it DependOnService. Double click on the item and in the Value Data box, enter Messenger. (I make sure that the Messenger service is configured to start automatically.) • Reboot. Reference Microsoft KB 193888 "How to delay loading of specific services." I chose the Messenger service because it is one of the last to start during normal bootup (per the KB article). If the computer were hooked directly to the internet (and not behind a router), I'd have to use a different service because a PC directly connected to the internet would risk Messenger spam (if that service were started automatically). When I update SqueezeCenter to a new version, I have to re-enter the above registry entries. Mac
SC doesn't need MySQL to be running when it's started. It will start it itself if needed. Could you please give us some information about how it failed starting?
". . . how it failed starting?" I'm not sure if "it" refers to MySQL or squeezecenter, but, in either case, I have not identified a cause for either the MySQL or the squeezecenter service failing to start, only that they would intermittently fail. Whenever squeezecenter failed to start on boot-up, I noticed that (1) the squeezecenter service was not started, and that (2) the MySQL service was hung. Whenever the MySQL service hung, I have been unable to manually start, re-start, or stop the MySQL service, either as a user or as an administrator. To gain control, I had to reboot Windows XP Pro. Whenever it failed to automatically start, I have always been able to manually start the squeezecenter service. (As part of squeezecenter startup options, the squeezecenter service was set up to use an administrator login and password). Since MySQL was always hung whenever squeezecenter failed to start, I assumed a relationship. Starting the squeezecenter service manually did not seem to be a satisfactory procedure to me. Since the failure to start was intermittent, I assumed some other process must occasionally interfere. Squeezecenter had no trouble starting IF I waited a minute or so to log in after bootup; this seemed to confirm my assumption that another process was interrupting, and that the process was part of the log in. E.g., immediately upon log in, my anti-virus (ESET NOD32) connects with its home base for signature updates. In order to avoid the intermittent failure of squeezecenter to start, I structured the dependencies described in my bug report. It works. Would you like me to unstructure the dependencies and collect a log report the next time SC fails to start?
Thanks for the update. > Whenever the MySQL service hung, I have been unable to manually start, > re-start, or stop the MySQL service, either as a user or as an > administrator. To gain control, I had to reboot Windows XP Pro. This sound like a good reason for SC to fail. Do you still have server.log from one of these events (see Settings/Status for the file path)?
[08-11-16 13:05:50.6096] Slim::Schema::Storage::throw_exception (70) Error: DBI Connection failed: DBI connect('hostname=127.0.0.1;port=9092;database=slimserver','slimserver',...) failed: Can't connect to MySQL server on '127.0.0.1' (10061) at /<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>DBIx/Class/Storage/DBI.pm line 652 [08-11-16 13:05:50.6116] Slim::Schema::Storage::throw_exception (70) Backtrace: frame 0: Slim::Utils::Log::logBacktrace (C:/Program Files/SqueezeCenter/server/Slim/Schema/Storage.pm line 70) frame 1: Slim::Schema::Storage::throw_exception (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>DBIx/Class/Storage/DBI.pm line 658) frame 2: DBIx::Class::Storage::DBI::_connect (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>DBIx/Class/Storage/DBI.pm line 616) frame 3: DBIx::Class::Storage::DBI::_populate_dbh (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>DBIx/Class/Storage/DBI.pm line 543) frame 4: DBIx::Class::Storage::DBI::ensure_connected (C:/Program Files/SqueezeCenter/server/Slim/Schema/Storage.pm line 29) frame 5: (eval) (C:/Program Files/SqueezeCenter/server/Slim/Schema/Storage.pm line 29) frame 6: Slim::Schema::Storage::dbh (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>Slim/Schema.pm line 131) frame 7: Slim::Schema::init (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>Slim/Music/Info.pm line 76) frame 8: Slim::Music::Info::init (slimserver.pl line 368) frame 9: main::init (slimserver.pl line 42) frame 10: PerlSvc::Startup (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>PerlSvc.pm line 95) frame 11: PerlSvc::_startup (slimserver.pl line 0) frame 12: (eval) (slimserver.pl line 0) [08-11-16 13:05:50.6253] Slim::Schema::init (134) Error: Couldn't connect to database! Fatal error: [Bad file descriptor] Exiting! [08-11-16 13:05:50.6258] Slim::Schema::init (134) Backtrace: frame 0: Slim::Utils::Log::logBacktrace (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>Slim/Schema.pm line 134) frame 1: Slim::Schema::init (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>Slim/Music/Info.pm line 76) frame 2: Slim::Music::Info::init (slimserver.pl line 368) frame 3: main::init (slimserver.pl line 42) frame 4: PerlSvc::Startup (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>PerlSvc.pm line 95) frame 5: PerlSvc::_startup (slimserver.pl line 0) frame 6: (eval) (slimserver.pl line 0) [08-11-16 13:05:50.6263] Slim::Schema::forceCommit (1487) Warning: Trying to commit transactions before DB is initialized!
The above log entry, dated 08-11-16, would make it seem I haven't really tested my "fix." But let me explain. I came up with this dependency "fix" shortly after upgrading to SqueezeCenter 7. I have updated squeezecenter with each new release. As noted in my initial report, the update overwrites my dependency "fix" so that both the squeezecenter service and the MySQL service revert back to having no dependencies. After updating, I do not hack my registry to invoke dependencies until the problem (squeezecenter failing to start on bootup) reappears. Whenever I update I assume that the problem may have gone away. After updating to version 7.2.1, it took awhile before the problem reappeared. Even though the log entry is recent, I've been using this "fix" ever since Squeezecenter 7 was released. Mac
I seem to be seeing something similar to this. I have XP Home SP3 with SqueezeCenter running as a service. My machine hops in and out of standby using WOL. Everything is usually fine but every now and then, the Squeezecenter won't start up and when I go to the server machine I see the service stopped. Starting the service manually gets it going fine. This is an extract from the log which corresponds to the last time I saw this: [08-11-18 08:27:09.9377] Slim::Networking::Async::DNS::resolve (208) DNS server 192.168.1.254 couldn't resolve IP address for www.squeezenetwork.com: Send: Unknown error [08-11-18 08:28:41.2346] Slim::Schema::Storage::throw_exception (70) Error: DBI Connection failed: DBI connect('hostname=127.0.0.1;port=9092;database=slimserver','slimserver',...) failed: Can't connect to MySQL server on '127.0.0.1' (10061) at /<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>DBIx/Class/Storage/DBI.pm line 652 [08-11-18 08:28:41.3027] Slim::Schema::Storage::throw_exception (70) Backtrace: frame 0: Slim::Utils::Log::logBacktrace (C:/Program Files/SqueezeCenter/server/Slim/Schema/Storage.pm line 70) frame 1: Slim::Schema::Storage::throw_exception (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>DBIx/Class/Storage/DBI.pm line 658) frame 2: DBIx::Class::Storage::DBI::_connect (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>DBIx/Class/Storage/DBI.pm line 616) frame 3: DBIx::Class::Storage::DBI::_populate_dbh (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>DBIx/Class/Storage/DBI.pm line 543) frame 4: DBIx::Class::Storage::DBI::ensure_connected (C:/Program Files/SqueezeCenter/server/Slim/Schema/Storage.pm line 29) frame 5: (eval) (C:/Program Files/SqueezeCenter/server/Slim/Schema/Storage.pm line 29) frame 6: Slim::Schema::Storage::dbh (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>Slim/Schema.pm line 131) frame 7: Slim::Schema::init (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>Slim/Music/Info.pm line 76) frame 8: Slim::Music::Info::init (slimserver.pl line 368) frame 9: main::init (slimserver.pl line 42) frame 10: PerlSvc::Startup (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>PerlSvc.pm line 95) frame 11: PerlSvc::_startup (slimserver.pl line 0) frame 12: (eval) (slimserver.pl line 0) [08-11-18 08:28:41.3926] Slim::Schema::init (134) Error: Couldn't connect to database! Fatal error: [Bad file descriptor] Exiting! [08-11-18 08:28:41.3933] Slim::Schema::init (134) Backtrace: frame 0: Slim::Utils::Log::logBacktrace (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>Slim/Schema.pm line 134) frame 1: Slim::Schema::init (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>Slim/Music/Info.pm line 76) frame 2: Slim::Music::Info::init (slimserver.pl line 368) frame 3: main::init (slimserver.pl line 42) frame 4: PerlSvc::Startup (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>PerlSvc.pm line 95) frame 5: PerlSvc::_startup (slimserver.pl line 0) frame 6: (eval) (slimserver.pl line 0) [08-11-18 08:28:41.3939] Slim::Schema::forceCommit (1487) Warning: Trying to commit transactions before DB is initialized!
One more point. I THOUGHT that this occurs when I come out of standby. But, in retrospect, that is not so clear. It's possible it only occurs on reboots. Sorry for the confusion but the problem is intermittent and when I WOL it's not obvious if the machine boots or returns from standby since both cases behave similarly and I can't necessarily remember if the machine was on or off before...
QA to investigate and reproduce
Squeezecenter should start mysql when it launches. Are you theorizing that the problem is that SC is not successfully launching mysql at run-time? Or are you finding that after sleep there is a Squeezecenter process but no mysql and SC doesn't work? What is the symptom you are experiencing when you try to use the product, and maybe we can approach this from that angle? Thanks!
(In reply to comment #9) > What is the symptom you are experiencing when you try to use the product, and > maybe we can approach this from that angle? I find I cannot do my usual thing and wake the server on lan. In fact the server does wake but the SqueezeBox cannot find the SqueezeCenter. I (go upstairs and) log on to the server and find no SqueezeCenter running even though it is set to start on boot. Starting SqueezeCenter then works fine. Ben
Bob: Please try the following, report back if this helps or not. 1) run the clean up tool -- C:\Program Files\SqueezeCenter\server\Cleanup.exe 2) please do (1) delete preference files 3) run the ServiceEnabler tool -- C:\Program Files\SqueezeCenter\ServiceEnabler.exe 4) select Start SqueezeCenter automatically when the computer starts. Make sure you provide logon credentials for an Admin level account. 5) reboot your system 6) wait at least 5 min for the system to boot and SC to start 7) try attaching a Player to SC running on the system above
I've recently upgraded from 7.2.1 to 7.3 with SqueezeCenter running automatically when the computer starts with Admin logon credentials. The dependency scheme described in the original post has not been implemented because SqueezeCenter is performing as advertised at this time. If I begin to experience startup malfunctions, I will employ the steps outlined in comment #11 and report the results.
Based on comment 12, I will mark this bug as fixed. If you have any further issues with 7.3, please reopen the bug and add new comments.
Verified to be working in 7.3.2 - 24638. SC starts as a service.
I'm running nightly 7.3.2 - 24695 and I'm still getting this bug. Last time I booted the machine I noticed that the SqueezeCenter service did not start. I checked in the services console and found the MySQL service had status "Stopping". Starting the SqueezeCenter service worked fine. The log is shown below. I'm running XP SP3 (with all updates). PS I'm attaching this comment though the bug shows as fixed. I don't know how to reopen the bug. [09-01-22 07:57:58.3127] Slim::Schema::Storage::throw_exception (70) Error: DBI Connection failed: DBI connect('hostname=127.0.0.1;port=9092;database=slimserver','slimserver',...) failed: Can't connect to MySQL server on '127.0.0.1' (10061) at /<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>DBIx/Class/Storage/DBI.pm line 652 [09-01-22 07:57:58.3648] Slim::Schema::Storage::throw_exception (70) Backtrace: frame 0: Slim::Utils::Log::logBacktrace (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>Slim/Schema/Storage.pm line 70) frame 1: Slim::Schema::Storage::throw_exception (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>DBIx/Class/Storage/DBI.pm line 658) frame 2: DBIx::Class::Storage::DBI::_connect (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>DBIx/Class/Storage/DBI.pm line 616) frame 3: DBIx::Class::Storage::DBI::_populate_dbh (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>DBIx/Class/Storage/DBI.pm line 543) frame 4: DBIx::Class::Storage::DBI::ensure_connected (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>Slim/Schema/Storage.pm line 29) frame 5: (eval) (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>Slim/Schema/Storage.pm line 29) frame 6: Slim::Schema::Storage::dbh (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>Slim/Schema.pm line 132) frame 7: Slim::Schema::init (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>Slim/Music/Info.pm line 77) frame 8: Slim::Music::Info::init (slimserver.pl line 369) frame 9: main::init (slimserver.pl line 41) frame 10: PerlSvc::Startup (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>PerlSvc.pm line 95) frame 11: PerlSvc::_startup (slimserver.pl line 0) frame 12: (eval) (slimserver.pl line 0) [09-01-22 07:57:58.4200] Slim::Schema::init (135) Error: Couldn't connect to database! Fatal error: [Bad file descriptor] Exiting! [09-01-22 07:57:58.4206] Slim::Schema::init (135) Backtrace: frame 0: Slim::Utils::Log::logBacktrace (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>Slim/Schema.pm line 135) frame 1: Slim::Schema::init (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>Slim/Music/Info.pm line 77) frame 2: Slim::Music::Info::init (slimserver.pl line 369) frame 3: main::init (slimserver.pl line 41) frame 4: PerlSvc::Startup (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>PerlSvc.pm line 95) frame 5: PerlSvc::_startup (slimserver.pl line 0) frame 6: (eval) (slimserver.pl line 0) [09-01-22 07:57:58.4212] Slim::Schema::forceCommit (1482) Warning: Trying to commit transactions before DB is initialized!
I followed the steps in Comment #11 - deleting my preferences and re-enabling the service and the SqueezeCenter started correctly upon reboot. I will monitor future reboots and report back if the issue recurs.
No, it's still happening - it has just done it again. Here's the log: [09-01-24 23:14:29.6096] Slim::Schema::Storage::throw_exception (70) Error: DBI Connection failed: DBI connect('hostname=127.0.0.1;port=9092;database=slimserver','slimserver',...) failed: Can't connect to MySQL server on '127.0.0.1' (10061) at /<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>DBIx/Class/Storage/DBI.pm line 652 [09-01-24 23:14:29.6584] Slim::Schema::Storage::throw_exception (70) Backtrace: frame 0: Slim::Utils::Log::logBacktrace (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>Slim/Schema/Storage.pm line 70) frame 1: Slim::Schema::Storage::throw_exception (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>DBIx/Class/Storage/DBI.pm line 658) frame 2: DBIx::Class::Storage::DBI::_connect (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>DBIx/Class/Storage/DBI.pm line 616) frame 3: DBIx::Class::Storage::DBI::_populate_dbh (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>DBIx/Class/Storage/DBI.pm line 543) frame 4: DBIx::Class::Storage::DBI::ensure_connected (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>Slim/Schema/Storage.pm line 29) frame 5: (eval) (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>Slim/Schema/Storage.pm line 29) frame 6: Slim::Schema::Storage::dbh (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>Slim/Schema.pm line 132) frame 7: Slim::Schema::init (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>Slim/Music/Info.pm line 77) frame 8: Slim::Music::Info::init (slimserver.pl line 369) frame 9: main::init (slimserver.pl line 41) frame 10: PerlSvc::Startup (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>PerlSvc.pm line 95) frame 11: PerlSvc::_startup (slimserver.pl line 0) frame 12: (eval) (slimserver.pl line 0) [09-01-24 23:14:29.6847] Slim::Schema::init (135) Error: Couldn't connect to database! Fatal error: [Bad file descriptor] Exiting! [09-01-24 23:14:29.7493] Slim::Schema::init (135) Backtrace: frame 0: Slim::Utils::Log::logBacktrace (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>Slim/Schema.pm line 135) frame 1: Slim::Schema::init (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>Slim/Music/Info.pm line 77) frame 2: Slim::Music::Info::init (slimserver.pl line 369) frame 3: main::init (slimserver.pl line 41) frame 4: PerlSvc::Startup (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>PerlSvc.pm line 95) frame 5: PerlSvc::_startup (slimserver.pl line 0) frame 6: (eval) (slimserver.pl line 0) [09-01-24 23:14:29.7499] Slim::Schema::forceCommit (1482) Warning: Trying to commit transactions before DB is initialized!
Can you start the SqueezeMySQL service from Windows' service management console (run services.msc)? Could you please upload your my.cnf (in SC's cache folder) and mysql-error-log.txt (or similar)? And you didn't by chance ever try to run SC from some external disk or something?
Created attachment 4707 [details] "my" file from SqueezeCEnter Cache directory
Created attachment 4708 [details] mysql-error.log
(In reply to comment #18) > Can you start the SqueezeMySQL service from Windows' service management console > (run services.msc)? No. The service shows as "stopping" and I am not given the option to start it. > Could you please upload your my.cnf (in SC's cache folder) > and mysql-error-log.txt (or similar)? OK. Done. > And you didn't by chance ever try to run SC from some external disk or > something? Now you may be on to something! I have my music folder and playlist folder on a drive which is not absolutely always online. The drive is on a separate controller. It IS online on the occasions when I get this problem since I can start SqueezeCenter fine once I am logged on. But a vaguely possible explanation is that the disk might have been offline on the PREVIOUS boot. SO then maybe when the MySQL service tries to start on the good boot it triggers some sort of race because it's doing recovery for the previous boot. or some other dubious speculation....:-) HTH
What kind of drive is E:?
(In reply to comment #22) > What kind of drive is E:? > E: is a partition on the same drive as C: It is always present. N: (where the music folder is) is on a separate controller. On odd occasions this extra controller fails to initialise properly when the computer comes out of standby (or on boot). When I reboot it's always fine. It may be (but I'm not sure) that the MySQL service only fails to start on those occasions when I reboot after the extra controller doesn't initialise. Or it might be unconnected... the TEMP path variable points to the same disk as N: and some swap is there too.
> E: is a partition on the same drive as C: That should be fine. > the TEMP path variable points to the same disk as N: and some swap is there > too. Could you please change this so these always point to c: or e: (or whatever drive doesn't make trouble) and see whether this changes the behaviour?
FWIW, I have the same problem as the OP. I am running 7.2.1 - 23630 on XP SP2. When I first installed SC7 I ran the tool that sets up SC to run as a service (I had previously run 6.5 as a service without any problems.) I don't think SC has ever successfully started up. I always have to start the service manually (by going into services, etc.) Until reading this thread, I hadn't looked too closely at it (I don't reboot that often.) I notice the same thing the OP reported: that SqueezeCenterMySQL reports "Stopping" under Services and it can not be stopped or restarted. Squeezecenter can be started from services just fine, and mySQL is called and runs just fine too (appears as a process under Task Manager.) I don't know if it's related, but I do find that mySQL always runs when SC starts and eats up alot of CPU time (80-100%) for 2-3 mins until SC becomes responsive.
> I notice the same thing the OP > reported: that SqueezeCenterMySQL reports "Stopping" under Services and it can > not be stopped or restarted. I tried altering the dependencies as suggested by the OP. SC still won't start properly on startup, however SqueezeCenterMySQL no longer reports "sTopping" on the services tap, instead it is happily running. A portion of server.log is below. > I don't know if it's related, but I do find that mySQL always runs when SC > starts and eats up alot of CPU time (80-100%) for 2-3 mins until SC becomes Actually, it's only 10-20% (he says looking sheepish.) [09-01-26 23:04:23.9846] Slim::Schema::Storage::throw_exception (70) Error: DBI Connection failed: DBI connect('hostname=127.0.0.1;port=9092;database=slimserver','slimserver',...) failed: Can't connect to MySQL server on '127.0.0.1' (10061) at /<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>DBIx/Class/Storage/DBI.pm line 652 [09-01-26 23:04:24.0060] Slim::Schema::Storage::throw_exception (70) Backtrace: frame 0: Slim::Utils::Log::logBacktrace (C:/Program Files/SqueezeCenter/server/Slim/Schema/Storage.pm line 70) frame 1: Slim::Schema::Storage::throw_exception (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>DBIx/Class/Storage/DBI.pm line 658) frame 2: DBIx::Class::Storage::DBI::_connect (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>DBIx/Class/Storage/DBI.pm line 616) frame 3: DBIx::Class::Storage::DBI::_populate_dbh (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>DBIx/Class/Storage/DBI.pm line 543) frame 4: DBIx::Class::Storage::DBI::ensure_connected (C:/Program Files/SqueezeCenter/server/Slim/Schema/Storage.pm line 29) frame 5: (eval) (C:/Program Files/SqueezeCenter/server/Slim/Schema/Storage.pm line 29) frame 6: Slim::Schema::Storage::dbh (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>Slim/Schema.pm line 131) frame 7: Slim::Schema::init (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>Slim/Music/Info.pm line 76) frame 8: Slim::Music::Info::init (slimserver.pl line 368) frame 9: main::init (slimserver.pl line 42) frame 10: PerlSvc::Startup (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>PerlSvc.pm line 95) frame 11: PerlSvc::_startup (slimserver.pl line 0) frame 12: (eval) (slimserver.pl line 0) [09-01-26 23:04:24.0071] Slim::Schema::init (134) Error: Couldn't connect to database! Fatal error: [Bad file descriptor] Exiting!
Did any of you ever install SC on a removable drive or a network share? I think I've recently hit an issue with XP refusing to start a service from a "non-trusted" drive, when I tried to run it off a network share. Could this be the case for any of you?
Googling around for this issue I came across that "Trust No Exe" app. It's intended to black-/whitelist executables. Could any of you try it, making sure all SC related executables (most of all squeezecenter.exe and mysqld.exe) are on its white list?
http://www.beyondlogic.org/solutions/trust-no-exe/trust-no-exe.htm
I am original poster. Since upgrading to version 7.3 in December 2008, both SqueezeCenter service and SqueezeMySQL service start normally (as a service) on boot up. I upgraded to 7.3.1 and 7.3.2 when they were released. I have made no registry hacks since upgrading to 7.3, but I have changed the "Recovery" tab items from "Take No Action" to "Restart the Service." SqueezeCenter has always been installed at (and run from) C:\Program Files\SqueezeCenter. My music files are stored on an external Western Digital hard drive connected to the PC via USB 2.0 and is always started on boot up. The server log is clean since upgrading to SqueezeCenter version 7.3 except for a couple entries like this one on Jan 14th: [09-01-14 13:48:36.5220] Slim::Schema::Storage::throw_exception (70) Backtrace: frame 0: Slim::Utils::Log::logBacktrace (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>Slim/Schema/Storage.pm line 70) frame 1: Slim::Schema::Storage::throw_exception (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>DBIx/Class/Storage/DBI.pm line 658) frame 2: DBIx::Class::Storage::DBI::_connect (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>DBIx/Class/Storage/DBI.pm line 616) frame 3: DBIx::Class::Storage::DBI::_populate_dbh (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>DBIx/Class/Storage/DBI.pm line 543) frame 4: DBIx::Class::Storage::DBI::ensure_connected (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>Slim/Schema/Storage.pm line 29) frame 5: (eval) (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>Slim/Schema/Storage.pm line 29) frame 6: Slim::Schema::Storage::dbh (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>Slim/Schema.pm line 131) frame 7: Slim::Schema::init (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>Slim/Music/Info.pm line 76) frame 8: Slim::Music::Info::init (slimserver.pl line 367) frame 9: main::init (slimserver.pl line 40) frame 10: PerlSvc::Startup (/<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>PerlSvc.pm line 95) frame 11: PerlSvc::_startup (slimserver.pl line 0) frame 12: (eval) (slimserver.pl line 0)
(In reply to comment #24) > > the TEMP path variable points to the same disk as N: and some swap is there > > too. > > Could you please change this so these always point to c: or e: (or whatever > drive doesn't make trouble) and see whether this changes the behaviour? The problem is rather intermittent so the testing is not thorough. But it has happened again and this time SqueezeCenter has started fine. So it looks like this was the fix for me. Thanks.