Having chroot Problems with MySQL

[Matt Graham]

From: Mark Phillips <mark at phillipsmarketing.biz>
> On Wed, Jun 2, 2010 at 1:24 PM, Matt Graham <danceswithcrows at usa.net>
wrote:
>> You said you weren't running a syslog daemon inside the chroot, though.
> You win the GOLD STAR for the day! I installed syslog-ng, started mysql and
> got this error message is syslog
> mysqld: Can't start server: Bind on TCP/IP port: Address already in use
 
> The light bulb went on, and the doh! moment happened.....mysql was running
> on the 64 bit squeeze side of the chroot jail.....Once I stopped it, the
> chroot mysql started without a hiccup!

Oops.  Funny how you can't have 2 processes both bound to port 3306 :-)  You
could run both mysqld instances if you changed one of them to use a different
port, or made one of them not use TCP (which is appropriate in some cases,
depending on stuff).  Never would've thought of that since you didn't mention
another mysqld instance on the machine.

> I will install it on ALL my current and new installations ASAP!!!!!

I prefer metalog to syslog, but the important thing is to have something
listening to /dev/log and writing the stuff it gets to some files somewhere so
you can take a look at things when it all goes pear-shaped.  Glad that it
helped,

-- 
Matt G / Dances With Crows
The Crow202 Blog:  http://crow202.org/wordpress/
There is no Darkness in Eternity/But only Light too dim for us to see