search for: 1_monitor_0

Displaying 3 results from an estimated 3 matches for "1_monitor_0".

2017 Dec 20
2
glusterfs, ganesh, and pcs rules
...ed: [ tlxdmz-nfs1 tlxdmz-nfs2 ] Clone Set: nfs-grace-clone [nfs-grace] Started: [ tlxdmz-nfs1 tlxdmz-nfs2 ] tlxdmz-nfs1-cluster_ip-1 (ocf::heartbeat:IPaddr): Stopped tlxdmz-nfs2-cluster_ip-1 (ocf::heartbeat:IPaddr): Stopped Failed Actions: * tlxdmz-nfs1-cluster_ip-1_monitor_0 on tlxdmz-nfs2 'not configured' (6): call=23, status=complete, exitreason='IP address (the ip parameter) is mandatory', last-rc-change='Wed Dec 20 09:19:28 2017', queued=0ms, exec=26ms * tlxdmz-nfs2-cluster_ip-1_monitor_0 on tlxdmz-nfs2 'not configured' (6): call...
2017 Dec 21
0
glusterfs, ganesh, and pcs rules
...ed: [ tlxdmz-nfs1 tlxdmz-nfs2 ] ?Clone Set: nfs-grace-clone [nfs-grace] ? ? ?Started: [ tlxdmz-nfs1 tlxdmz-nfs2 ] ?tlxdmz-nfs1-cluster_ip-1? ? ? ?(ocf::heartbeat:IPaddr):? ? ? ? Stopped ?tlxdmz-nfs2-cluster_ip-1? ? ? ?(ocf::heartbeat:IPaddr):? ? ? ? Stopped Failed Actions: * tlxdmz-nfs1-cluster_ip-1_monitor_0 on tlxdmz-nfs2 'not configured' (6): call=23, status=complete, exitreason='IP address (the ip parameter) is mandatory', ? ? last-rc-change='Wed Dec 20 09:19:28 2017', queued=0ms, exec=26ms * tlxdmz-nfs2-cluster_ip-1_monitor_0 on tlxdmz-nfs2 'not configured' (6): call...
2017 Dec 24
1
glusterfs, ganesh, and pcs rules
...t; Clone Set: nfs-grace-clone [nfs-grace] > Started: [ tlxdmz-nfs1 tlxdmz-nfs2 ] > tlxdmz-nfs1-cluster_ip-1 (ocf::heartbeat:IPaddr): Stopped > tlxdmz-nfs2-cluster_ip-1 (ocf::heartbeat:IPaddr): Stopped > > Failed Actions: > * tlxdmz-nfs1-cluster_ip-1_monitor_0 on tlxdmz-nfs2 'not configured' (6): > call=23, status=complete, exitreason='IP address (the ip parameter) is > mandatory', > last-rc-change='Wed Dec 20 09:19:28 2017', queued=0ms, exec=26ms > * tlxdmz-nfs2-cluster_ip-1_monitor_0 on tlxdmz-nfs2 'not confi...