Last Friday I started a on-line verification for a replicated device
on a 2-nodes active/passive cluster in testig mode and I'm not sure if
it's related (I'll investigate later) but I ended up with one failed
resource:
Current DC: feeble-1 (d7fb07f0-a857-446d-98e6-fce91c1b6094)
2 Nodes configured.
2 Resources configured.
============
Node: feeble-1 (d7fb07f0-a857-446d-98e6-fce91c1b6094): online
Node: feeble-0 (51c8df9a-95a6-4beb-a534-82f20abd2612): online
Master/Slave Set: ms-drbd_id
drbd_id:0 (ocf::heartbeat:drbd): Started feeble-0
drbd_id:1 (ocf::heartbeat:drbd): Master feeble-1
Resource Group: group_id
fs_id (ocf::heartbeat:Filesystem): Started feeble-1
nfs_kernel-id (ocf::bic:nfs-kernel): Started feeble-1
nfs_common-id (ocf::bic:nfs-common): Started feeble-1
ip_id (ocf::heartbeat:IPaddr): Started feeble-1
mysql_id (ocf::heartbeat:mysql): Started feeble-1 (unmanaged) FAILED
apache_id (ocf::heartbeat:apache): Stopped
Failed actions:
mysql_id_stop_0 (node=feeble-1, call=72, rc=-2): Timed Out
apache_id_monitor_30000 (node=feeble-1, call=69, rc=-2): Timed Out
Anyone knows how to get gracefully out of this wedged situation?
regards,
jf
--
<° ><
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
