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

If anyone can help, this must be a simple problem for the experienced.

I installed mySQL 4.0.13 a couple of years ago when I was taking a
java course and it was working ok until I recently reinstalled windows
xp with their updates.

Using the CMD window to access mySQL, I get an error 2003: cannot
connect server on localhost 10061. I checked that mySQL was running on
localhost and port 3306. Also when I telnet localhost 3306, I cannot
open a connection to host on port 3306. When I enable winmysqladmin, I
get ODBC driver 3.51 not found.

I am using mysql-connector-java-3.0.8-stable-bin.jar. I believe that
is to connect my java application to the Microsoft ODBC.

I suspect I no longer have correct ODBC driver but I'm not sure what I
have. Do I need to download the 3.51 driver from mySQL or get it from
Microsoft? I do not see any driver in the control panel nor my program
files. Can someone provide me any guidance so I can get mySQL working
again? I am using it to develop a program for myself and further
develop my java skills.

If I download the newest version of mySQL, do you believe it will work
with my windows xp? The window home edition version I am using is the
following:
v 5.1(build 2600.xpsp_sp2_gdr.o50301-1519:servicePack2)

Any help to set me in the right direction is appreciated.


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

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

Correction. I cannot get mysql to run. It seems to stop when I use
winmysqladmin or run directly from the application. Also, in my.ini
file I have the following:

#This File was made using the WinMySQLAdmin 1.4 Tool
#7/17/2003 10:47:51 PM

#Uncomment or Add only the keys that you know how works.
#Read the MySQL Manual for instructions

[mysqld]
basedir=C:/mysql
#bind-address=68.70.103.150
datadir=C:/mysql/data
#language=C:/mysql/share/your language directory
#slow query log#=
#tmpdir#=
#port=3306
#set-variable=key_buffer=16M
[WinMySQLadmin]
Server=C:/mysql/bin/mysqld-nt.exe
user=bob
password=bob
QueryInterval=10


-----Original Message-----
From: Bob Melis [mailto:bobmelis@adelphia.net]
Sent: Monday, November 28, 2005 3:43 PM
To: myodbc@lists.mysql.com
Subject: Error 2003: Cannot connect to mySQL server on localhost
<10061>


If anyone can help, this must be a simple problem for the experienced.

I installed mySQL 4.0.13 a couple of years ago when I was taking a
java course and it was working ok until I recently reinstalled windows
xp with their updates.

Using the CMD window to access mySQL, I get an error 2003: cannot
connect server on localhost 10061. I checked that mySQL was running on
localhost and port 3306. Also when I telnet localhost 3306, I cannot
open a connection to host on port 3306. When I enable winmysqladmin, I
get ODBC driver 3.51 not found.

I am using mysql-connector-java-3.0.8-stable-bin.jar. I believe that
is to connect my java application to the Microsoft ODBC.

I suspect I no longer have correct ODBC driver but I'm not sure what I
have. Do I need to download the 3.51 driver from mySQL or get it from
Microsoft? I do not see any driver in the control panel nor my program
files. Can someone provide me any guidance so I can get mySQL working
again? I am using it to develop a program for myself and further
develop my java skills.

If I download the newest version of mySQL, do you believe it will work
with my windows xp? The window home edition version I am using is the
following:
v 5.1(build 2600.xpsp_sp2_gdr.o50301-1519:servicePack2)

Any help to set me in the right direction is appreciated.


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

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

Bob Melis wrote:
> I cannot get mysql to run.

Check the mysql .err file in your data directory (specified in
my.{ini,cnf}) for error messages from the server. If the mysql server
doesn't even get that far, check your NT Application event log (run
"eventvwr"), or run the server (mysqld-nt ?) from the command line.

> Cannot connect to mySQL server on localhost <10061>

10061 is an error number from Windows' socket layer meaning that the TCP
connection was actively refused (by a RESET packet from the remote
host). This usually means that noone is listening at the ip/port you're
trying to access.

> I am using mysql-connector-java-3.0.8-stable-bin.jar. I believe that
> is to connect my java application to the Microsoft ODBC.

Never used it, but I think you're wrong.
I think ODBC connections from Java are done using a generic ODBC-JDBC
bridge (supplied by eg. Sun).
I think the Java connector is a JDBC driver that does not depend on
Connector/ODBC.


--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=3Dgcdmo-myodbc@m.gmane.o rg

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

Thanks for your quick response.
- I've checked process running and I cannot get mysql to run using the
CMD window and typing mysqld or mysqld-n. Also when I start the
winmysqladmin, the stoplight never turns green. It also says myodbc
not found.

