mySQL mystery....

Every few days late at night... between 12AM and 2AM mySQL will stop working. It cant be restarted untill I kill the last one running but nothing can be read from the databse and the non wokring mySQL process shows 0% CPU usage. I checked all the crons and theres nothing out of the ordinary at those times.

It appears there are porcesses hanging... but that souldnt totally halt mySQL... This only happens every few days wich is more annoying becasue I dont know when to watch for it. Anybody think they can help?

(RH 8.0 + mySQL 3.23.52)

Heres what the logs say.


Code: 
Number of processes running now: 1
mysqld process hanging, pid 9666 - killed
030409 00:05:57  mysqld restarted
Cannot initialize InnoDB as 'innodb_data_file_path' is not set.
If you do not want to use transactional InnoDB tables, add a line
skip-innodb
to the [mysqld] section of init parameters in your my.cnf
or my.ini. If you want to use InnoDB tables, add to the [mysqld]
section, for example,
innodb_data_file_path = ibdata1:10M:autoextend
But to get good performance you should adjust for your hardware
the InnoDB startup options listed in section 2 at
http://www.innodb.com/ibman.html
030409  0:05:57  Found an entry in the 'db' table with empty database name; Skipped
/usr/libexec/mysqld: ready for connections

Number of processes running now: 1
mysqld process hanging, pid 5529 - killed
030409 00:05:58  mysqld restarted
Cannot initialize InnoDB as 'innodb_data_file_path' is not set.
If you do not want to use transactional InnoDB tables, add a line
skip-innodb
to the [mysqld] section of init parameters in your my.cnf
or my.ini. If you want to use InnoDB tables, add to the [mysqld]
section, for example,
innodb_data_file_path = ibdata1:10M:autoextend
But to get good performance you should adjust for your hardware
the InnoDB startup options listed in section 2 at
http://www.innodb.com/ibman.html
030409  0:05:58  Found an entry in the 'db' table with empty database name; Skipped
/usr/libexec/mysqld: ready for connections

Number of processes running now: 1
mysqld process hanging, pid 5554 - killed
030409 00:06:07  mysqld restarted
Cannot initialize InnoDB as 'innodb_data_file_path' is not set.
If you do not want to use transactional InnoDB tables, add a line
skip-innodb
to the [mysqld] section of init parameters in your my.cnf
or my.ini. If you want to use InnoDB tables, add to the [mysqld]
section, for example,
innodb_data_file_path = ibdata1:10M:autoextend
But to get good performance you should adjust for your hardware
the InnoDB startup options listed in section 2 at
http://www.innodb.com/ibman.html
030409  0:06:08  Found an entry in the 'db' table with empty database name; Skipped
/usr/libexec/mysqld: ready for connections


##-----THIS IS THE POINT WHERE MYSQL STOPPS WORKING-----##

Number of processes running now: 2
mysqld process hanging, pid 5583 - killed
mysqld process hanging, pid 5583 - killed
030409 00:06:08  mysqld restarted
030409  0:06:08  Can't start server: Bind on TCP/IP port: Address already in use
030409  0:06:08  Do you already have another mysqld server running on port: 3306 ?
030409  0:06:08  Aborting

030409  0:06:08  /usr/libexec/mysqld: Shutdown Complete

030409 00:06:08  mysqld ended

030409 00:08:24  mysqld started
030409  0:08:24  Can't start server: Bind on TCP/IP port: Address already in use
030409  0:08:24  Do you already have another mysqld server running on port: 3306 ?
030409  0:08:24  Aborting

030409  0:08:24  /usr/libexec/mysqld: Shutdown Complete

 

 

 

 

Top