You have been subscribed to a public bug:
Binary package hint: upstart
new install of ubuntu-10.04-server-i386.iso
spent 3 hours attempting to connect to mySQL using 127.0.0.1:3606
for instance, telnet 127.0.0.1 3606
should return something like:
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
@
5.1.41-3ubuntu12.3 (gibberesh)Connection closed by foreign host.
always and forever mySQL is forced to use the socket or nothing.
Have disabled apparmor, disabled the default configs etc.
but somehow no matter what I try, it always gets overridden and refuses
connections on the port.
this is the case even though the mySQL log itself says that it is listening on
the port + socket.
100618 1:32:29 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12.3' socket: '/var/run/mysqld/mysqld.sock' port:
3306 (Ubuntu)
finally I manually start mySQL and totally bypass the rc/upstart system. and
finally I can indeed connect using the port.
This Works:
/usr/sbin/mysqld --bind-address=127.0.0.1 --datadir=/var/lib/mysql
--user=mysql --pid-file=/var/run/mysqld/mysqld.pid --skip-external-locking
--port=3606 --socket=/var/run/mysqld/mysqld.sock &
except that the mysql client program itself is still hardcoded in some
way to only use the socket despite it's config file clearly telling it
to use the port. and despite me telling it on the command line that
--port=3606
I find this situation to be rather uncharming and unendearing. ;-o
There are a lot of valid reasons for programs to want to use ports, you
should allow the programmer to decided about the security issues, you
should not force people into a straight-jacket and padded room because
they *might* hurt themselves. -- guard rails yes, locked padded rooms,
No!
I am not inclined to reverse engineer the entire upstart system in order
to find this problem. actually, this points out a very serious problem
with the upstart design, everything is now hidden into obscurity and
problems become impossible to find and fix without huge effort.
I can work around this issue for now by writing my own init script.
But this whole mess needs to be rethought and mySQL Ports MUST be
enabled to function.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: upstart 0.6.5-6
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Fri Jun 18 02:41:04 2010
InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release i386
(20100427)
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: upstart
** Affects: mysql-dfsg-5.1 (Ubuntu)
Importance: Undecided
Status: Incomplete
** Tags: apport-bug i386 lucid
--
impossible to use Ports on mySQL - Upstart/Config Problem
https://bugs.launchpad.net/bugs/595877
You received this bug notification because you are a member of Ubuntu Server
Team, which is subscribed to mysql-dfsg-5.1 in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