- 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.
When I use winmysqladmin and go to err file nothing shows up. I do
have a my.ini file under windows but not my.cnf file.

- run "eventvwr"), or run the server (mysqld-nt ?) from the command
line: don't see anything in event viewer related to mysql,and when I
run mysqld-nt or mysqld nothing happens. When I use HijackThis to see
start up processes it shows 023-service:mysql-unknown
owner-c:mysql/bin/mysqld-nt.exe; however, when I check processes
running, mysql has stopped while showing automatic.

- This problem started after I reinstalled windows xp and I noticed
the update version was labled differently than what I had before. Do
you think I will need to reinstall mysql?

- I installed and configured the myodbc 3.51 and the winsqladmin still
says myodbc not found but also has ...
Driver Version
Driver c:\windows\system32\myodbc3.dll
api level
setup c:\windows\system32\myodbc3s.dll
sql level

- my.ini file listing is the following:
#This File was made using the WinMySQLAdmin 1.4 Tool
#7/17/2003 10:47:51 PM

#Uncomment or Add only the keys that you know how works.
#Read the MySQL Manual for instructions

[mysqld]
basedir=C:/mysql
#bind-address=68.70.103.150
datadir=C:/mysql/data
#language=C:/mysql/share/your language directory
#slow query log#=
#tmpdir#=
#port=3306
#set-variable=key_buffer=16M
[WinMySQLadmin]
Server=C:/mysql/bin/mysqld-nt.exe
user=bob
password=bob

I hope this sheds some light on what I must do to correct this issue.

Again thanks for your help.

Bob

-----Original Message-----
From: David Dindorp [mailto:ddi@dubex.dk]
Sent: Tuesday, November 29, 2005 2:43 AM
To: Bob Melis
Cc: myodbc@lists.mysql.com
Subject: RE: Error 2003: Cannot connect to mySQL server on localhost
<10061>


Bob Melis wrote:
> I cannot get mysql to run.

Check the mysql .err file in your data directory (specified in
my.{ini,cnf}) for error messages from the server. If the mysql server
doesn't even get that far, check your NT Application event log (run
"eventvwr"), or run the server (mysqld-nt ?) from the command line.

> Cannot connect to mySQL server on localhost <10061>

10061 is an error number from Windows' socket layer meaning that the
TCP
connection was actively refused (by a RESET packet from the remote
host). This usually means that noone is listening at the ip/port
you're
trying to access.

> I am using mysql-connector-java-3.0.8-stable-bin.jar. I believe that
> is to connect my java application to the Microsoft ODBC.

Never used it, but I think you're wrong.
I think ODBC connections from Java are done using a generic ODBC-JDBC
bridge (supplied by eg. Sun).
I think the Java connector is a JDBC driver that does not depend on
Connector/ODBC.


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

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

I would get the latest versions of both MySQL and MyODBC and reinstall,
carefully following the instructions in the MySQL manual on Windows
installation. It all runs under XP Pro SP2, I am running it.

John B.

-----Original Message-----
From: Bob Melis [mailto:bobmelis@adelphia.net]
Sent: Tuesday, 29 November 2005 9:13 AM
To: myodbc@lists.mysql.com
Subject: Error 2003: Cannot connect to mySQL server on localhost <10061>

If anyone can help, this must be a simple problem for the experienced.

I installed mySQL 4.0.13 a couple of years ago when I was taking a
java course and it was working ok until I recently reinstalled windows
xp with their updates.

Using the CMD window to access mySQL, I get an error 2003: cannot
connect server on localhost 10061. I checked that mySQL was running on
localhost and port 3306. Also when I telnet localhost 3306, I cannot
open a connection to host on port 3306. When I enable winmysqladmin, I
get ODBC driver 3.51 not found.

I am using mysql-connector-java-3.0.8-stable-bin.jar. I believe that
is to connect my java application to the Microsoft ODBC.

I suspect I no longer have correct ODBC driver but I'm not sure what I
have. Do I need to download the 3.51 driver from mySQL or get it from
Microsoft? I do not see any driver in the control panel nor my program
files. Can someone provide me any guidance so I can get mySQL working
again? I am using it to develop a program for myself and further
develop my java skills.

If I download the newest version of mySQL, do you believe it will work
with my windows xp? The window home edition version I am using is the
following:
v 5.1(build 2600.xpsp_sp2_gdr.o50301-1519:servicePack2)

Any help to set me in the right direction is appreciated.



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

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

-----Original Message-----
From: David Dindorp [mailto:ddi@dubex.dk]
Sent: Tuesday, November 29, 2005 3:56 AM
To: Bob Melis
Subject: RE: 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@m.gmane.org

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

Bob Melis wrote:
> InnoDB: Log file .\ib_logfile1 did not exist: new to be created
> Can't init databases
> Aborting

Well, there's your problem.
Unfortunately, "can't init databases" is
not a very informative error message.

You can check the basics (is there enough disk space? etc.)
and try a newer MySQL server version. Other than that, I think
you'll need someone with specific knowledge of InnoDB internals
to help you out..

An easy solution is to disable InnoDB (and BDB) and just use MyISAM.
Adding skip-innodb and skip-bdb to the [mysqld] section of your my.ini
should accomplish that..


--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=3Dgcdmo-myodbc@m.gmane.o rg

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

Thanks DAvid, I'll try that if I can figure it out.

Another thing, when I telnet to port 3306 I also get an error. I think
I typed open 3306 or something like that. Once I open the telnet
window
What do I type to check if 3306 is available and what should I get in
response? Could something else be occupying that port and that is why
I can't init db?

-----Original Message-----
From: David Dindorp [mailto:ddi@dubex.dk]
Sent: Thursday, December 01, 2005 3:49 AM
To: Bob Melis
Cc: myodbc@lists.mysql.com
Subject: RE: Error 2003: Cannot connect to mySQL server on localhost
<10061>


Bob Melis wrote:
> InnoDB: Log file .\ib_logfile1 did not exist: new to be created
> Can't init databases
> Aborting

Well, there's your problem.
Unfortunately, "can't init databases" is
not a very informative error message.

You can check the basics (is there enough disk space? etc.)
and try a newer MySQL server version. Other than that, I think
you'll need someone with specific knowledge of InnoDB internals
to help you out..

An easy solution is to disable InnoDB (and BDB) and just use MyISAM.
Adding skip-innodb and skip-bdb to the [mysqld] section of your my.ini
should accomplish that..


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

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

Dave,

When I do the mysqld-nt --console, I get
ready for connections.
Version: 4.0.13-nt socket: '' port:3306

I then opened another window and could start winmysqladmin (green
light)and see my databases but it still says odbc not found. My java
programs also worked.

Does this mean I will need to start mysql this way until I resolve the
innodb issue or download mysql again? I will first contact the group
that understands DB internals to see if there is a simple fix.

If I reinstall mysql, I assume I should use the same version (4.0.13).
If so, will I have to reinstall java connector, or keep the one I
already have (connector-java-3.0.8-stable-bin.jar)? Also will the
reinstall include myodbc since I never had to install that in the
past. If so, should I delete the one that I installed since I cannot
get it to work using the Test function on the Windows ODBC Data Source
Administrator?

Once I get mysql working again at my current version, are there any
advantages to upgrading to 4.1.15 - my application today is only
standalone but in the future I might offer a web service access to my
java program that uses mysql as its DB. I assume 5.0.16 would be used
for larger applications then I am considering at this time. Not
totally sure the difference between 4.1 and 5.0.

Thanks again for your help.

Bob
-----Original Message-----
From: David Dindorp [mailto:ddi@dubex.dk]
Sent: Thursday, December 01, 2005 3:57 AM
To: Bob Melis
Subject: RE: Error 2003: Cannot connect to mySQL server on localhost
<10061>


> > > - 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********************

Oops. Failed to mention that when you run mysqld-nt from the CLI,
you must supply a '--console' option, otherwise you won't get any
output. Sorry. Anyway, not important, it would have printed the
exact same as you see in the .err file, so the lines you've quoted
from there is sufficient.


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

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

Hi, shaoul-tellink;

I did the following and could not get telnet to work.

Opened window: Start --> Run --> telnet: Got a telnet window:
typed: Microsoft Telnet> open localhost [3306]
Got:Connecting to localhost...Could not open connection to the host,
on port 3306

typed: open localhost
Got: Connecting to localhost...Could not open connection to the host,
on port 23.

I did get mysql running as a standalone and it is on port 3306. So the
above is while mysql is running. Also turned my firewall off.

Am I using telnet properly? Where do I type: 'telnet 3306'? Not sure
how to use ethereal. Will need to research.

Last coorespondence with Dave resulted in something wrong with
internal DB since can't initiate it. My guess is that something is not
working properly with windows xp since I reinstalled it. I will
contact another group that understands mysql internals before I try to
reinstall mysql. My guess is that I will need to reinstall mysql.

Thanks

Bob

If you use MS windows, you should type : 'telnet 3306'
If that works, you will get a string starting with the version number
of the
MySQL server followed by several special characters.

If it does not work, use ethereal to sniff the packets both on the
server
and the client.
I suspect some firewall settings.

