Forum Moderators: open
When I stop the already dead mysql
it says:
/etc/rc.d/init.d/mysql stop
"No mysqld pid file found."
and I can restart and it will stay running
for a short while anywhere from 10 mins to
a couple of hours.mysqladmin -p version
mysqladmin Ver 8.40 Distrib 4.0.23,
for pc-linux on i686
Server version 4.0.23-standard
Protocol version 10
Connection Localhost via UNIX socket
UNIX socket /tmp/mysql.sock
Uptime: 5 sec
and when it is down:
mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)'
Check that mysqld is running and that the socket: '/tmp/mysql.sock' exists!
the sock exists when it is running
and then dissapears.
Something seems to be killing it....
ANY SUGGESTIONS are APPRECIATED!
InnoDB: Page may be an update undo log page
InnoDB: Page may be an index page where index id is 0 40
InnoDB: (index `PRIMARY` of table `piprd/Broadcast`)
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 2280.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
Number of processes running now: 0
051211 11:37:03 mysqld restarted
SO it looks like data corruption.
Any way to work around the corruption?
I presume we need to replace the HD?
OR is there some utility to mark this place
as bad (page 2280) and keep running?
