My PC crashed while running a query on a large database and now I get the
error 2003, Can't connect to MySQL on localhost (10061). It's MySQL vs. 5.1
running on Win-XP.

What can I do to fix it?


Gary Luke

Just in case someone suggests it, the fault isn't due to a firewall setting.
After the crash I can't get the server to run.


> My PC crashed while running a query on a large database and now I get the
> error 2003, Can't connect to MySQL on localhost (10061). It's MySQL vs.
> 5.1 running on Win-XP.
>
> What can I do to fix it?
>
>
> Gary Luke
>

Gary wrote:
> Just in case someone suggests it, the fault isn't due to a firewall setting.
> After the crash I can't get the server to run.
>
>
>> My PC crashed while running a query on a large database and now I get the
>> error 2003, Can't connect to MySQL on localhost (10061). It's MySQL vs.
>> 5.1 running on Win-XP.
>>
>> What can I do to fix it?
>>
>>
>> Gary Luke
>>
>
>

What's your MySQL error log show?

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

"Jerry Stuckle" <jstucklex@attglobal.net> wrote in message
news:Ob-dneyp8Kz52drVnZ2dnUVZ_r6dnZ2d@comcast.com...

> Gary wrote:
>> Just in case someone suggests it, the fault isn't due to a firewall
>> setting. After the crash I can't get the server to run.
>>
>>
>>> My PC crashed while running a query on a large database and now I get
>>> the error 2003, Can't connect to MySQL on localhost (10061). It's MySQL
>>> vs. 5.1 running on Win-XP.
>>>
>>> What can I do to fix it?
>>>
>>>
>>> Gary Luke
>>>
>>
>>
>
> What's your MySQL error log show?
>

Jerry, thanks for the reply.

Restarted the PC after the crash and tried to connect - These are the last
few entries on failed attempts. If you want more from the whole session
including other attempts I could send to your email address.

Also tried 'sc query MySQL' and 'sc start MySQL' in the command screen with
no success. I must have corrupted something with the crash which now doesn't
allow the MySQL server to start.

Please don't assume from this that I know what I'm doing. I found
http://forge.mysql.com/wiki/Error200...tToMySQLServer and gently
worked through it trying to get diagnostic info before asking here.

Question - If I re-install MySQL will I lose all my databases?


080605 8:39:12 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
080605 8:39:21 InnoDB: Operating system error number 23 in a file
operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/mysql/en/Op...ror_codes.html
InnoDB: File name .\ibdata1
InnoDB: File operation call: 'Windows aio'.
InnoDB: Cannot continue operation.
080605 12:06:58 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
080605 12:07:15 InnoDB: Operating system error number 23 in a file
operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/mysql/en/Op...ror_codes.html
InnoDB: File name .\ibdata1
InnoDB: File operation call: 'Windows aio'.
InnoDB: Cannot continue operation.

> --
> ==================
> Remove the "x" from my email address
> Jerry Stuckle
> JDS Computer Training Corp.
> jstucklex@attglobal.net
> ==================

Gary wrote:
> "Jerry Stuckle" <jstucklex@attglobal.net> wrote in message
> news:Ob-dneyp8Kz52drVnZ2dnUVZ_r6dnZ2d@comcast.com...
>
>> Gary wrote:
>>> Just in case someone suggests it, the fault isn't due to a firewall
>>> setting. After the crash I can't get the server to run.
>>>
>>>
>>>> My PC crashed while running a query on a large database and now I get
>>>> the error 2003, Can't connect to MySQL on localhost (10061). It's MySQL
>>>> vs. 5.1 running on Win-XP.
>>>>
>>>> What can I do to fix it?
>>>>
>>>>
>>>> Gary Luke
>>>>
>>>
>> What's your MySQL error log show?
>>
>
> Jerry, thanks for the reply.
>
> Restarted the PC after the crash and tried to connect - These are the last
> few entries on failed attempts. If you want more from the whole session
> including other attempts I could send to your email address.
>
> Also tried 'sc query MySQL' and 'sc start MySQL' in the command screen with
> no success. I must have corrupted something with the crash which now doesn't
> allow the MySQL server to start.
>
> Please don't assume from this that I know what I'm doing. I found
> http://forge.mysql.com/wiki/Error200...tToMySQLServer and gently
> worked through it trying to get diagnostic info before asking here.
>
> Question - If I re-install MySQL will I lose all my databases?
>
>
> 080605 8:39:12 InnoDB: Database was not shut down normally!
> InnoDB: Starting crash recovery.
> InnoDB: Reading tablespace information from the .ibd files...
> InnoDB: Restoring possible half-written data pages from the doublewrite
> InnoDB: buffer...
> 080605 8:39:21 InnoDB: Operating system error number 23 in a file
> operation.
> InnoDB: Some operating system error numbers are described at
> InnoDB: http://dev.mysql.com/doc/mysql/en/Op...ror_codes.html
> InnoDB: File name .\ibdata1
> InnoDB: File operation call: 'Windows aio'.
> InnoDB: Cannot continue operation.
> 080605 12:06:58 InnoDB: Database was not shut down normally!
> InnoDB: Starting crash recovery.
> InnoDB: Reading tablespace information from the .ibd files...
> InnoDB: Restoring possible half-written data pages from the doublewrite
> InnoDB: buffer...
> 080605 12:07:15 InnoDB: Operating system error number 23 in a file
> operation.
> InnoDB: Some operating system error numbers are described at
> InnoDB: http://dev.mysql.com/doc/mysql/en/Op...ror_codes.html
> InnoDB: File name .\ibdata1
> InnoDB: File operation call: 'Windows aio'.
> InnoDB: Cannot continue operation.
>