If ethereal on the server shows your telnet request but the server do
not
react, chances are high you are blocked by a firewall on the server

Also, are you sure that you use port 3306 ?
Some administrators compile MySQL to use a non standard (different)
port

Sorry if others already proposed the same ideas.
I did not followed the whole discussion

Regards,

T. Jacobson






--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.362 / Virus Database: 267.13.10/189 - Release Date:
30/11/2005



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

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

For some reason when I try to reach forums.mysql.com on my ie browser,
it hangs up and I need to close it down. Not sure why that is.
However, when I use the foxfire browser,it works. Guess I will tell MS
about that issue.

-----Original Message-----
From: David Dindorp [mailto:ddi@dubex.dk]
Sent: Thursday, December 01, 2005 4:03 AM
To: Bob Melis
Subject: RE: Error 2003: Cannot connect to mySQL server on localhost
<10061>


David Dindorp wrote:
> Other than that, I think you'll need someone with specific
> knowledge of InnoDB internals to help you out..

Btw, those guys probably hang out over here:
http://forums.mysql.com/list.php?22

If you won't make do with MyISAM and you want the InnoDB
engine to work, that's the place to ask InnoDB questions..


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

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

> When I do the mysqld-nt --console, I get:
> ready for connections.

You fail to mention whether you've added
skip-bdb
skip-innodb
to [mysqld] in your my.ini as I suggested.

> Once I open the telnet window what do I
> type to check if 3306 is available

open localhost 3306

> and what should I get in response?

Depends on your Windows version.
On XP, if it succeeds, you'll get garbage or nothing at all.

If it fails (still XP), you'll see:
==================== =====3D=
===3D
Connecting To localhost...
Could not open connection to the host, on port 3306:
Connect failed
==================== =====3D=
===3D

If the connection is actively denied, the above message
appears instantly. If the connection is silently dropped
by fx. a firewall the message appears after 10 sec. or so.

> Could something else be occupying that
> port and that is why I can't init db?

With MySQL stopped, run:

netstat -an | find "3306"

If something is occupying the MySQL port, you'll see:
TCP 0.0.0.0:3306 0.0.0.0:0 LISTENING

Otherwise you'll see nothing printed on the screen.

> it still says odbc not found

Try (re-)installing the newest Connector/ODBC.

> are there any advantages to upgrading

The likelihood of developers being able to help you is
a lot better if you upgrade. Then again, the likelihood
of the problems encountered being known problems is
better if you stick to an old version. All in all, when
it comes to MySQL, I'd definitely recommend upgrading to
the GA version of both MySQL, Connector/ODBC and Connector/J.


--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=3Dgcdmo-myodbc@m.gmane.o rg

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

Hello Bob,
if the server runs standalone, but not as a service, I guess you have a =
missconfigured server-config-file:
post us the contents of your "my.ini"
regards,
armin.

> -----Original Message-----
> From: Bob Melis [mailto:bobmelis@adelphia.net]=20
> Sent: Friday, December 02, 2005 3:45 AM
> To: myodbc@lists.mysql.com
> Cc: Shaoul-Tellink
> Subject: RE: Error 2003: Cannot connect to mySQL server on=20
> localhost <10061>
>=20
> Hi, shaoul-tellink;
>=20
> I did the following and could not get telnet to work.
>=20
> Opened window: Start --> Run --> telnet: Got a telnet window:
> typed: Microsoft Telnet> open localhost [3306] Got:Connecting=20
> to localhost...Could not open connection to the host, on port 3306
>=20
> typed: open localhost
> Got: Connecting to localhost...Could not open connection to=20
> the host, on port 23.
>=20
> I did get mysql running as a standalone and it is on port=20
> 3306. So the above is while mysql is running. Also turned my=20
> firewall off.
>=20
> Am I using telnet properly? Where do I type: 'telnet 3306'?=20
> Not sure how to use ethereal. Will need to research.
>=20
> Last coorespondence with Dave resulted in something wrong=20
> with internal DB since can't initiate it. My guess is that=20
> something is not working properly with windows xp since I=20
> reinstalled it. I will contact another group that understands=20
> mysql internals before I try to reinstall mysql. My guess is=20
> that I will need to reinstall mysql.
>=20
> Thanks
>=20
> Bob
>=20
> If you use MS windows, you should type : 'telnet 3306'
> If that works, you will get a string starting with the=20
> version number of the MySQL server followed by several=20
> special characters.
>=20
> If it does not work, use ethereal to sniff the packets both=20
> on the server and the client.
> I suspect some firewall settings.
>=20
> If ethereal on the server shows your telnet request but the=20
> server do not react, chances are high you are blocked by a=20
> firewall on the server
>=20
> Also, are you sure that you use port 3306 ?
> Some administrators compile MySQL to use a non standard=20
> (different) port
>=20
> Sorry if others already proposed the same ideas.
> I did not followed the whole discussion
>=20
> Regards,
>=20
> T. Jacobson
>=20
>=20
>=20
>=20
>=20
>=20
> --
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.1.362 / Virus Database: 267.13.10/189 - Release Date:
> 30/11/2005
>=20
>=20
>=20
> --
> MySQL ODBC Mailing List
> For list archives: http://lists.mysql.com/myodbc
> To unsubscribe: =20
> http://lists.mysql.com/myodbc?unsub=3Darmin.schoeffmann@aega eon.de
>=20
>=20
>=20
>=20

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=3Dgcdmo-myodbc@m.gmane.o rg

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

