On Tue, Nov 24, 2009 at 8:28 AM, Mark Beierl <m...@jemms.net> wrote: > The TIME_WAIT is not an active socket, it's the remnant of a previous > connection. I have no idea at all why mysqld has moved to 127.0.1.1. > Is the bind address config line set to the host name and is the host > name entry in /etc/hosts 127.0.1.1? > > Unfortunately, I know very little about mysql, so I can't point you in > the right direction for configuration... > > Regards, > Mark > > Adam Hardy wrote: >> You're right. The result from netstat was: >> >> >> tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 2557/mysqld >> >> after changing the bindaddress config in the mysql config as per the docs to >> free up networking, it then gives this result: >> >> adam@isengard:~$ sudo netstat -napt | grep 3306 >> tcp 0 0 127.0.1.1:3306 0.0.0.0:* LISTEN 16473/mysqld >> tcp 0 0 127.0.1.1:53067 127.0.1.1:3306 TIME_WAIT - >> >> which looks weird. But then it's probably just because I don't have much >> experience in this area. Why has it switched over to 127.0.1.1 ? >> >> Thanks >> Adam >>
The mysql configuration file is my.cnf Its probably in /etc/ somewhere By default mysql listens on the localhost interface only. you can skip networking completely and just use pipes/sockets by using the skip-networking directive in the my.cnf file. Or you can add a bind-address directive to my.cnf. bind-address 0.0.0.0 will listen on all interfaces a series of bind-address x.x.x.x will specify a list of interfaces to listen on (don't forget to include localhost) Rance