Bugzilla – Bug 4706
Selecting "Stop Server" from Slimtray should stop Mysqld.exe
Last modified: 2008-12-18 11:11:58 UTC
Currently, if you click "Stop Server" via Slimtray it sometimes only shuts down SLIM.EXE. It leaves running MYSQLD.EXE. This is a problem from support standpoint if we need customers to stop the server so they can delete their database files. Windows will not allow this because MYSQLD.EXE is still accessing the files. ("Error Deleting File or Folder" - cannot delete ibdata1)
MySqld is not stopped when Slim.exe is run as a process and MySQLD.exe is started as a service owned by System and not the user. MySQLD always runs as a service and AFAICT when it is run as a service owned by the system and SLim.exe is run as a background process or service owned by the user - this bug happens. Sysinternals (now part of MS) ProcessExplorer (free) is good at showing ownership of processes and better than Task manager for this sort of diagnostic. Slimserver can be started in 3 ways and each should be a test case. 1. Automatic on startup - Slim.EXE and MYSQLD.exd are both system services. Stopping SLim.exe also stop MySqld. 2. Automatic on login - Slim.exe is a user service and MySqld is a user service. Can't be sure if stopping SLim.exe also stops MySQld. 3. Installed as Automatic on startup but either on installation (ie. do no start auomatically) or separately afterwards when Slim.exe service is disabled from Services control panel and then system rebooted. Slimserver then needs to be started manually from SlimTray - in this case MySqld is a service owned by System and but Slim.exe is a background process owned by user. MySQld will not stop when Slim.exe is stopped. Furthermore, there is a slight change in behaviour (i.e. ownership of process/service) if in cases 2 & 3 Slimserver is stopped and then restarted. So what happens to MySQLD upon Slimserver stopping, after Slimserver has been stopped and restarted manually, also needs to be a test case. For 6.5.x my patch for bug 4762 to SlimTray will shutdown MySQLD if it is still running after Slim.exe has stopped in all circumstances by issuing s "Stop Service" if MySQLD service is running. In 7.0 this bugs has been fixed by adding "Stop Service" into Slimserver (see svn 10795). From a support point of view - the patched SlimTray can be installed separately from Slimserver so that if support is chasing a bug in Slimserver, SlimTray can be updated without altering Slimserver and/or its files.
Chris, this should be fixed in 6.5.2 with the latest slimtray, correct?
correct!
*** This bug has been marked as a duplicate of 4763 ***
Fixed in 6.5.2, which is now released and available for download at http://www.slimdevices.com/su_downloads.html If you're still experiencing this bug, please re-open it!