Dave, I sent this to the list since I cannot send to your address.

When I do the mysqld-nt --console, I get
ready for connections.
Version: 4.0.13-nt socket: '' port:3306

I then opened another window and could start winmysqladmin (green
light)and see my databases but it still says odbc not found. My java
programs also worked.

Does this mean I will need to start mysql this way until I resolve the
innodb issue or download mysql again? I will first contact the group
that understands DB internals to see if there is a simple fix.

If I reinstall mysql, I assume I should use the same version (4.0.13).
If so, will I have to reinstall java connector, or keep the one I
already have (connector-java-3.0.8-stable-bin.jar)? Also will the
reinstall include myodbc since I never had to install that in the
past. If so, should I delete the one that I installed since I cannot
get it to work using the Test function on the Windows ODBC Data Source
Administrator?

Once I get mysql working again at my current version, are there any
advantages to upgrading to 4.1.15 - my application today is only
standalone but in the future I might offer a web service access to my
java program that uses mysql as its DB. I assume 5.0.16 would be used
for larger applications then I am considering at this time. Not
totally sure the difference between 4.1 and 5.0.

Thanks again for your help.

Bob

-----Original Message-----
From: David Dindorp [mailto:ddi@dubex.dk]
Sent: Friday, December 02, 2005 2:34 AM
To: Bob Melis
Cc: myodbc@lists.mysql.com
Subject: RE: Error 2003: Cannot connect to mySQL server on localhost
<10061>


> When I do the mysqld-nt --console, I get:
> ready for connections.

You fail to mention whether you've added
skip-bdb
skip-innodb
to [mysqld] in your my.ini as I suggested.

> Once I open the telnet window what do I
> type to check if 3306 is available

open localhost 3306

> and what should I get in response?

Depends on your Windows version.
On XP, if it succeeds, you'll get garbage or nothing at all.

If it fails (still XP), you'll see:
============================
Connecting To localhost...
Could not open connection to the host, on port 3306:
Connect failed
============================

If the connection is actively denied, the above message
appears instantly. If the connection is silently dropped
by fx. a firewall the message appears after 10 sec. or so.

> Could something else be occupying that
> port and that is why I can't init db?

With MySQL stopped, run:

netstat -an | find "3306"

If something is occupying the MySQL port, you'll see:
TCP 0.0.0.0:3306 0.0.0.0:0 LISTENING

Otherwise you'll see nothing printed on the screen.

> it still says odbc not found

Try (re-)installing the newest Connector/ODBC.

> are there any advantages to upgrading

The likelihood of developers being able to help you is
a lot better if you upgrade. Then again, the likelihood
of the problems encountered being known problems is
better if you stick to an old version. All in all, when
it comes to MySQL, I'd definitely recommend upgrading to
the GA version of both MySQL, Connector/ODBC and Connector/J.


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

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

Below is my.ini file. I was told it was ok. I added skip innodb and
bdb to get the mysqld-nt console to run.
Without it my .err file says cannot init DB and creates an ib_logfile1
with nothing in it. Below is also the .err file.
> InnoDB: Log file .\ib_logfile1 did not exist: new to be created
> Can't init databases
> Aborting

my.ini file:
#This File was made using the WinMySQLAdmin 1.4 Tool
#7/17/2003 10:47:51 PM

#Uncomment or Add only the keys that you know how works.
#Read the MySQL Manual for instructions

[mysqld]
basedir=C:/mysql
#bind-address=68.70.103.150
datadir=C:/mysql/data
#language=C:/mysql/share/your language directory
#slow query log#=
#tmpdir#=
#port=3306
#set-variable=key_buffer=16M
skip-innodb
skip-bdb
[WinMySQLadmin]
Server=C:/mysql/bin/mysqld-nt.exe
user=bob
password=bob

bob


