search for: exitreason

Displaying 6 results from an estimated 6 matches for "exitreason".

Did you mean: exit_reason
2017 Dec 20
2
glusterfs, ganesh, and pcs rules
...d: [ 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=27, status=complete, exitreason='IP address (the ip parameter) is mandatory...
2017 Dec 21
0
glusterfs, ganesh, and pcs rules
...d: [ 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=27, status=complete, exitreason='IP address (the ip parameter) is mandatory...
2017 Dec 24
1
glusterfs, ganesh, and pcs rules
...] > 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=27, status=complete, exitreason='IP address (the ip param...
2017 Dec 07
4
GlusterFS, Pacemaker, OCF resource agents on CentOS 7
...?? Stopped: [ pcmk01-cr pcmk02-cr ] ?Clone Set: gluster_vol-clone [gluster_vol] ???? gluster_vol??????? (ocf::glusterfs:volume):??????? FAILED pcmk01-cr (blocked) ???? Stopped: [ pcmk02-cr ] Failed Actions: * gluster_data_start_0 on pcmk01-cr 'not configured' (6): call=72, status=complete, exitreason='DANGER! xfs on /dev/cl/lv_drbd is NOT cluster-aware!', ??? last-rc-change='Thu Dec? 7 13:09:28 2017', queued=0ms, exec=250ms * gluster_vol_stop_0 on pcmk01-cr 'unknown error' (1): call=60, status=Timed Out, exitreason='none', ??? last-rc-change='Thu Dec? 7 12:55...
2017 Dec 08
0
GlusterFS, Pacemaker, OCF resource agents on CentOS 7
...] > ?Clone Set: gluster_vol-clone [gluster_vol] > ???? gluster_vol??????? (ocf::glusterfs:volume): FAILED pcmk01-cr > (blocked) > ???? Stopped: [ pcmk02-cr ] > > Failed Actions: > * gluster_data_start_0 on pcmk01-cr 'not configured' (6): call=72, > status=complete, exitreason='DANGER! xfs on /dev/cl/lv_drbd is NOT > cluster-aware!', > ??? last-rc-change='Thu Dec? 7 13:09:28 2017', queued=0ms, exec=250ms > * gluster_vol_stop_0 on pcmk01-cr 'unknown error' (1): call=60, > status=Timed Out, exitreason='none', > ??? last-rc-c...
2020 Jul 22
34
[RFC PATCH v1 00/34] VM introspection - EPT Views and Virtualization Exceptions
This patch series is based on the VM introspection patches (https://lore.kernel.org/kvm/20200721210922.7646-1-alazar at bitdefender.com/), extending the introspection API with EPT Views and Virtualization Exceptions (#VE) support. The purpose of this series is to get an initial feedback and to see if we are on the right track, especially because the changes made to add the EPT views are not small