Whenever the probe service takes action on a guest that has stopped responding to probes, the probe service logs an appropriate message in the /var/log/messages file. By default, messages are logged only when probes fail or an action is taken. With the debug option enabled, additional messages are logged when a probe is sent, a response is received, or the probe times out.

The following section provides an example of nondebug log entries. In the example, the foo probe fails three times and causes the a-guest guest to be reset.

2015-10-14T01:12:17.882305+00:00 localhost probed: Probe foo failed
2015-10-14T01:12:43.440805+00:00 localhost probed: message repeated 3 times: [ Probe foo failed]
2015-10-14T01:12:43.441094+00:00 localhost probed: Sequential failures for probe foo have exceeded the threshold (3), running actions
2015-10-14T01:12:43.452570+00:00 localhost probed: a-guest reset performed