-----Original Message-----
From: Armin Schöffmann [mailto:armin.schoeffmann@aegaeon.de]
Sent: Friday, December 02, 2005 2:52 AM
To: Bob Melis; myodbc@lists.mysql.com
Cc: Shaoul-Tellink
Subject: RE: Error 2003: Cannot connect to mySQL server on localhost
<10061>


Hello Bob,
if the server runs standalone, but not as a service, I guess you have
a missconfigured server-config-file:
post us the contents of your "my.ini"
regards,
armin.

> -----Original Message-----
> From: Bob Melis [mailto:bobmelis@adelphia.net]
> Sent: Friday, December 02, 2005 3:45 AM
> To: myodbc@lists.mysql.com
> Cc: Shaoul-Tellink
> Subject: RE: Error 2003: Cannot connect to mySQL server on
> localhost <10061>
>
> Hi, shaoul-tellink;
>
> I did the following and could not get telnet to work.
>
> Opened window: Start --> Run --> telnet: Got a telnet window:
> typed: Microsoft Telnet> open localhost [3306] Got:Connecting
> to localhost...Could not open connection to the host, on port 3306
>
> typed: open localhost
> Got: Connecting to localhost...Could not open connection to
> the host, on port 23.
>
> I did get mysql running as a standalone and it is on port
> 3306. So the above is while mysql is running. Also turned my
> firewall off.
>
> Am I using telnet properly? Where do I type: 'telnet 3306'?
> Not sure how to use ethereal. Will need to research.
>
> Last coorespondence with Dave resulted in something wrong
> with internal DB since can't initiate it. My guess is that
> something is not working properly with windows xp since I
> reinstalled it. I will contact another group that understands
> mysql internals before I try to reinstall mysql. My guess is
> that I will need to reinstall mysql.
>
> Thanks
>
> Bob
>
> If you use MS windows, you should type : 'telnet 3306'
> If that works, you will get a string starting with the
> version number of the MySQL server followed by several
> special characters.
>
> If it does not work, use ethereal to sniff the packets both
> on the server and the client.
> I suspect some firewall settings.
>
> If ethereal on the server shows your telnet request but the
> server do not react, chances are high you are blocked by a
> firewall on the server
>
> Also, are you sure that you use port 3306 ?
> Some administrators compile MySQL to use a non standard
> (different) port
>
> Sorry if others already proposed the same ideas.
> I did not followed the whole discussion
>
> Regards,
>
> T. Jacobson
>
>
>
>
>
>
> --
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.1.362 / Virus Database: 267.13.10/189 - Release Date:
> 30/11/2005
>
>
>
> --
> MySQL ODBC Mailing List
> For list archives: http://lists.mysql.com/myodbc
> To unsubscribe:
> http://lists.mysql.com/myodbc?unsub=armin.schoeffmann@aegaeo n.de
>
>
>
>


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

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

Bob Melis wrote:
> Below is my.ini file. I added skip innodb and
> bdb to get the mysqld-nt console to run.

> When I do the mysqld-nt --console, I get:
> ready for connections.

> Does this mean I will need to start mysql this way until
> I resolve the innodb issue or download mysql again?

No, if it starts OK in console mode with skip-innodb,
it _should_ run fine in service mode too (with skip-innodb).

> are there any advantages to upgrading

Use the MySQL feature comparison page:
http://dev.mysql.com/tech-resources/features.html

You might want to prod the MySQL folks and tell them to
update the web page to include MySQL series 5.

Also, you can read the MySQL change history:
http://dev.mysql.com/doc/refman/5.0/en/news.html

It only covers the currently recommended version.
For older versions, you'll have to dig out an
older version of the manual which it's included in:
http://dev.mysql.com/doc/refman/4.1/en/news.html

> I assume 5.0.16 would be used for larger
> applications then I am considering at this time.

No, it's equally suited for small applications.


--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=3Dgcdmo-myodbc@m.gmane.o rg

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

David, thanks soooo much.

You got my application running again with the skip innodb and bdb in
my.ini file. I will look into installing a later versions of mysql in
the future.

When you say save data files, that of course is the data files I
created. Do I need to save everything under the mysql\data directory
such as ibdata1, ib_logfile0, ib_arch_log_0000000000.

I assume I can reuse the mysql-connector-java file without downloading
it again. Is that correct?

Also, will I need to ...
- uninstall mysql before I download it, or
- just download and unzip it and it will automatically replace the
existing one?

Issue Resolved and thanks again.

Bob

-----Original Message-----
From: David Dindorp [mailto:ddi@dubex.dk]
Sent: Friday, December 02, 2005 5:31 AM
To: Bob Melis
Cc: myodbc@lists.mysql.com
Subject: RE: Error 2003: Cannot connect to mySQL server on localhost
<10061>


