« Nero: Not Enough Space To Burn | Main | The Advantages of Upgrading From Vista To XP »

December 16, 2007

Oops - We Spilled Beer on the Servers Again

Oops. We spilled beer on the servers again. We had some technical difficulties with the servers from about 1:33 a.m. MST to 11:13 a.m. MST this morning. Sorry for the inconvenience. The system came down hard last night, corrupting some files on the C: drive. Then, when we rebooted, MySQL wouldn't start because it couldn't write to a temporary file that had become corrupted. I tried to delete the file, but couldn't, so I scheduled a "chkdsk /f" on the C: drive and rebooted. It ran the chkdsk and fixed the three corrupted files that were giving us grief and then MySQL came up like a champ. Wipes sweat from brow. Now... back to the book.

Scary technical details of crash and it's resolution here or click on the extended entry link below.

MYSQL_is_not_running.doc

When I tried to run any .cgi scripts on PeenieWallie this morning, I got the following error message:

Got an error: Bad ObjectDriver config: Connection error: Can't connect to MySQL server on 'localhost' (10061)

So I went to DOS (Start – Run – CMD) and tried to start MySQL.

C:\Documents and Settings\Rob>net start mysql

The MySQL service is starting.
The MySQL service could not be started.

A system error has occurred.

System error 1067 has occurred.

The process terminated unexpectedly.

I tried stopping MySQL:

C:\Documents and Settings\Rob>net stop mysql
The MySQL service is not started.

More help is available by typing NET HELPMSG 3521.

And starting MySQL again:

C:\Documents and Settings\Rob>net start mysql
The MySQL service is starting.
The MySQL service could not be started.

A system error has occurred.

System error 1067 has occurred.

The process terminated unexpectedly.


So, I went to Start – Settings – Control Panel – Administrative Tools – Services and tried to start the MYSQL service there, but still no luck. Then, I looked in the Event Viewer under Administrative Tools and found some messages in there.

The error message says “Can't init databases?

I tried to sign into the database, or get some type of feedback from it:

C:\>mysqlshow -p
Enter password: ********
mysqlshow: Can't connect to MySQL server on 'localhost' (10061)

C:\>telnet localhost 3306
Connecting To localhost...Could not open connection to the host, on port 3306: C
onnect failed

OK. I dug around and finally found that my MYSQL files are on my C drive at C:\MySQL. Then, I found the error file I was looking for called C:\MySQL\Data\Dell2400Mhz.err.

The log actually goes back to Feb 16, 2005, when I installed MySQL. Cool.

Finally, I found this in my Dell2400Mhz.err log:

C:\MySQL\bin\mysqld-nt: Can't create/write to file 'C:\WINDOWS\TEMP\ib50' (Errcode: 22)
071216 1:39:08 InnoDB: Error: unable to create temporary file; errno: 22
071216 1:39:08 [ERROR] Can't init databases
071216 1:39:08 [ERROR] Aborting


So, I found all of these temp files in the c:\windows\temp directory named ib**, from like ib2 – ib52. I created a new fold and moved them there and they all moved except for ib50, ib51, and ib52. For these three files, I get the following message in windows when I try to move them:

“The file is corrupted and unreadable.?

So, the good news is, I think I may have found the problem. I think that if I can get these files removed, then I may have a chance at getting MySQL working again.

I right-clicked on My Computer and selected Manage, then Storage, and Disk Management. It said the C: drive was a “Healthy NTFS drive? so I righ-clicked on the c: drive and selected Tools and selected Properties – Tools – Check Now. It tried to run a check disk but failed. It said it couldn’t complete the Check Disk successfully. Aha.

So, I went to DOS and attempted to run a “chkdsk /f?. It balked and scheduled one to run on reboot.

It rebooted, and ran the chkdsk twice apparently. But, on the first pass, it found some problems and fixed them and when the PC booted up, MySQL started up without a scrape.

Here’s the last entry in my Dell2400Mhz.err log:

071216 11:09:49 InnoDB: Started; log sequence number 0 2345938738
C:\MySQL\bin\mysqld-nt: ready for connections.
Version: '4.1.10-nt' socket: '' port: 3306 MySQL Community Edition (GPL)

At the end, to test it a little more, I went to DOS (start-run-cmd) and ran:

C:\net stop mysql

This successfully shut down the MySQL connection, resulting in the predicted error message when I tried to search PW for a string:

Got an error: Bad ObjectDriver config: Connection error: Can't connect to MySQL server on 'localhost' (10061)

And then I restarted MySQL under dos the same way.

C:\net start mysql

And it started up and now we’re off to the races.

Posted by Rob Kiser on December 16, 2007 at 11:12 AM

Comments

Post a comment




Remember Me?

(you may use HTML tags for style)


NOTICE: IT WILL TAKE APPROX 1-2 MINS FOR YOUR COMMENT TO POST SUCCESSFULLY. YOU WILL HAVE TO REFRESH YOUR BROWSER. PLEASE DO NOT DOUBLE POST COMMENTS OR I WILL KILL YOU.