Bugzilla – Bug 4860
6.5.2: SlimServer does not start automatically after reboot.
Last modified: 2009-09-08 09:21:52 UTC
Steps to Reproduce: 1. On a clean ghost of Vista SP0 ENU, install SlimServer 6.5.2, build 2007-03-26. 2. During the install, make sure the "Automatically Start" button is checked. This is for auto starting SlimServer after system reboot. 3. Reboot the PC. 4. Notice SlimSer does not start automatically. Note: There is already a bug like this about 7.0a1. This is for 6.5.2.
Also not able to reproduce this, perhaps another intermittent issue. I'll have another look at this and bug 4859 again tomorrow if I have time.
Assigning to myself.
I'm able to reproduce this with 3-28-2007 6.5.2 I tried installing with 'start automatically' checked, and then rebooting. It doesn't start. I also tried installing, then actually running SlimServer, then rebooting, it doesn't start.
I just noticed that this option is no longer in the nightly installer. Is this deliberate?
Reassigned to Dean. If the removal of the check box on installer is intentional, I will close this bug.
Triode could this have something to do with the changes you made recently?
Does the server restart if you block SlimTray from starting?
Triode could you be more specific? How would you like me to block SlimTray?
Disable SlimTray.exe via msconfig [or just remove/rename]. When you reboot does the server startup?
Wallace - I've just checked something in which may improve this (change 11894). Please could you let me know if tomorrow's nightly is different.
No problem. I will do that.
I tried today's build. The option in the installer to auto start SlimServer upon reboot is still not there. Therefore, I am not able to fully test the fix. In fact, I am not sure this bug should still be open. However, rebooting without selecting the auto start item in SlimTray first does not start the SlimServer, as expected. And if the tray item is selected, SlimServer does start upon reboot. That is good.
Wallace, could you please ask Ross if he thinks this bug should be closed due to the recent changes to the Windows installer?
About to check something in which I hope improves this. So don't close it yet! Wallace - could you check the mysql-error-log files - are you seeing the following at present? 070507 17:58:56 InnoDB: Operating system error number 32 in a file operation. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/mysql/en/Operating_System_error_codes.html InnoDB: File name .\ibdata1 InnoDB: File operation call: 'open'. InnoDB: Cannot continue operation. 070507 17:58:57 InnoDB: Shutdown completed; log sequence number 0 570833
Created attachment 2010 [details] mysql-error-log
Hi, Triod, I have not seen this bug for over a week now. SlimServer has been starting fine after reboot. However, I do see similar lines in the mysql-error-log.txt as mentioned. I have attach the log file above. Thanks Wallace
Can you correlate the error messages to be at startup or shutdown or only on reinstall? Are you running mysqld as a service or an app when they occur? I think they will will be ok as we have a transaction aware backend which should be able to recover from errors, but it would be good to get to the bottom of this.
It looks to me like this bug is basically fixed. If you still want it open for 6.5.2 please let me know, Adrian.
Close it unless and it can be reopened if this causes a problem. It is somewhere to look if people report the server stopping.
change number in Triode's comment 10, above
MySQL was running as a service. The fix has been verified on several nightlies in the past week. Bug as written is no longer seen. Regression testing has dug up no new bugs around starting SlimServer after reboot. Marking it as "VERIFIED".
Closing.
Developers working on SlimServer are truely knowledgable people.