Bugzilla – Bug 4506
Installed MySQL service isn't stopped or started by SlimServer
Last modified: 2008-12-18 11:11:39 UTC
In r10553 changes were made to install SlimServer's bundled MySQL as a service. One user in the forums has reported the inability to upgrade SlimServer because he couldn't overwrite the mysql.exe file, so had to go find the service applet and stop it himself. Several things about how SlimServer and the installed SlimServerMySQL service operate: When SlimServer stops, it doesn't stop the SlimServerMySQL service like it does for the bundled MySQL run as an application. For people who only run SlimServer when listening to music, this leaves an unwanted service running. It may also mean some problems, as noted above, during SlimServer upgrades. If the SlimServerMySQL service isn't running when SlimServer starts, SlimServer launches the built-in MySQL as an application instead of starting the SlimServerMySQL service. SlimServerMySQL's startup type is set to Automatic. If SlimServer _can_ start and stop the MySQL service that it installs, then it should probably be set to Manual and let SlimServer start it at startup, instead of having Windows start it up automatically.
Change 10795 fixes the following issues: * Stopping MySQL on SlimServer shutdown when MySQL is running as a service. * Stopping & removing the SlimServerMySQL service via the uninstaller. Regarding your second point: SlimServer tries to start MySQL as a service. If you can reproduce that specific behavior, please reopen this bug. I was unable to reproduce. Regarding your third point: I don't see this as an issue, and to the user, SlimServer starts up faster if MySQL is already running.
*** Bug 4559 has been marked as a duplicate of this bug. ***
I posted this on the forums, I repost it here as it might be relevant. It was the stable 6.5.1, no nightly release. 6.5.1 gave me problems, with freezing sound for fractions of a second, randomly. This on a newly formatted and reinstalled Windows machine. I decided to downgrade back to 6.3.1 and it began. First, when you uninstall the mySQL service is left running. That, in turn, means that traces of the service stay on your machine. I found out about it when, after installing 6.3.1, the service for it was constantly stopping for no reason... I went to services.msc and there I saw the SlimServerMySQL thing... how to get rid of it? I had to boot in safe mode, changing the permission on the registry entries to be able to wipe them from my machine. After I did that, reinstalled 6.3.1 and everything was ok, crossing fingers.
Just downloaded SlimServer_6.5_v2006-12-03.exe and installed it, had to stop the sql service manually for the install to work. Also, SlimServer didn't open the browser when it started. Win XP SP2.
Downloaded SlimServer_6.5_v2006-12-20.exe and it loaded without me having to do anything to MYSQL, so its fixed.