This issue has bothered me from day one but I never got around to pinning down why. When a fence action takes place it would be great if a reason for the action could be placed in the log.
For example I had a cluster fence its primary node this morning.
May 30 03:34:40 fenced fencing node fpracprox1
May 30 03:34:53 fenced fence fpracprox1 success
Syslog provides no indication of why
May 30 03:33:15 fpracprox1 rgmanager[879803]: [pvevm] VM 100 is running
May 30 03:40:55 fpracprox1 kernel: imklog 5.8.11, log source = /proc/kmsg started.
Is there any specific reason why a reason or some type of clue can't be in the log? Fencing is great, but if you can't figure out why, then its like finding a needle in a hay stack.
For example I had a cluster fence its primary node this morning.
May 30 03:34:40 fenced fencing node fpracprox1
May 30 03:34:53 fenced fence fpracprox1 success
Syslog provides no indication of why
May 30 03:33:15 fpracprox1 rgmanager[879803]: [pvevm] VM 100 is running
May 30 03:40:55 fpracprox1 kernel: imklog 5.8.11, log source = /proc/kmsg started.
Is there any specific reason why a reason or some type of clue can't be in the log? Fencing is great, but if you can't figure out why, then its like finding a needle in a hay stack.
Last edited: