unable to start mysql on RHEL6.2

pix9 · 06-18-2014, 04:53 PM

Hi Firends,
I am not able to start mysql on one of the systems. Here is what I did to to get into this trouble
Mysql was already running on the server, was master server, I gracefully stopped by running following command.

sudo mysqladmin flush-tables && sudo mysqladmin flush-tables && sudo mysqladmin flush-tables && sudo /etc/init.d/mysqld stop

after that I synced data on other 2 servers
using rsync

OS/package and mysql details OS RHEL6.2

Code:

$ uname -r
2.6.32-358.2.1.el6.x86_64

$ rpm -qa|grep  mysql
php-mysql-5.3.3-3.el6_1.3.x86_64
mysql-5.1.52-1.el6_0.1.x86_64
mysql-server-5.1.52-1.el6_0.1.x86_64
mysql-libs-5.1.52-1.el6_0.1.x86_64

after that I tried starting mysql but it didin't started.
below is my my.cnf file

Code:

$ cat /etc/my.cnf
[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
server-id=833
report-host=X.X.X.X
log-bin=/var/log/mysql/binary/mysql-bin.log

innodb_file_per_table

[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
[mysqldump]
quick
max_allowed_packet=64M

[myisamchk]
key_buffer=256M
sort_buffer_size=256M
read_buffer=2M
write_buffer=2M

[mysqlhotcopy]
interactive-timeout

#note I've replace ip address with X.X.X.X for security reasons

permissions on data directory are fine it is mysql.mysql

following is the error I am getting in /var/log/mysqld.log
(NOTE: log was too big to be pasted over here so used pastebin insted.)

http://pastebin.com/Mmz2D31m

Thank you for your efforts and time.

Regards

AlucardZero · 06-18-2014, 05:47 PM

Did you read the log?

Code:

InnoDB: Starting crash recovery.
...
InnoDB: Page directory corruption: infimum not pointed to
140619 
...
InnoDB: Error: trying to access a stray pointer 0x80007fbcde84bff8
InnoDB: buf pool start is at 0x7fbcde83c000, end at 0x7fbcdf03c000
InnoDB: Probable reason is database corruption or memory
InnoDB: corruption. If this happens in an InnoDB database recovery, see
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: how to force recovery.

Did you consult http://dev.mysql.com/doc/refman/5.1/...-recovery.html ?

pix9 · 06-18-2014, 06:53 PM

yes I tried those options of

innodb_force_recovery = 1 upto 6 but didn't worked.