I have tried to force a cpanel update, I have tried to force a mysql update. I also change the reset the root password to the server as well as tried to reset the mysql password.
One tip I saw was to move and rename /var/lib/mysql to /var/lib/mysql.bak and for an mysqlupdate, then I freaked when all my databases disappeared. So I moved the mysql.bak to mysql
Here is the error message:
Starting MySQL. ERROR! Manager of pid-file quit without updating file.
I just restarted my server and here is what is in the /usr/cpanel/log/error_log file:
Code:
[2011-03-28 14:23:12 -0400] warn [dbstoregrants] Error while connecting to MySQL. Failover enacted. at /usr/local/cpanel/Cpanel/Mysql.pm line 44
Cpanel::Mysql::new('Cpanel::Mysql') called at /usr/local/cpanel/bin/dbstoregrants line 74
main::dump_mysql_sql() called at /usr/local/cpanel/bin/dbstoregrants line 48
[2011-03-28 14:23:12 -0400] warn [dbstoregrants] DBI connect('mysql:localhost','root',...) failed: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) at /usr/local/cpanel/Cpanel/Mysql.pm line 39
at /usr/local/cpanel/Cpanel/Mysql.pm line 45
Cpanel::Mysql::new('Cpanel::Mysql') called at /usr/local/cpanel/bin/dbstoregrants line 74
main::dump_mysql_sql() called at /usr/local/cpanel/bin/dbstoregrants line 48
mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)'
Check that mysqld is running and that the socket: '/var/lib/mysql/mysql.sock' exists!
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
[2011-03-28 14:27:12 -0400] warn [dbstoregrants] Error while connecting to MySQL. Failover enacted. at /usr/local/cpanel/Cpanel/Mysql.pm line 44
Cpanel::Mysql::new('Cpanel::Mysql') called at /usr/local/cpanel/bin/dbstoregrants line 74
main::dump_mysql_sql() called at /usr/local/cpanel/bin/dbstoregrants line 48
[2011-03-28 14:27:12 -0400] warn [dbstoregrants] DBI connect('mysql:localhost','root',...) failed: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) at /usr/local/cpanel/Cpanel/Mysql.pm line 39
at /usr/local/cpanel/Cpanel/Mysql.pm line 45
Cpanel::Mysql::new('Cpanel::Mysql') called at /usr/local/cpanel/bin/dbstoregrants line 74
main::dump_mysql_sql() called at /usr/local/cpanel/bin/dbstoregrants line 48
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
/usr/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)'
Check that mysqld is running and that the socket: '/var/lib/mysql/mysql.sock' exists!
[2011-03-28 14:27:42 -0400] warn [dbstoregrants] Error while connecting to MySQL. Failover enacted. at /usr/local/cpanel/Cpanel/Mysql.pm line 44
Cpanel::Mysql::new('Cpanel::Mysql') called at /usr/local/cpanel/bin/dbstoregrants line 74
main::dump_mysql_sql() called at /usr/local/cpanel/bin/dbstoregrants line 48
[2011-03-28 14:27:42 -0400] warn [dbstoregrants] DBI connect('mysql:localhost','root',...) failed: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) at /usr/local/cpanel/Cpanel/Mysql.pm line 39
at /usr/local/cpanel/Cpanel/Mysql.pm line 45
Cpanel::Mysql::new('Cpanel::Mysql') called at /usr/local/cpanel/bin/dbstoregrants line 74
main::dump_mysql_sql() called at /usr/local/cpanel/bin/dbstoregrants line 48
mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)'
Check that mysqld is running and that the socket: '/var/lib/mysql/mysql.sock' exists!
[2011-03-28 14:30:01 -0400] warn [mysqluserstore] Unable to query MySQL database at localhost at /usr/local/cpanel/bin/mysqluserstore line 37
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
/usr/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)'
Check that mysqld is running and that the socket: '/var/lib/mysql/mysql.sock' exists!
[2011-03-28 14:38:42 -0400] warn [dbstoregrants] Error while connecting to MySQL. Failover enacted. at /usr/local/cpanel/Cpanel/Mysql.pm line 44
Cpanel::Mysql::new('Cpanel::Mysql') called at /usr/local/cpanel/bin/dbstoregrants line 74
main::dump_mysql_sql() called at /usr/local/cpanel/bin/dbstoregrants line 48
[2011-03-28 14:38:42 -0400] warn [dbstoregrants] DBI connect('mysql:localhost','root',...) failed: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) at /usr/local/cpanel/Cpanel/Mysql.pm line 39
at /usr/local/cpanel/Cpanel/Mysql.pm line 45
Cpanel::Mysql::new('Cpanel::Mysql') called at /usr/local/cpanel/bin/dbstoregrants line 74
main::dump_mysql_sql() called at /usr/local/cpanel/bin/dbstoregrants line 48
mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)'
Check that mysqld is running and that the socket: '/var/lib/mysql/mysql.sock' exists!
-- RESTART MARKER (PID 25793 at 1301339011)--
[2011-03-28 15:03:32 -0400] info [cpanellogd] Unable to load summary files: /var/cpanel/bandwidth/smb.hour, /var/cpanel/bandwidth/smb.5min
Building global cache for cpanel...Done
[2011-03-28 15:09:16 -0400] warn [quotacheck] User file '/var/cpanel/users/root' is empty or non-existent. at /usr/local/cpanel/Cpanel/Config/LoadCpUserFile.pm line 106
Cpanel::Config::LoadCpUserFile::_load('root', undef, 0) called at /usr/local/cpanel/Cpanel/Config/LoadCpUserFile.pm line 25
Cpanel::Config::LoadCpUserFile::load('root') called at /usr/local/cpanel/Cpanel/Config/LoadCpUserFile.pm line 252
Cpanel::Config::LoadCpUserFile::loadcpuserfile('root') called at /scripts/quotacheck line 84
[2011-03-28 15:09:16 -0400] warn [quotacheck] Failed to load cPanel user file for root at /usr/local/cpanel/Cpanel/Config/LoadCpUserFile.pm line 28
Cpanel::Config::LoadCpUserFile::load('root') called at /usr/local/cpanel/Cpanel/Config/LoadCpUserFile.pm line 252
Cpanel::Config::LoadCpUserFile::loadcpuserfile('root') called at /scripts/quotacheck line 84
[2011-03-28 15:12:08 -0400] warn [securemysql] Unable to determine MySQL data directory from mysqladmin variables. at /usr/local/cpanel/Cpanel/MysqlUtils.pm line 109
Cpanel::MysqlUtils::getmysqldir() called at /scripts/securemysql line 140
[2011-03-28 15:12:18 -0400] info [apache_conf_distiller] 'local' datastore in use (/var/cpanel/conf/apache/local)
[2011-03-28 15:12:22 -0400] info [realadduser] No password specified for cpanel
[2011-03-28 15:12:22 -0400] die [realadduser] User cpanel already exists
[2011-03-28 15:12:22 -0400] info [realadduser] No password specified for ftp
[2011-03-28 15:12:22 -0400] die [realadduser] User ftp already exists
-- RESTART MARKER (PID 20457 at 1301339605)--
Building global cache for cpanel...Done
/scripts/mysqlpasswd: pass is blank
/scripts/mysqlpasswd: pass is blank
/usr/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)'
Check that mysqld is running and that the socket: '/var/lib/mysql/mysql.sock' exists!
mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)'
Check that mysqld is running and that the socket: '/var/lib/mysql/mysql.sock' exists!
[2011-03-28 15:26:06 -0400] warn [securemysql] Unable to determine MySQL data directory from mysqladmin variables. at /usr/local/cpanel/Cpanel/MysqlUtils.pm line 109
Cpanel::MysqlUtils::getmysqldir() called at /scripts/securemysql line 140
[2011-03-28 15:29:44 -0400] warn [quotacheck] User file '/var/cpanel/users/root' is empty or non-existent. at /usr/local/cpanel/Cpanel/Config/LoadCpUserFile.pm line 106
Cpanel::Config::LoadCpUserFile::_load('root', undef, 0) called at /usr/local/cpanel/Cpanel/Config/LoadCpUserFile.pm line 25
Cpanel::Config::LoadCpUserFile::load('root') called at /usr/local/cpanel/Cpanel/Config/LoadCpUserFile.pm line 252
Cpanel::Config::LoadCpUserFile::loadcpuserfile('root') called at /scripts/quotacheck line 84
[2011-03-28 15:29:44 -0400] warn [quotacheck] Failed to load cPanel user file for root at /usr/local/cpanel/Cpanel/Config/LoadCpUserFile.pm line 28
Cpanel::Config::LoadCpUserFile::load('root') called at /usr/local/cpanel/Cpanel/Config/LoadCpUserFile.pm line 252
Cpanel::Config::LoadCpUserFile::loadcpuserfile('root') called at /scripts/quotacheck line 84
[2011-03-28 15:31:15 -0400] info [apache_conf_distiller] 'local' datastore in use (/var/cpanel/conf/apache/local)
[2011-03-28 15:31:16 -0400] info [realadduser] No password specified for cpanel
[2011-03-28 15:31:16 -0400] die [realadduser] User cpanel already exists
[2011-03-28 15:31:16 -0400] info [realadduser] No password specified for ftp
[2011-03-28 15:31:16 -0400] die [realadduser] User ftp already exists
-- RESTART MARKER (PID 20208 at 1301340774)--
Building global cache for cpanel...Done
-- RESTART MARKER (PID 20235 at 1301341551)--
Building global cache for cpanel...Done
This is what is the the hostname.err file:
Code:
110328 15:45:18 mysqld started
110328 15:45:18 [Warning] Changed limits: max_open_files: 65535 max_connections: 500 table_cache: 32512
InnoDB: ##########################################################
InnoDB: WARNING!
InnoDB: The log sequence number in ibdata files is higher
InnoDB: than the log sequence number in the ib_logfiles! Are you sure
InnoDB: you are using the right ib_logfiles to start up the database?
InnoDB: Log sequence number in ib_logfiles is 0 977688, log
InnoDB: sequence numbers stamped to ibdata file headers are between
InnoDB: 589505315 589505315 and 589505315 589505315.
InnoDB: ##########################################################
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
110328 15:45:18 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Error: page n:o stored in the page read in is 538976288, should be 3!
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 3.
InnoDB: You may have to recover from a backup.
110328 15:45:19 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex
) ;InnoDB: End of page dump 110328 14:38:24 InnoDB: Page checksum 1508866187, prior-to-4.0.14-form checksum 3161919040 InnoDB: stored checksum 538976288, prior-to-4.0.14-form stored checksum 236985105 InnoDB: Page lsn 538976288 538976288, low 4 bytes of lsn at page end 10651 InnoDB: Page number (if stored to page already) 538976288, InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 538976288 InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 3. 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 InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html InnoDB: about forcing recovery. InnoDB: Ending processing because of a corrupt database page. se page. ) ;InnoDB: End of page dump
110328 15:45:19 InnoDB: Page checksum 2747739185, prior-to-4.0.14-form checksum 3161919040
InnoDB: stored checksum 538976288, prior-to-4.0.14-form stored checksum 236985105
InnoDB: Page lsn 538976288 538976288, low 4 bytes of lsn at page end 10651
InnoDB: Page number (if stored to page already) 538976288,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 538976288
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 3.
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 InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
110328 15:45:19 mysqld ended
110328 15:46:31 mysqld started
110328 15:46:31 [Warning] Changed limits: max_open_files: 65535 max_connections: 500 table_cache: 32512
InnoDB: ##########################################################
InnoDB: WARNING!
InnoDB: The log sequence number in ibdata files is higher
InnoDB: than the log sequence number in the ib_logfiles! Are you sure
InnoDB: you are using the right ib_logfiles to start up the database?
InnoDB: Log sequence number in ib_logfiles is 0 977688, log
InnoDB: sequence numbers stamped to ibdata file headers are between
InnoDB: 589505315 589505315 and 589505315 589505315.
InnoDB: ##########################################################
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
110328 15:46:31 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Error: page n:o stored in the page read in is 538976288, should be 3!
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 3.
InnoDB: You may have to recover from a backup.
110328 15:46:32 InnoDB: Page dump in ascii and hex (16384 bytes):
) ;InnoDB: End of page dump 110328 14:38:24 InnoDB: Page checksum 1508866187, prior-to-4.0.14-form checksum 3161919040 InnoDB: stored checksum 538976288, prior-to-4.0.14-form stored checksum 236985105 InnoDB: Page lsn 538976288 538976288, low 4 bytes of lsn at page end 10651 InnoDB: Page number (if stored to page already) 538976288, InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 538976288 InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 3. 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 InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html InnoDB: about forcing recovery. InnoDB: Ending processing because of a corrupt database page. se page. ) ;InnoDB: End of page dump
110328 15:46:32 InnoDB: Page checksum 2747739185, prior-to-4.0.14-form checksum 3161919040
InnoDB: stored checksum 538976288, prior-to-4.0.14-form stored checksum 236985105
InnoDB: Page lsn 538976288 538976288, low 4 bytes of lsn at page end 10651
InnoDB: Page number (if stored to page already) 538976288,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 538976288
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 3.
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 InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
110328 15:46:32 mysqld ended
110328 15:50:57 mysqld started
110328 15:50:57 [Warning] Changed limits: max_open_files: 65535 max_connections: 500 table_cache: 32512
InnoDB: ##########################################################
InnoDB: WARNING!
InnoDB: The log sequence number in ibdata files is higher
InnoDB: than the log sequence number in the ib_logfiles! Are you sure
InnoDB: you are using the right ib_logfiles to start up the database?
InnoDB: Log sequence number in ib_logfiles is 0 977688, log
InnoDB: sequence numbers stamped to ibdata file headers are between
InnoDB: 589505315 589505315 and 589505315 589505315.
InnoDB: ##########################################################
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
110328 15:50:57 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Error: page n:o stored in the page read in is 538976288, should be 3!
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 3.
InnoDB: You may have to recover from a backup.
110328 15:50:57 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex
) ;InnoDB: End of page dump 110328 14:38:24 InnoDB: Page checksum 1508866187, prior-to-4.0.14-form checksum 3161919040 InnoDB: stored checksum 538976288, prior-to-4.0.14-form stored checksum 236985105 InnoDB: Page lsn 538976288 538976288, low 4 bytes of lsn at page end 10651 InnoDB: Page number (if stored to page already) 538976288, InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 538976288 InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 3. 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 InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html InnoDB: about forcing recovery. InnoDB: Ending processing because of a corrupt database page. se page. ) ;InnoDB: End of page dump
110328 15:50:58 InnoDB: Page checksum 2747739185, prior-to-4.0.14-form checksum 3161919040
InnoDB: stored checksum 538976288, prior-to-4.0.14-form stored checksum 236985105
InnoDB: Page lsn 538976288 538976288, low 4 bytes of lsn at page end 10651
InnoDB: Page number (if stored to page already) 538976288,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 538976288
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 3.
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 InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
110328 15:50:58 mysqld ended