Bob Melis wrote:
> Below is my.ini file. I added skip innodb and
> bdb to get the mysqld-nt console to run.

> When I do the mysqld-nt --console, I get:
> ready for connections.

> Does this mean I will need to start mysql this way until
> I resolve the innodb issue or download mysql again?

No, if it starts OK in console mode with skip-innodb,
it _should_ run fine in service mode too (with skip-innodb).

> are there any advantages to upgrading

Use the MySQL feature comparison page:
http://dev.mysql.com/tech-resources/features.html

You might want to prod the MySQL folks and tell them to
update the web page to include MySQL series 5.

Also, you can read the MySQL change history:
http://dev.mysql.com/doc/refman/5.0/en/news.html

It only covers the currently recommended version.
For older versions, you'll have to dig out an
older version of the manual which it's included in:
http://dev.mysql.com/doc/refman/4.1/en/news.html

> I assume 5.0.16 would be used for larger
> applications then I am considering at this time.

No, it's equally suited for small applications.


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

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

David, one more time. Maybe the following (Table mysql.host doesn't
exist.) can shed some light on how I might recover.

I went to mysql 15.6.1. Dealing with InnoDB Initialization Problems
and tried the following:

1. Deleted ibdata, ib_logfiles and .frm files (saved my data first in
another folder so I could retrieve it later).

2. Shut down mysql since it was running.

3. Started mysq at the CMD line with mysqld-nt --standalone and got
the following in my error log.

InnoDB: The first specified data file .\ibdata1 did not exist:
InnoDB: a new database to be created!
051202 21:58:22 InnoDB: Setting file .\ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
051202 21:58:22 InnoDB: Log file .\ib_logfile0 did not exist: new to
be created
InnoDB: Setting log file .\ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
051202 21:58:23 InnoDB: Log file .\ib_logfile1 did not exist: new to
be created
InnoDB: Setting log file .\ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
051202 21:58:32 InnoDB: Started
051202 21:58:32 Fatal error: Can't open privilege tables: Table
'mysql.host' doesn't exist
051202 21:58:32 Aborting

051202 21:58:32 InnoDB: Starting shutdown...
051202 21:58:35 InnoDB: Shutdown completed
051202 21:58:35 mysqld-nt: Shutdown Complete

After initializing the files, InnoDB tried to start but had a Fatal
error. Is there any way to create Table mysql.host that does not exist
so it can open privilege tables? Do you think doing mysql_install_db
would help or would that screw things up, and it would be better to
download and reinstall from scratch?

Bob




-----Original Message-----
From: Bob Melis [mailto:bobmelis@adelphia.net]
Sent: Friday, December 02, 2005 7:18 PM
To: myodbc@lists.mysql.com
Cc: Armin Schoffmann [armin.schoeffmann@aegaeon.de]
Subject: RE: Error 2003: Cannot connect to mySQL server on localhost
<10061>


David, thanks soooo much.

You got my application running again with the skip innodb and bdb in
my.ini file. I will look into installing a later versions of mysql in
the future.

When you say save data files, that of course is the data files I
created. Do I need to save everything under the mysql\data directory
such as ibdata1, ib_logfile0, ib_arch_log_0000000000.

I assume I can reuse the mysql-connector-java file without downloading
it again. Is that correct?

Also, will I need to ...
- uninstall mysql before I download it, or
- just download and unzip it and it will automatically replace the
existing one?

Issue Resolved and thanks again.

Bob

-----Original Message-----
From: David Dindorp [mailto:ddi@dubex.dk]
Sent: Friday, December 02, 2005 5:31 AM
To: Bob Melis
Cc: myodbc@lists.mysql.com
Subject: RE: Error 2003: Cannot connect to mySQL server on localhost
<10061>


Bob Melis wrote:
> Below is my.ini file. I added skip innodb and
> bdb to get the mysqld-nt console to run.

> When I do the mysqld-nt --console, I get:
> ready for connections.

> Does this mean I will need to start mysql this way until
> I resolve the innodb issue or download mysql again?

No, if it starts OK in console mode with skip-innodb,
it _should_ run fine in service mode too (with skip-innodb).

> are there any advantages to upgrading

Use the MySQL feature comparison page:
http://dev.mysql.com/tech-resources/features.html

You might want to prod the MySQL folks and tell them to
update the web page to include MySQL series 5.

Also, you can read the MySQL change history:
http://dev.mysql.com/doc/refman/5.0/en/news.html

It only covers the currently recommended version.
For older versions, you'll have to dig out an
older version of the manual which it's included in:
http://dev.mysql.com/doc/refman/4.1/en/news.html

