Jump to content


Photo

MySQL keeps turning itself off


  • Please log in to reply
3 replies to this topic

#1 slobjones

slobjones
  • New Members
  • Pip
  • Newbie
  • 7 posts

Posted 08 May 2006 - 10:52 PM

I can't keep MySQL running. I start it, it turns itself off. This started today, after a week with no problems.

I've tried it with installations of EasyPHP and now XAMPP. Same problem. I've tried removing the whole thing and reinstalling. Nothing changes.

Could there be some MySQL configuration files on my system that I'm missing?

Thanks.

#2 fenway

fenway
  • Staff Alumni
  • MySQL Si-Fu / PHP Resident Alien
  • 16,199 posts
  • LocationToronto, ON

Posted 10 May 2006 - 03:26 PM

Check the error log, and post whatever messages appear in said log.
Seriously... if people don't start reading this before posting, I'm going to consider not answering at all.

#3 slobjones

slobjones
  • New Members
  • Pip
  • Newbie
  • 7 posts

Posted 10 May 2006 - 06:23 PM

[!--quoteo(post=372938:date=May 10 2006, 10:26 AM:name=fenway)--][div class=\'quotetop\']QUOTE(fenway @ May 10 2006, 10:26 AM) View Post[/div][div class=\'quotemain\'][!--quotec--]
Check the error log, and post whatever messages appear in said log.
[/quote]

Here's a nice, fresh error log. I started XAMPP Control Panel, performed a refresh and status check and got this in the error log:

[Wed May 10 13:07:47 2006] [crit] (22)Invalid argument: unable to replace stderr with error_log
[Wed May 10 13:07:47 2006] [crit] (2)No such file or directory: unable to replace stderr with /dev/null
[Wed May 10 13:07:54 2006] [crit] (22)Invalid argument: unable to replace stderr with error_log
[Wed May 10 13:07:54 2006] [crit] (2)No such file or directory: unable to replace stderr with /dev/null
[Wed May 10 13:08:06 2006] [notice] Apache/2.2.0 (Win32) DAV/2 mod_ssl/2.2.0 OpenSSL/0.9.8a mod_autoindex_color PHP/5.1.2 configured -- resuming normal operations
[Wed May 10 13:08:06 2006] [notice] Server built: Dec 1 2005 18:36:53
[Wed May 10 13:08:06 2006] [notice] Parent: Created child process 1244
[Wed May 10 13:08:22 2006] [notice] Child 1244: Child process is running
[Wed May 10 13:08:22 2006] [notice] Child 1244: Acquired the start mutex.
[Wed May 10 13:08:22 2006] [notice] Child 1244: Starting 250 worker threads.
[Wed May 10 13:08:22 2006] [notice] Child 1244: Starting thread to listen on port 443.
[Wed May 10 13:08:22 2006] [notice] Child 1244: Starting thread to listen on port 80.

I've found now that if I run XAMPP-restart, MySQL will operate, even though XAMPP-restart first reports: "Can't connect to MySQL server on localhost (10061)."

A check of the error log then shows:

[Wed May 10 13:12:57 2006] [notice] Apache/2.2.0 (Win32) DAV/2 mod_ssl/2.2.0 OpenSSL/0.9.8a mod_autoindex_color PHP/5.1.2 configured -- resuming normal operations
[Wed May 10 13:12:57 2006] [notice] Server built: Dec 1 2005 18:36:53
[Wed May 10 13:12:57 2006] [notice] Parent: Created child process 5648
[Wed May 10 13:13:30 2006] [notice] Child 5648: Child process is running
[Wed May 10 13:13:30 2006] [notice] Child 5648: Acquired the start mutex.
[Wed May 10 13:13:30 2006] [notice] Child 5648: Starting 250 worker threads.
[Wed May 10 13:13:31 2006] [notice] Child 5648: Starting thread to listen on port 443.
[Wed May 10 13:13:31 2006] [notice] Child 5648: Starting thread to listen on port 80.

XAMPP Control Panel reports:

ERROR: Status Check Failure [1]
ERROR: Status Check Failure [2]

But at that point, I can run localhost in my browser and MySQL operates with no problem. So maybe I should just run it this way and ignore the error messages.



#4 fenway

fenway
  • Staff Alumni
  • MySQL Si-Fu / PHP Resident Alien
  • 16,199 posts
  • LocationToronto, ON

Posted 10 May 2006 - 08:44 PM

Well, that's not a MySQL error log; and the fact that it thinks it can't connect is definitely a problem.
Seriously... if people don't start reading this before posting, I'm going to consider not answering at all.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users