RE: Error 2003: Cannot connect to mySQL server on localhost <10061>

This may shed some light on my issue.

1.When I delete ib_logfile1 since nothing is in it and restart my
computer below is what I  get in my .err log. A new ib_logfile1 is
created with nothing in it.

051130 12:04:12  InnoDB: Log file .\ib_logfile1 did not exist: new to
be created
051130 12:04:12  Can't init databases
051130 12:04:12  Aborting

051130 12:04:12  InnoDB: Warning: shutting down a not properly started
                 InnoDB: or created database!
051130 12:04:12  MySql: Shutdown Complete

2. Next I start winmysqladmin and I get....
myodbc not found
driver version
driver  c:\windows\system32\myodbc3.dll
api level
setup           c:\windows\system32\myodbc3s.dll
sql level

3. I then checked my .err log and get the following:

InnoDB: Error: log file .\ib_logfile1 is of different size 0 0 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
051130 12:10:41  Can't init databases
051130 12:10:41  Aborting

051130 12:10:41  InnoDB: Warning: shutting down a not properly started
                 InnoDB: or created database!
051130 12:10:41  MySql: Shutdown Complete

4. Since after I reinstalled windows xp, myodbc 3.51 driver was
missing. So I installed a new one and configured it with the odbc data
source administrator. When I configure it and did a test, I got sql
error. When I enabled dianostics I got: odbc3.51 driver can't connect
to MySQL server on localhost [10061].

Myodbc configuration is as follows:
Name: myodbc
Description: mysql odbc 3.51 driver dsn
Server: localhost
User: bob
Password:bob
Database: blank
Port: 3306
Socket: blank

User and Password is the same as my.ini file. So why can't I connect
to the local host at port 3306? Is that where my problem lies or is it
because I can't keep mysql running on port 3306?

Bob

-----Original Message-----
From: Bob Melis [mailto:bobmelis@xxxxxxxxxxxx]
Sent: Tuesday, November 29, 2005 9:55 PM
To: myodbc@xxxxxxxxxxxxxxx
Subject: RE: Error 2003: Cannot connect to mySQL server on localhost
<10061>


It looks like this is when the problem started. Before that it started
and shut down ok. I believe that is because I was not accessing mysql.
I believe the good start and shutdown happened without my trying to
access mysql. Once I did, it says need to create logfile1. If that is
the issue, how do I create it and what do I put in it?

bob

051122 17:14:23  InnoDB: Started
MySql: ready for connections.
Version: '4.0.13-nt'  socket: ''  port: 3306
051123  3:09:27  MySql: Normal shutdown

051123  3:09:31  InnoDB: Starting shutdown...
051123  3:09:37  InnoDB: Shutdown completed
051123  3:09:37  MySql: Shutdown Complete

051123 13:46:22  InnoDB: Log file .\ib_logfile1 did not exist: new to
be created
051123 13:46:22  Can't init databases
051123 13:46:22  Aborting

051123 13:46:22  InnoDB: Warning: shutting down a not properly started
                 InnoDB: or created database!
051123 13:46:22  MySql: Shutdown Complete

-----Original Message-----
From: Bob Melis [mailto:bobmelis@xxxxxxxxxxxx]
Sent: Tuesday, November 29, 2005 8:00 PM
To: myodbc@xxxxxxxxxxxxxxx
Subject: FW: Error 2003: Cannot connect to mySQL server on localhost
<10061>


Bob Melis wrote:
> - I've checked process running and I cannot get mysql to run using
the
> CMD window and typing mysqld or mysqld-n.

Please elaborate..
(or copy/paste from cmd window.)
***************RESPONSE1*****************
cmd procedure:
cd\mysql\bin
mysql>mysqld
mysql>mysqld-nt

to try and get it running
***************end1********************

> - err file in data directory: I cannot open it or do not know how to
> open it - it is called Robert.err and is 345kb so something is in
it.

It's a plain ASCII text file with CR/LF line endings.
It opens with notepad or similar.

You can also paste the last 20 lines or so into this conversation,
or attach the entire file in zipped form.

***** RESPONSE TO ABOVE2**********************
err file: looks like a conflict with logfile1 and .cnf file.
InnoDB: Error: log file .\ib_logfile1 is of different size 0 0 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
051129 18:54:02  Can't init databases
051129 18:54:02  Aborting

051129 18:54:03  InnoDB: Warning: shutting down a not properly started
                 InnoDB: or created database!
051129 18:54:03  MySql: Shutdown Complete
*****************END2**************************

> - This problem started after I reinstalled windows xp and I noticed
> the update version was labled differently than what I had before.

Not sure what you mean by "update version".
*******************Response3********************************
Used the windows reinstall CD per Dell's instructions to correct a
problem conflict between an application and IE. When I did this it
asked about drivers and the help desk said to skip it. Turned out the
next day had a problem with my sound card but it repaired itself. I
also had to download all of Microsoft updates since they were all
gone. When I noticed that mysql was not working, I found that I no
longer had myodbc and reinstalled 3.51 yesterday.
******************end3***************************************

> Do you think I will need to reinstall mysql?

No, but then again, I have no clue what your exact problem is (yet).
*******************Response4****************************
hopefully this new information will help determine what I must do.
**********************end4*********************************

> - my.ini file listing is the following:
> [mysqld]
> basedir=C:/mysql
> datadir=C:/mysql/data

Assuming the above directories exist etc., the config file looks OK to
me.

**********************Response5*******************************
Yes, they I have all of them. It worked for two years and only had
this problem since I reinstalled windows. I suspect something was
changed or deleted when I did this since the myodbc was no longer on
my pc.
*********************end5************************************


-- 
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe:    http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc@xxxxxxxxxxx