Bugzilla – Bug 12977
SC will not start
Last modified: 2009-10-30 15:37:55 UTC
Created attachment 5501 [details] Server log Squeezecenter will not start on the customer’s Windows XP- Pro machine. SC tries to start but after a few seconds it dies. -Uninstalled the antivirus -Uninstalled My SQL client software -Uninstalled Cygwin -Windows Firewall turned off -Tried SC 7.3.4 -Cleaned all the PDK* -Changed the HHTPPORT from 9000 to 10050 SC on both version still behaving the same way, it tries to start but after a few seconds it stops. Included log files for -The normal server log file -The server debug log file from command line -Windows application event log, -Windows system event log RN = 090616-004186
Created attachment 5502 [details] Squeezecenter log
Created attachment 5503 [details] Windows application event log
Created attachment 5504 [details] Windows system event log
There is already another copy of the SqueezeCenter running on this machine. (Unknown error) at /<C:\PROGRA~1\SQUEEZ~1\server\SQUEEZ~1.EXE>Slim/Networking/UDP.pm line 39 This error shows up every few minutes in the application event viewer log. Is this one helpful: The following information is part of the event: Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them Osama did you try having the customer uninstall SqueezeCenter and ensure that it has been completely removed before reinstalling? Andy, anything useful from the UDP.pm error?
Ross We have done clean install about 15 times with different versions of SC 7.3.3, 7.3.4 and 7.4.
Osama are you 100% certain the customer removed everything SqueezeCenter related from his system before trying to install again? The install directory and prefs are all double checked to be removed. No previous SlimServer or SqueezeCenter files can be found on the system? The error seems to indicate this isn't the case: There is already another copy of the SqueezeCenter running on this machine. (Unknown error) at /<C:\PROGRA~1\SQUEEZ~1\server\SQUEEZ~1.EXE>Slim/Networking/UDP.pm line 39
That error may occur, if the system has not been Rebooted after 'uninstall' Make sure to uninstall, reboot, verify complete removal
Yes, we've done that. To be sure, I just uninstalled, checked for left overs, rebooted and reinstalled... Still no joy.
> Yes, we've done that. To be sure, I just uninstalled, checked for left overs, > rebooted and reinstalled... Still no joy. What if you don't reinstall? Do you see anything squeeze* in the task manager? If you open a DOS window (cmd.exe) and run the following command: netstat -ab do you see something using port 3483? What exact SC build are you trying to run?
No, there is nothing in task manager with Squeeze in it. Looking at netstat there is nothing using port 3483. I've tried several, but most recently I've used 7.3.3 v 27044, downloaded from this page - http://www.logitechsqueezebox.com/support/download-squeezecenter.html
Do you have any other MySQL instances? Can you think of anything else to share about this system that could help us diagnose this?
I can't think of anything that's running any kind of SQL server on this machine. I run SQLyog as a client, but only use it to connect to web servers on the net. I have Cygwin installed, but didn't install MySQL with it. There's nothing else installed on this box, that I can think of, that would interfere with SQL or PERL. What about SETI @ home/BIONIC? I don't know what they use to process and store job tasks.... If you want to connect to the box remotely with VNC or something similar, to poke around, I don't have a problem with that.
Any progress on this issue? I'd love to use this product as intended, but if I can't use it I'll have to return it.
Eric I don't have any solution for you right this minute. I'm not even sure this is a bug in our software since nobody else is seeing this, and I'm sure if it were a bug many people would be reporting it. This leads me to believe it's isolated to your system, and I'm afraid I won't have time to VNC into your machine to have a look, thank you for the offer though. Can you reproduce this on any other computers?
Eric - did you recently update your Windows? I think there's been an issue with some SP/patch where SC wouldn't be allowed to use some ports. Do you run a DNS on that machine by chance?
(In reply to comment #15) > Eric - did you recently update your Windows? I think there's been an issue with > some SP/patch where SC wouldn't be allowed to use some ports. Do you run a DNS > on that machine by chance? Windows updates automatically, I don't know of anything in particular. I do not run DNS on this machine. I have run your troubleshooter.exe and it appears the ports are ok... Probing Ports -> Port 9000: ok -> Port 9090: ok -> Port 3483: ok List of processes known to potentially cause issues with SqueezeCenters -> AVGRSX: AVG Resident Shield Service -> AVGWDSVC: AVG Watchdog Service
> List of processes known to potentially cause issues with SqueezeCenters > -> AVGRSX: AVG Resident Shield Service > -> AVGWDSVC: AVG Watchdog Service Sound like firewalls to me. Did you configure them to allow incoming traffing on ports 9000, 9090 and 3438?
(In reply to comment #17) > > List of processes known to potentially cause issues with SqueezeCenters > > -> AVGRSX: AVG Resident Shield Service > > -> AVGWDSVC: AVG Watchdog Service > > Sound like firewalls to me. Did you configure them to allow incoming > traffing on ports 9000, 9090 and 3438? Osama had me uninstall AVG & Spybot, and turn off the firewall several times during our many uninstalls, reinstalls... And, there are lots of exception entries in the firewall for SqueezeCenter. 1000 tcp 3483 tcp 3483 udp 8000 tcp 9000 - 9010 tcp 9090 tcp 9100 tcp
(In reply to comment #18) > (In reply to comment #17) > > > List of processes known to potentially cause issues with SqueezeCenters > > > -> AVGRSX: AVG Resident Shield Service > > > -> AVGWDSVC: AVG Watchdog Service > > > > Sound like firewalls to me. Did you configure them to allow incoming > > traffing on ports 9000, 9090 and 3438? > > Osama had me uninstall AVG & Spybot, and turn off the firewall several times > during our many uninstalls, reinstalls... And, there are lots of exception > entries in the firewall for SqueezeCenter. Even with the applications uninstalled our troubleshooter still gives those messages? Wouldn't that imply they're actually not completely uninstalled?
(In reply to comment #19) > (In reply to comment #18) > > (In reply to comment #17) > > > > List of processes known to potentially cause issues with SqueezeCenters > > > > -> AVGRSX: AVG Resident Shield Service > > > > -> AVGWDSVC: AVG Watchdog Service > > > > > > Sound like firewalls to me. Did you configure them to allow incoming > > > traffing on ports 9000, 9090 and 3438? > > > > Osama had me uninstall AVG & Spybot, and turn off the firewall several times > > during our many uninstalls, reinstalls... And, there are lots of exception > > entries in the firewall for SqueezeCenter. > > Even with the applications uninstalled our troubleshooter still gives those > messages? Wouldn't that imply they're actually not completely uninstalled? No, it would imply that I have since reinstalled them and I ran the troubleshooter app with them in place simply to show you that the ports are still open. If you have specific instructions as to what to try I'll be happy to. But your first level tech support did have me go through all the basics of uninstalling all security programs, turning off the firewall and installing, both with and without restarts. Is there anything new to try? Thanks, Eric
(In reply to comment #20) > Is there anything new to try? No. This is a bug report not a support forum, we've suggested what should resolve this. I don't believe this is a bug, I'm sure if you would try this on another PC you would agree it's an issue specific to this machine. Try running our trouble shooter without your anti-virus installed, maybe that will give some other clue. The repeating errors in your event log show that SqueezeCenter is not being completely uninstalled, take a closer look and double-check it is thoroughly removed before re-installing. Is there anything else that you could share with us about this system that could give us a hint about why this is happening? I'm noticing lots of errors in your event log, is this system having other issues that could be related?
this is clearly a support issue, QA is unable to assist further. Closing this bug