That's not good. IIRC, Error 23 on Windows is a CRC error - IOW, disk
failure. I hope you have a backup of your databases on InnoDB.

You can try running the disk check utilities on the drive, just in case
it was caused by the crash. But I would suggest you plan on getting
another drive ASAP. Too often after seeing errors like this I've had
drives fail completely.


--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

"Jerry Stuckle" <jstucklex@attglobal.net> wrote in message
news:bPudnW2D_osQx9rVnZ2dnUVZ_qqdnZ2d@comcast.com. ..
> Gary wrote:
>> "Jerry Stuckle" <jstucklex@attglobal.net> wrote in message
>> news:Ob-dneyp8Kz52drVnZ2dnUVZ_r6dnZ2d@comcast.com...
>>
>>> Gary wrote:
>>>> Just in case someone suggests it, the fault isn't due to a firewall
>>>> setting. After the crash I can't get the server to run.
>>>>
>>>>
>>>>> My PC crashed while running a query on a large database and now I get
>>>>> the error 2003, Can't connect to MySQL on localhost (10061). It's
>>>>> MySQL vs. 5.1 running on Win-XP.
>>>>>
>>>>> What can I do to fix it?
>>>>>
>>>>>
>>>>> Gary Luke
>>>>>
>>>>
>>> What's your MySQL error log show?
>>>
>>
>> Jerry, thanks for the reply.
>>
>> Restarted the PC after the crash and tried to connect - These are the
>> last few entries on failed attempts. If you want more from the whole
>> session including other attempts I could send to your email address.
>>
>> Also tried 'sc query MySQL' and 'sc start MySQL' in the command screen
>> with no success. I must have corrupted something with the crash which now
>> doesn't allow the MySQL server to start.
>>
>> Please don't assume from this that I know what I'm doing. I found
>> http://forge.mysql.com/wiki/Error200...tToMySQLServer and gently
>> worked through it trying to get diagnostic info before asking here.
>>
>> Question - If I re-install MySQL will I lose all my databases?
>>
>>
>> 080605 8:39:12 InnoDB: Database was not shut down normally!
>> InnoDB: Starting crash recovery.
>> InnoDB: Reading tablespace information from the .ibd files...
>> InnoDB: Restoring possible half-written data pages from the doublewrite
>> InnoDB: buffer...
>> 080605 8:39:21 InnoDB: Operating system error number 23 in a file
>> operation.
>> InnoDB: Some operating system error numbers are described at
>> InnoDB:
>> http://dev.mysql.com/doc/mysql/en/Op...ror_codes.html
>> InnoDB: File name .\ibdata1
>> InnoDB: File operation call: 'Windows aio'.
>> InnoDB: Cannot continue operation.
>> 080605 12:06:58 InnoDB: Database was not shut down normally!
>> InnoDB: Starting crash recovery.
>> InnoDB: Reading tablespace information from the .ibd files...
>> InnoDB: Restoring possible half-written data pages from the doublewrite
>> InnoDB: buffer...
>> 080605 12:07:15 InnoDB: Operating system error number 23 in a file
>> operation.
>> InnoDB: Some operating system error numbers are described at
>> InnoDB:
>> http://dev.mysql.com/doc/mysql/en/Op...ror_codes.html
>> InnoDB: File name .\ibdata1
>> InnoDB: File operation call: 'Windows aio'.
>> InnoDB: Cannot continue operation.
>>
>
> That's not good. IIRC, Error 23 on Windows is a CRC error - IOW, disk
> failure. I hope you have a backup of your databases on InnoDB.
>
> You can try running the disk check utilities on the drive, just in case it
> was caused by the crash. But I would suggest you plan on getting another
> drive ASAP. Too often after seeing errors like this I've had drives fail
> completely.

