The other day, mysql died on my system for no apparent reason. When I reboot
the machine, based on the script in /etc/rc.d/init.d/mysql, mysql should
start up and it does --somewhat.
Here's the message I get:
[root@myserver mysql]# /etc/rc.d/init.d/mysql start
[root@myserver mysql]# Starting mysqld daemon with databases from
/usr/var/mysql
And it shows up in the process list below...
root 5340 0.0 0.3 1668 828 pts/0 S 21:23 0:00 sh
/usr/bin/safe_
mysql 5365 0.0 0.4 3308 1176 pts/0 S 21:23 0:00
/usr/sbin/mysqld
mysql 5366 0.0 0.4 3308 1176 pts/0 S 21:23 0:00
/usr/sbin/mysqld
mysql 5367 0.0 0.4 3308 1176 pts/0 S 21:23 0:00
/usr/sbin/mysqld
And it logs it to my /usr/var/mysql/server.log as:
/usr/sbin/mysqld, Version: 3.23.21-beta-log, started with:
Tcp port: 3306 Unix socket: /var/lib/mysql/mysql.sock
Time Id Command Argument
But any commands I send to mysql or mysqladmin hangup and nothing ever
happens. I then have to kill -9 to force it to stop.
So now I manually go in and start it, as root with safe_mysqld. Here's what
I get:
[root@myserver mysql]# safe_mysqld
kill 4212: No such process
Starting mysqld daemon with databases from /usr/var/mysql
mysqld daemon ended
It tries to kill a process, but there is no process in the list!
This seems to start it, but then, any commands I send to it just hang the
app.
If I just try to run mysql from command line I get this:
[root@myserver mysql]# mysql
ERROR 2002: Can't connect to local MySQL server through socket
'/var/lib/mysql/m
ysql.sock' (111)
One other thing -- if I try to stop mysql, with:
[root@myserver /etc]# /etc/rc.d/init.d/mysql stop
Killing mysqld with pid 9024
Wait for mysqld to exit\c
It never stops it, just gives up waiting.
One thing I have to consider is some recent DNS work I did. Is it possible
DNS could cause these problems?
I'm really at a loss here. Any help is greatly appreciated.
Thanks,
Jeff
the machine, based on the script in /etc/rc.d/init.d/mysql, mysql should
start up and it does --somewhat.
Here's the message I get:
[root@myserver mysql]# /etc/rc.d/init.d/mysql start
[root@myserver mysql]# Starting mysqld daemon with databases from
/usr/var/mysql
And it shows up in the process list below...
root 5340 0.0 0.3 1668 828 pts/0 S 21:23 0:00 sh
/usr/bin/safe_
mysql 5365 0.0 0.4 3308 1176 pts/0 S 21:23 0:00
/usr/sbin/mysqld
mysql 5366 0.0 0.4 3308 1176 pts/0 S 21:23 0:00
/usr/sbin/mysqld
mysql 5367 0.0 0.4 3308 1176 pts/0 S 21:23 0:00
/usr/sbin/mysqld
And it logs it to my /usr/var/mysql/server.log as:
/usr/sbin/mysqld, Version: 3.23.21-beta-log, started with:
Tcp port: 3306 Unix socket: /var/lib/mysql/mysql.sock
Time Id Command Argument
But any commands I send to mysql or mysqladmin hangup and nothing ever
happens. I then have to kill -9 to force it to stop.
So now I manually go in and start it, as root with safe_mysqld. Here's what
I get:
[root@myserver mysql]# safe_mysqld
kill 4212: No such process
Starting mysqld daemon with databases from /usr/var/mysql
mysqld daemon ended
It tries to kill a process, but there is no process in the list!
This seems to start it, but then, any commands I send to it just hang the
app.
If I just try to run mysql from command line I get this:
[root@myserver mysql]# mysql
ERROR 2002: Can't connect to local MySQL server through socket
'/var/lib/mysql/m
ysql.sock' (111)
One other thing -- if I try to stop mysql, with:
[root@myserver /etc]# /etc/rc.d/init.d/mysql stop
Killing mysqld with pid 9024
Wait for mysqld to exit\c
It never stops it, just gives up waiting.
One thing I have to consider is some recent DNS work I did. Is it possible
DNS could cause these problems?
I'm really at a loss here. Any help is greatly appreciated.
Thanks,
Jeff