We had a cluster fail over happen, but it wasn’t a clean fail over.
Some service are now running on freepbx-b,others still on freepbx-a (drbd_spare, drbd_mysql).
Don’t know why the fail over happened and why mysql is still running on secondary node. Anything wrong with mysql?
What action to take now? Bring individual services, like mysql over to freepbx-b, or put the whole node into standby?
pcs status
Online: [ freepbx-a freepbx-b ]
Full list of resources:
spare_ip (ocf:
IPaddr2): Started freepbx-a
floating_ip (ocf:IPaddr2): Started freepbx-b
Master/Slave Set: ms-asterisk [drbd_asterisk]
Masters: [ freepbx-b ]
Slaves: [ freepbx-a ]
Master/Slave Set: ms-mysql [drbd_mysql]
Masters: [ freepbx-a ]
Slaves: [ freepbx-b ]
Master/Slave Set: ms-httpd [drbd_httpd]
Masters: [ freepbx-b ]
Slaves: [ freepbx-a ]
Master/Slave Set: ms-spare [drbd_spare]
Masters: [ freepbx-a ]
Slaves: [ freepbx-b ]
spare_fs (ocf:Filesystem): Started freepbx-a
Resource Group: mysql
mysql_fs (ocf:Filesystem): Started freepbx-a
mysql_ip (ocf:IPaddr2): Started freepbx-a
mysql_service (ocf:mysql): Started freepbx-a
Resource Group: asterisk
asterisk_fs (ocf:Filesystem): Started freepbx-b
asterisk_ip (ocf:IPaddr2): Started freepbx-b
asterisk_service (ocf:freepbx): Started freepbx-b
Resource Group: httpd
httpd_fs (ocf:Filesystem): Started freepbx-b
httpd_ip (ocf:IPaddr2): Started freepbx-b
httpd_service (ocf:apache): Started freepbx-b
Clone Set: ClusterMon-SMTP-clone [ClusterMon-SMTP]
Started: [ freepbx-a freepbx-b ]
fence_a (stonith:fence_ipmilan): Started freepbx-b
fence_b (stonith:fence_ipmilan): Started freepbx-a