I've discovered a little more from looking into the error log. In the data
folder there are three files called ib_logfile0, ib_logfile1 and ibdata1. If
I temporarily shift them to another folder, MySQL server can start, can
regognise all the table names from the databases, but says the databases
don't exist. It also creates a new set of those three files. Next step, shut
down MySQL server, put the three files back in place, and MySQL server can't
start.

It looks like those three files have become corrupted. The first two are
about 10meg each, the last is almost 6gig.

Question - Are all the databases held in the single file called ibdata1?
Is there any way to repair this set of three files?

Gary wrote:
> "Jerry Stuckle" <jstucklex@attglobal.net> wrote in message
> news:bPudnW2D_osQx9rVnZ2dnUVZ_qqdnZ2d@comcast.com. ..
>> Gary wrote:
>>> "Jerry Stuckle" <jstucklex@attglobal.net> wrote in message
>>> news:Ob-dneyp8Kz52drVnZ2dnUVZ_r6dnZ2d@comcast.com...
>>>
>>>> Gary wrote:
>>>>> Just in case someone suggests it, the fault isn't due to a firewall
>>>>> setting. After the crash I can't get the server to run.
>>>>>
>>>>>
>>>>>> My PC crashed while running a query on a large database and now I get
>>>>>> the error 2003, Can't connect to MySQL on localhost (10061). It's
>>>>>> MySQL vs. 5.1 running on Win-XP.
>>>>>>
>>>>>> What can I do to fix it?
>>>>>>
>>>>>>
>>>>>> Gary Luke
>>>>>>
>>>> What's your MySQL error log show?
>>>>
>>> Jerry, thanks for the reply.
>>>
>>> Restarted the PC after the crash and tried to connect - These are the
>>> last few entries on failed attempts. If you want more from the whole
>>> session including other attempts I could send to your email address.
>>>
>>> Also tried 'sc query MySQL' and 'sc start MySQL' in the command screen
>>> with no success. I must have corrupted something with the crash which now
>>> doesn't allow the MySQL server to start.
>>>
>>> Please don't assume from this that I know what I'm doing. I found
>>> http://forge.mysql.com/wiki/Error200...tToMySQLServer and gently
>>> worked through it trying to get diagnostic info before asking here.
>>>
>>> Question - If I re-install MySQL will I lose all my databases?
>>>
>>>
>>> 080605 8:39:12 InnoDB: Database was not shut down normally!
>>> InnoDB: Starting crash recovery.
>>> InnoDB: Reading tablespace information from the .ibd files...
>>> InnoDB: Restoring possible half-written data pages from the doublewrite
>>> InnoDB: buffer...
>>> 080605 8:39:21 InnoDB: Operating system error number 23 in a file
>>> operation.
>>> InnoDB: Some operating system error numbers are described at
>>> InnoDB:
>>> http://dev.mysql.com/doc/mysql/en/Op...ror_codes.html
>>> InnoDB: File name .\ibdata1
>>> InnoDB: File operation call: 'Windows aio'.
>>> InnoDB: Cannot continue operation.
>>> 080605 12:06:58 InnoDB: Database was not shut down normally!
>>> InnoDB: Starting crash recovery.
>>> InnoDB: Reading tablespace information from the .ibd files...
>>> InnoDB: Restoring possible half-written data pages from the doublewrite
>>> InnoDB: buffer...
>>> 080605 12:07:15 InnoDB: Operating system error number 23 in a file
>>> operation.
>>> InnoDB: Some operating system error numbers are described at
>>> InnoDB:
>>> http://dev.mysql.com/doc/mysql/en/Op...ror_codes.html
>>> InnoDB: File name .\ibdata1
>>> InnoDB: File operation call: 'Windows aio'.
>>> InnoDB: Cannot continue operation.
>>>
>> That's not good. IIRC, Error 23 on Windows is a CRC error - IOW, disk
>> failure. I hope you have a backup of your databases on InnoDB.
>>
>> You can try running the disk check utilities on the drive, just in case it
>> was caused by the crash. But I would suggest you plan on getting another
>> drive ASAP. Too often after seeing errors like this I've had drives fail
>> completely.
>
> I've discovered a little more from looking into the error log. In the data
> folder there are three files called ib_logfile0, ib_logfile1 and ibdata1. If
> I temporarily shift them to another folder, MySQL server can start, can
> regognise all the table names from the databases, but says the databases
> don't exist. It also creates a new set of those three files. Next step, shut
> down MySQL server, put the three files back in place, and MySQL server can't
> start.
>
> It looks like those three files have become corrupted. The first two are
> about 10meg each, the last is almost 6gig.
>
> Question - Are all the databases held in the single file called ibdata1?
> Is there any way to repair this set of three files?
>
>

