Port parameter at command line is ignored

Bug #215595 reported by Ruben Gomez
2
Affects Status Importance Assigned to Milestone
mysql-dfsg-5.0 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Hi I'm unsuccessfully trying to start a tunneled connection on mysql, after a bit of suffering I've discovered that the mysql client command is just ignoring the "--port=[n]" or "-P [n]" parameters.

BTW I'm on Hardy Heron beta amd64 arch.

Thanks

Ruben Gomez (rkg-morgan)
description: updated
description: updated
description: updated
Revision history for this message
Dustin Kirkland  (kirkland) wrote : Re: [Bug 215595] [NEW] Port parameter at command line is ignored

Hi,

What do you mean by 'start a tunneled connection on mysql' ?

Generally, "tunneled connections" refer to stunnel or ssh port
forwarding. In which case, you'd ssh from one machine to your mysql
server and use "local port forwarding". See the ssh man page.

Or are you just simply trying to run the mysql client from one machine
to the other? First check to make sure you can connect to the server
from the server using the mysql against localhost. You might also
sanity check your settings in /etc/mysql/my.cnf

:-Dustin

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Thanks for the bug report and helping make Ubuntu better. We're going to need a bit more information about what you're doing to proceed.

Changed in mysql-dfsg-5.0:
status: New → Incomplete
Revision history for this message
Ruben Gomez (rkg-morgan) wrote :

Hi, I've used tunneled connections for a while, in several OS, just using SSH, evaluating the problem is quite simple, if you try an alternative (unused) port calling the mysql client executable at localhost, the connection should fail, but always starts OK. It's always using the default port ignoring the specified parameter.

Revision history for this message
Mathias Gug (mathiaz) wrote :

Could you post the exact command line you're using to connect to the mysql server ?

Note that the -P option should be used in conjunction with the -h option to specify which host to connect to and that using localhost as a host for -h will force the client to use the socket instead of the loopback address.

Revision history for this message
Ruben Gomez (rkg-morgan) wrote :

Oh, you're right Mathias using 127.0.0.1 everything is OK. A strange behavior anyway... Sorry about my wrong info.

Changed in mysql-dfsg-5.0:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.