Hello,
I am using Heartbeat 2 to failover DRBD and MySQL, however I am
confused as to which IP address to specify where. I have followed the
DRBD guide at http://www.drbd.org/users-guide/s-heartbeat-crm.html
<group ordered="true" collocated="true" id="rg_mysql">
[cut]
<primitive class="ocf" type="IPaddr2"
provider="heartbeat" id="ip_mysql">
<instance_attributes>
<attributes>
<nvpair name="ip" value="192.168.42.1/24"/>
<nvpair name="nic" value="eth0"/>
</attributes>
</instance_attributes>
[cut]
</group>
cibadmin -o resources -C -x hb_mysql.xml
<resources>
[cút]
<group id="rg_mysql">
<primitive class="ocf" type="Filesystem"
provider="heartbeat" id="fs_mysql">
<instance_attributes id="fs_mysql-instance_attributes">
[cut]
</instance_attributes>
</primitive>
<primitive class="ocf" type="IPaddr2"
provider="heartbeat" id="ip_mysql">
<instance_attributes id="ip_mysql-instance_attributes">
<attributes>
<nvpair name="ip" value="10.9.42.1"/>
<nvpair name="nic" value="eth0"/>
</attributes>
</instance_attributes>
</primitive>
<primitive class="lsb" type="mysqld"
provider="heartbeat" id="mysqld"/>
</group>
</resources>
cibadmin -U -x resources.xml
how does
<nvpair name="ip" value="192.168.100.200/24" />
differ from
<nvpair name="ip" value="10.9.42.1"/>
in terms of usage?
[r...@db1 conf]# crm_verify -LV
crm_verify[27010]: 2008/12/13_20:22:55 ERROR: unpack_rsc_op: Hard
error: ip_mysql_monitor_0 failed with rc=2.
crm_verify[27010]: 2008/12/13_20:22:55 ERROR: unpack_rsc_op:
Preventing ip_mysql from re-starting on db1
crm_verify[27010]: 2008/12/13_20:22:55 WARN: unpack_rsc_op:
drbddisk_mysql_monitor_0 found active drbddisk_mysql on db1
crm_verify[27010]: 2008/12/13_20:22:55 WARN: unpack_rsc_op: Processing
failed op drbddisk_mysql_stop_0 on db1: Error
crm_verify[27010]: 2008/12/13_20:22:55 WARN: unpack_rsc_op:
fs_mysql_monitor_0 found active fs_mysql on db1
crm_verify[27010]: 2008/12/13_20:22:55 WARN: unpack_rsc_op:
drbd_mysql:0_monitor_0 found active drbd_mysql:0 in master mode on db1
crm_verify[27010]: 2008/12/13_20:22:55 WARN: unpack_rsc_op:
drbd_mysql:1_monitor_0 found active drbd_mysql:1 in master mode on db1
crm_verify[27010]: 2008/12/13_20:22:55 WARN: unpack_rsc_op: Processing
failed op mysqld_monitor_0 on db1: Error
crm_verify[27010]: 2008/12/13_20:22:55 WARN: unpack_rsc_op: Processing
failed op mysqld_stop_0 on db1: Error
crm_verify[27010]: 2008/12/13_20:22:55 ERROR: unpack_rsc_op: Hard
error: ip_mysql_monitor_0 failed with rc=2.
crm_verify[27010]: 2008/12/13_20:22:55 ERROR: unpack_rsc_op:
Preventing ip_mysql from re-starting on db2
crm_verify[27010]: 2008/12/13_20:22:55 WARN: unpack_rsc_op:
drbd_mysql:0_monitor_0 found active drbd_mysql:0 on db2
crm_verify[27010]: 2008/12/13_20:22:55 WARN: unpack_rsc_op:
drbd_mysql:1_monitor_0 found active drbd_mysql:1 on db2
crm_verify[27010]: 2008/12/13_20:22:55 WARN: unpack_rsc_op: Processing
failed op mysqld_monitor_0 on db2: Error
crm_verify[27010]: 2008/12/13_20:22:55 WARN: unpack_rsc_op: Processing
failed op mysqld_stop_0 on db2: Error
crm_verify[27010]: 2008/12/13_20:22:55 WARN: native_color: Resource
fs_mysql cannot run anywhere
crm_verify[27010]: 2008/12/13_20:22:55 WARN: native_color: Resource
ip_mysql cannot run anywhere
crm_verify[27010]: 2008/12/13_20:22:55 WARN: custom_action: Action
drbddisk_mysql_stop_0 (unmanaged)
crm_verify[27010]: 2008/12/13_20:22:55 ERROR: native_create_actions:
Attempting recovery of resource mysqld
crm_verify[27010]: 2008/12/13_20:22:55 WARN: custom_action: Action
mysqld_stop_0 (unmanaged)
crm_verify[27010]: 2008/12/13_20:22:55 WARN: custom_action: Action
mysqld_stop_0 (unmanaged)
crm_verify[27010]: 2008/12/13_20:22:55 WARN: should_dump_action:
action 5 (drbddisk_mysql_stop_0) was for an unmanaged resource
(drbddisk_mysql)
crm_verify[27010]: 2008/12/13_20:22:55 WARN: should_dump_action:
action 7 (mysqld_stop_0) was for an unmanaged resource (mysqld)
crm_verify[27010]: 2008/12/13_20:22:55 WARN: should_dump_action:
action 8 (mysqld_stop_0) was for an unmanaged resource (mysqld)
crm_verify[27010]: 2008/12/13_20:22:55 WARN: should_dump_action:
action 5 (drbddisk_mysql_stop_0) was for an unmanaged resource
(drbddisk_mysql)
crm_verify[27010]: 2008/12/13_20:22:55 WARN: should_dump_action:
action 7 (mysqld_stop_0) was for an unmanaged resource (mysqld)
crm_verify[27010]: 2008/12/13_20:22:55 WARN: should_dump_action:
action 8 (mysqld_stop_0) was for an unmanaged resource (mysqld)
crm_verify[27010]: 2008/12/13_20:22:55 WARN: should_dump_action:
action 7 (mysqld_stop_0) was for an unmanaged resource (mysqld)
crm_verify[27010]: 2008/12/13_20:22:55 WARN: should_dump_action:
action 8 (mysqld_stop_0) was for an unmanaged resource (mysqld)
crm_verify[27010]: 2008/12/13_20:22:55 WARN: should_dump_action:
action 5 (drbddisk_mysql_stop_0) was for an unmanaged resource
(drbddisk_mysql)
crm_verify[27010]: 2008/12/13_20:22:55 WARN: should_dump_action:
action 7 (mysqld_stop_0) was for an unmanaged resource (mysqld)
crm_verify[27010]: 2008/12/13_20:22:55 WARN: should_dump_action:
action 8 (mysqld_stop_0) was for an unmanaged resource (mysqld)
crm_verify[27010]: 2008/12/13_20:22:55 WARN: should_dump_action:
action 5 (drbddisk_mysql_stop_0) was for an unmanaged resource
(drbddisk_mysql)
crm_verify[27010]: 2008/12/13_20:22:55 WARN: should_dump_action:
action 7 (mysqld_stop_0) was for an unmanaged resource (mysqld)
crm_verify[27010]: 2008/12/13_20:22:55 WARN: should_dump_action:
action 8 (mysqld_stop_0) was for an unmanaged resource (mysqld)
Warnings found during check: config may not be valid
I also have an occasional error in /var/log/messages:
Dec 13 20:47:14 db1 lrmd: [27522]: info: RA output:
(drbddisk_mysql:monitor:stderr) /etc/drbd.conf: line 10: resource:
command not found
and I'm not sure why drbd.conf is getting executed. Is that a ha.cf config?
Many thanks,
Andrew
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