Yes, by default, all InnoDB databases are in your ibdata1 file (the
others are log files for transactions & recovery).

The good news is if you can do that, then the CRC check error is false.
The bad news is it means your innodb data file itself is corrupted.

I've never had good luck getting data back once the file has been
corrupted. Maybe others have, but not me. I virtually always end up
restoring from backup.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

>>>>> Gary wrote:
>>>>>> Just in case someone suggests it, the fault isn't due to a firewall
>>>>>> setting. After the crash I can't get the server to run.
>>>>>>
>>>>>>
>>>>>>> My PC crashed while running a query on a large database and now I
>>>>>>> get the error 2003, Can't connect to MySQL on localhost (10061).
>>>>>>> It's MySQL vs. 5.1 running on Win-XP.
>>>>>>>
>>>>>>> What can I do to fix it?
>>>>>>>
>>>>>>> Gary Luke
>>>>>>>
>>>>> What's your MySQL error log show?

<snip>

>> I've discovered a little more from looking into the error log. In the
>> data folder there are three files called ib_logfile0, ib_logfile1 and
>> ibdata1. If I temporarily shift them to another folder, MySQL server can
>> start, can regognise all the table names from the databases, but says the
>> databases don't exist. It also creates a new set of those three files.
>> Next step, shut down MySQL server, put the three files back in place, and
>> MySQL server can't start.
>>
>> It looks like those three files have become corrupted. The first two are
>> about 10meg each, the last is almost 6gig.
>>
>> Question - Are all the databases held in the single file called ibdata1?
>> Is there any way to repair this set of three files?
>>
>>
>
> Yes, by default, all InnoDB databases are in your ibdata1 file (the others
> are log files for transactions & recovery).
>
> The good news is if you can do that, then the CRC check error is false.
> The bad news is it means your innodb data file itself is corrupted.
>
> I've never had good luck getting data back once the file has been
> corrupted. Maybe others have, but not me. I virtually always end up
> restoring from backup.
>

Jerry

Thanks for your interest and the ideas, it led me to the error file. I found
something which looks like it might solve it - I'm still carefully working
through it bit by bit.
http://forums.mysql.com/read.php?22,...450#msg-192450
"innob_force_recovery 1" allowed the server to run for 10 seconds. Not
enough time to do a dump, but after another coffee I'll move on to the next
stage. I keep telling myself. - "don't rush".

The backup is a couple of days out of date. I can repeat the last two days
work but would rather not if it's possible. It was mainly figuring out some
algorithms before programming procedures to verify various things about 2.3
million records. The thinking part of that is still in scribbles on paper -
a back-up of my brain.


Gary

It solved it. See the URL at the end of this email.

==========================

