| Bug #40522 | mysql high availability | ||
|---|---|---|---|
| Submitted: | 5 Nov 2008 9:27 | Modified: | 7 Nov 2008 5:25 |
| Reporter: | leo joe | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | MySQL Server | Severity: | S1 (Critical) |
| Version: | 5.0.45-7.el5 | OS: | Linux (Cent OS 5) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | drbd, heartbeat, MySQL | ||
[5 Nov 2008 10:10]
leo joe
For cent os 5
[5 Nov 2008 14:26]
Valeriy Kravchuk
This looks like DRBD (configuration?) problem, not MySQL server bug. Please, report this problem to Linbit.
[7 Nov 2008 4:34]
leo joe
Thanks for reply Valeriy Kravchuk,
I have configured mysql Master Master Replication + DRBD + Heartbeat
after Primary server Fails mysql should mount to secondary server and it should run automatically.
I noticed that after primary server fails the mysql mounted in secondary server, but it fails to start automatically.
here is my drbd.conf
vi /etc/drbd.conf
resource mysql {
protocol C;
#incon-degr-cmd "echo '!DRBD! pri-on-incon-degr' | wall ; sleep 60 ;
#halt -f";
handlers { pri-on-incon-degr "..."; }
startup {
degr-wfc-timeout 120; # 2 minutes.
}
disk {
on-io-error detach;
}
net {
}
syncer {
rate 3M;
#group 1;
#al-extents 257;
}
on mysql01 {
device /dev/drbd0;
disk /dev/hdd6;
address 192.168.1.34:7788;
meta-disk /dev/hdd5[0];
}
on mysql02 {
device /dev/drbd0;
disk /dev/sda5;
address 192.168.1.35:7788;
meta-disk /dev/sda6[0];
}
}
===============================================================================
Heart Beart
vi /etc/ha.d/ha.cf
logfacility daemon
keepalive 1
deadtime 10
warntime 5
initdead 120
udpport 694
ping 192.168.1.1
bcast eth0
auto_failback off
node mysql01
node mysql02
respawn hacluster /usr/lib/heartbeat/ipfail
use_logd yes
logfile /var/log/ha-log
debugfile /var/log/heartbeat-debug.log
==================================================================================
vi /etc/ha.d/haresources
mysql01 IPaddr::192.168.1.92/24 drbddisk::mysql Filesystem::/dev/drbd0::/var/lib/mysql::ext3::defaults mysqld
==================================================================================
Mysql (Primary server)
vi /etc/my.cnf
[mysqld]
datadir=/var/lib/mysql
#datadir=/opt/mysql
#socket=/opt/mysql/mysql.sock
socket=/var/lib/mysql/mysql.sock
server-id=1
auto-increment-increment = 2
auto-increment-offset = 1
master-host = 192.168.1.35
master-user = root
master-password = password
master-port = 3306
log-bin=/var/log/mysql/mysql #information for becoming master added
binlog-do-db=zestadz_development
replicate-do-db=zestadz_development
[mysql.server]
user=mysql
basedir=/var/lib
#relay-log = /var/lib/mysql/slave-relay.log
# Default to using old password format for compatibility with mysql 3.x
# clients (those using the mysqlclient10 compatibility package).
old_passwords=1
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
==================================================================================
Mysql (secondary server)
vi /etc/my.cnf
[mysqld]
datadir=/var/lib/mysql
#datadir=/mnt/mysql/data
socket=/var/lib/mysql/mysql.sock
server-id=2
auto-increment-increment = 2
auto-increment-offset = 2
master-host = 192.168.1.34
master-user = root
master-password = password
master-port = 3306
log-bin=/var/log/mysql/mysql #information for becoming master added
binlog-do-db=zestadz_development
replicate-do-db=zestadz_development
#relay-log=/var/run/mysqld/mysqld-relay-bin
[mysql.server]
user=mysql
basedir=/var/lib
# Default to using old password format for compatibility with mysql 3.x
# clients (those using the mysqlclient10 compatibility package).
old_passwords=1
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
==================================================================================
Can you please help me ?
[7 Nov 2008 5:25]
Valeriy Kravchuk
We're sorry, but the bug system is not the appropriate forum for asking help on using MySQL products. Your problem is not the result of a bug. Support on using our products is available both free in our forums at http://forums.mysql.com/ and for a reasonable fee direct from our skilled support engineers at http://www.mysql.com/support/ Thank you for your interest in MySQL.
Description: I tried to setup Drbd + Mysql master master replication + Heartbeat. while I start heart beat I am getting Stopping High-Availability services: [ OK ] Waiting to allow resource takeover to complete: [ OK ] Starting High-Availability services: 2008/11/05_20:21:33 INFO: Resource is stopped [ OK ] In log i am getting like this Stopping MySQL: [FAILED]^M Stopping MySQL: [FAILED]^M Stopping MySQL: [FAILED]^M Stopping MySQL: [FAILED]^M Stopping MySQL: [FAILED]^M Stopping MySQL: [FAILED]^M Stopping MySQL: [FAILED]^M Stopping MySQL: [FAILED]^M Stopping MySQL: [FAILED]^M Stopping MySQL: [FAILED]^M Stopping MySQL: [FAILED]^M INFO: Success /etc/drbd.conf: line 5: resource: command not found /etc/drbd.conf: line 6: protocol: command not found /etc/drbd.conf: line 9: syntax error near unexpected token `}' /etc/drbd.conf: line 9: ` handlers { pri-on-incon-degr "..."; }' /etc/drbd.conf: line 5: resource: command not found /etc/drbd.conf: line 6: protocol: command not found /etc/drbd.conf: line 9: syntax error near unexpected token `}' /etc/drbd.conf: line 9: ` handlers { pri-on-incon-degr "..."; }' INFO: Success /etc/drbd.conf: line 5: resource: command not found /etc/drbd.conf: line 6: protocol: command not found /etc/drbd.conf: line 9: syntax error near unexpected token `}' /etc/drbd.conf: line 9: ` handlers { pri-on-incon-degr "..."; }' Any Idea please? How to repeat: any Suggested fix: welcome