> I assume 5.0.16 would be used for larger
> applications then I am considering at this time.

No, it's equally suited for small applications.


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

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

Success!! After doing the what I summarized below and restarting my
computer it now works as before with my java application. I forgot to
mention that I removed skip-bdb and skip-innodb from my.ini file.
Also,mysql created the ib_logfile0 the same size as ib_logfile1 which
I guess was needed. I alos but all my .frm files back before I
restarted my computer. The only thing I still need to do is see if I
can read/write to my DB via the CMD window.

Hopefully this will help anyone else that gets into is problem.

Bob


-----Original Message-----
From: Bob Melis [mailto:bobmelis@adelphia.net]
Sent: Friday, December 02, 2005 11:25 PM
To: myodbc@lists.mysql.com
Subject: RE: Error 2003: Cannot connect to mySQL server on localhost
<10061>


David, one more time. Maybe the following (Table mysql.host doesn't
exist.) can shed some light on how I might recover.

I went to mysql 15.6.1. Dealing with InnoDB Initialization Problems
and tried the following:

1. Deleted ibdata, ib_logfiles and .frm files (saved my data first in
another folder so I could retrieve it later).

2. Shut down mysql since it was running.

3. Started mysq at the CMD line with mysqld-nt --standalone and got
the following in my error log.

InnoDB: The first specified data file .\ibdata1 did not exist:
InnoDB: a new database to be created!
051202 21:58:22 InnoDB: Setting file .\ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
051202 21:58:22 InnoDB: Log file .\ib_logfile0 did not exist: new to
be created
InnoDB: Setting log file .\ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
051202 21:58:23 InnoDB: Log file .\ib_logfile1 did not exist: new to
be created
InnoDB: Setting log file .\ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
051202 21:58:32 InnoDB: Started
051202 21:58:32 Fatal error: Can't open privilege tables: Table
'mysql.host' doesn't exist
051202 21:58:32 Aborting

051202 21:58:32 InnoDB: Starting shutdown...
051202 21:58:35 InnoDB: Shutdown completed
051202 21:58:35 mysqld-nt: Shutdown Complete

After initializing the files, InnoDB tried to start but had a Fatal
error. Is there any way to create Table mysql.host that does not exist
so it can open privilege tables? Do you think doing mysql_install_db
would help or would that screw things up, and it would be better to
download and reinstall from scratch?

Bob




-----Original Message-----
From: Bob Melis [mailto:bobmelis@adelphia.net]
Sent: Friday, December 02, 2005 7:18 PM
To: myodbc@lists.mysql.com
Cc: Armin Schoffmann [armin.schoeffmann@aegaeon.de]
Subject: RE: Error 2003: Cannot connect to mySQL server on localhost
<10061>


David, thanks soooo much.

You got my application running again with the skip innodb and bdb in
my.ini file. I will look into installing a later versions of mysql in
the future.

When you say save data files, that of course is the data files I
created. Do I need to save everything under the mysql\data directory
such as ibdata1, ib_logfile0, ib_arch_log_0000000000.

I assume I can reuse the mysql-connector-java file without downloading
it again. Is that correct?

Also, will I need to ...
- uninstall mysql before I download it, or
- just download and unzip it and it will automatically replace the
existing one?

Issue Resolved and thanks again.

Bob

-----Original Message-----
From: David Dindorp [mailto:ddi@dubex.dk]
Sent: Friday, December 02, 2005 5:31 AM
To: Bob Melis
Cc: myodbc@lists.mysql.com
Subject: RE: Error 2003: Cannot connect to mySQL server on localhost
<10061>


Bob Melis wrote:
> Below is my.ini file. I added skip innodb and
> bdb to get the mysqld-nt console to run.

> When I do the mysqld-nt --console, I get:
> ready for connections.

> Does this mean I will need to start mysql this way until
> I resolve the innodb issue or download mysql again?

No, if it starts OK in console mode with skip-innodb,
it _should_ run fine in service mode too (with skip-innodb).

> are there any advantages to upgrading

Use the MySQL feature comparison page:
http://dev.mysql.com/tech-resources/features.html

You might want to prod the MySQL folks and tell them to
update the web page to include MySQL series 5.

Also, you can read the MySQL change history:
http://dev.mysql.com/doc/refman/5.0/en/news.html

It only covers the currently recommended version.
For older versions, you'll have to dig out an
older version of the manual which it's included in:
http://dev.mysql.com/doc/refman/4.1/en/news.html

> I assume 5.0.16 would be used for larger
> applications then I am considering at this time.

No, it's equally suited for small applications.


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