"Gary" <feraltek@westnet.com.au> wrote in message
news:ZNudnUYA87QUWNrVnZ2dnUVZ8tvinZ2d@westnet.com. au...
>>>>>> Gary wrote:
>>>>>>> Just in case someone suggests it, the fault isn't due to a firewall
>>>>>>> setting. After the crash I can't get the server to run.
>>>>>>>
>>>>>>>
>>>>>>>> My PC crashed while running a query on a large database and now I
>>>>>>>> get the error 2003, Can't connect to MySQL on localhost (10061).
>>>>>>>> It's MySQL vs. 5.1 running on Win-XP.
>>>>>>>>
>>>>>>>> What can I do to fix it?
>>>>>>>>
>>>>>>>> Gary Luke
>>>>>>>>
>>>>>> What's your MySQL error log show?
>
> <snip>
>
>>> I've discovered a little more from looking into the error log. In the
>>> data folder there are three files called ib_logfile0, ib_logfile1 and
>>> ibdata1. If I temporarily shift them to another folder, MySQL server can
>>> start, can regognise all the table names from the databases, but says
>>> the databases don't exist. It also creates a new set of those three
>>> files. Next step, shut down MySQL server, put the three files back in
>>> place, and MySQL server can't start.
>>>
>>> It looks like those three files have become corrupted. The first two are
>>> about 10meg each, the last is almost 6gig.
>>>
>>> Question - Are all the databases held in the single file called ibdata1?
>>> Is there any way to repair this set of three files?
>>>
>>>
>>
>> Yes, by default, all InnoDB databases are in your ibdata1 file (the
>> others are log files for transactions & recovery).
>>
>> The good news is if you can do that, then the CRC check error is false.
>> The bad news is it means your innodb data file itself is corrupted.
>>
>> I've never had good luck getting data back once the file has been
>> corrupted. Maybe others have, but not me. I virtually always end up
>> restoring from backup.
>>
>
> Jerry
>
> Thanks for your interest and the ideas, it led me to the error file. I
> found something which looks like it might solve it - I'm still carefully
> working through it bit by bit.
> http://forums.mysql.com/read.php?22,...450#msg-192450
> "innob_force_recovery 1" allowed the server to run for 10 seconds. Not
> enough time to do a dump, but after another coffee I'll move on to the
> next stage. I keep telling myself. - "don't rush".
>
> The backup is a couple of days out of date. I can repeat the last two days
> work but would rather not if it's possible. It was mainly figuring out
> some algorithms before programming procedures to verify various things
> about 2.3 million records. The thinking part of that is still in scribbles
> on paper - a back-up of my brain.
>
>
> Gary
>
>

On 6 Jun, 15:57, "Gary" <feral...@westnet.com.au> wrote:
> It solved it. See the URL at the end of this email.
>
> ==========================
>
> "Gary" <feral...@westnet.com.au> wrote in message
>
> news:ZNudnUYA87QUWNrVnZ2dnUVZ8tvinZ2d@westnet.com. au...
>
>
>
> >>>>>> Gary wrote:
> >>>>>>> Just in case someone suggests it, the fault isn't due to a firewall
> >>>>>>> setting. After the crash I can't get the server to run.
>
> >>>>>>>> My PC crashed while running a query on a large database and now I
> >>>>>>>> get the error 2003, Can't connect to MySQL on localhost (10061).
> >>>>>>>> It's MySQL vs. 5.1 running on Win-XP.
>
> >>>>>>>> What can I do to fix it?
>
> >>>>>>>> Gary Luke
>
> >>>>>> What's your MySQL error log show?
>
> > <snip>
>
> >>> I've discovered a little more from looking into the error log. In the
> >>> data folder there are three files called ib_logfile0, ib_logfile1 and
> >>> ibdata1. If I temporarily shift them to another folder, MySQL server can
> >>> start, can regognise all the table names from the databases, but says
> >>> the databases don't exist. It also creates a new set of those three
> >>> files. Next step, shut down MySQL server, put the three files back in
> >>> place, and MySQL server can't start.
>
> >>> It looks like those three files have become corrupted. The first two are
> >>> about 10meg each, the last is almost 6gig.
>
> >>> Question - Are all the databases held in the single file called ibdata1?
> >>> Is there any way to repair this set of three files?
>
> >> Yes, by default, all InnoDB databases are in your ibdata1 file (the
> >> others are log files for transactions & recovery).
>
> >> The good news is if you can do that, then the CRC check error is false.
> >> The bad news is it means your innodb data file itself is corrupted.
>
> >> I've never had good luck getting data back once the file has been
> >> corrupted. *Maybe others have, but not me. *I virtually always end up
> >> restoring from backup.
>
> > Jerry
>
> > Thanks for your interest and the ideas, it led me to the error file. I
> > found something which looks like it might solve it - I'm still carefully
> > working through it bit by bit.
> >http://forums.mysql.com/read.php?22,...450#msg-192450
> > "innob_force_recovery 1" allowed the server to run for 10 seconds. Not
> > enough time to do a dump, but after another coffee I'll move on to the
> > next stage. I keep telling myself. - "don't rush".
>
> > The backup is a couple of days out of date. I can repeat the last two days
> > work but would rather not if it's possible. It was mainly figuring out
> > some algorithms before programming procedures to verify various things
> > about 2.3 million records. The thinking part of that is still in scribbles
> > on paper - a back-up of my brain.
>
> > Gary- Hide quoted text -
>
> - Show quoted text -

Please stop top posting.

I tried that url and it didn't work