Stale State File

Issue #943 resolved

js290 created an issue 2020-10-26

My openvpn monit config gets into a weird state where it no longer monitors. Here’s the config:

‌

check process openvpn with pidfile /run/openvpn/protonvpn.pid
  start program = "/bin/systemctl start openvpn"
  stop program = "/bin/systemctl stop openvpn"
  if failed host 9.9.9.9 port 53 type tcp protocol dns retry 5 then stop

check network vpn with interface tun0
  start program = "/bin/systemctl start openvpn"
  stop program = "/bin/systemctl stop openvpn"
  if failed link then restart

Something happens, and the check process portion stops running but the network portion keeps running. Debug output:

[EDT Oct 26 01:43:35] info     : Monit daemon with pid [28064] stopped
[EDT Oct 26 01:43:35] info     : 'chromebox' Monit 5.26.0 stopped
[EDT Oct 26 01:43:35] debug    : pidfile '/run/monit.pid' does not exist
[EDT Oct 26 01:43:35] info     : Starting Monit 5.26.0 daemon
[EDT Oct 26 01:43:35] info     : 'chromebox' Monit 5.26.0 started
[EDT Oct 26 01:43:35] debug    : Processing postponed events queue
[EDT Oct 26 01:43:35] debug    : Cannot open proc file '/proc/29093/stat' -- No such file or directory
[EDT Oct 26 01:43:35] debug    : system statistic error -- cannot read /proc/29093/stat
[EDT Oct 26 01:43:35] debug    : Cannot open proc file '/proc/29094/stat' -- No such file or directory
[EDT Oct 26 01:43:35] debug    : system statistic error -- cannot read /proc/29094/stat
[EDT Oct 26 01:43:35] debug    : Cannot open proc file '/proc/29099/stat' -- No such file or directory
[EDT Oct 26 01:43:35] debug    : system statistic error -- cannot read /proc/29099/stat
[EDT Oct 26 01:43:35] debug    : Cannot open proc file '/proc/29103/stat' -- No such file or directory
[EDT Oct 26 01:43:35] debug    : system statistic error -- cannot read /proc/29103/stat
[EDT Oct 26 01:43:35] debug    : 'vpn' link data collection succeeded
[EDT Oct 26 01:43:35] debug    : 'vpn' link up
[EDT Oct 26 01:43:35] debug    : 'vpn' upload errors check succeeded
[EDT Oct 26 01:43:35] debug    : 'vpn' download errors check succeeded
[EDT Oct 26 01:43:40] debug    : Socket test failed for [192.5.5.241]:53 -- Connection timed out
[EDT Oct 26 01:43:40] warning  : 'internet' failed protocol test [DNS] at [192.5.5.241]:53 [TCP/IP] -- Connection timed out (atte
mpt 1/5)

‌

The ‘internet’ check fails because openvpn is no longer running correctly, which monit has gotten into a state where it’s no longer checking ‘openvpn’ as configured. I end up deleting /var/lib/monit/state file, restart monit, and it starts working again:

[EDT Oct 26 02:27:19] info     : Reinitializing Monit -- control file '/etc/monit/monitrc'
[EDT Oct 26 02:27:19] info     : 'chromebox' Monit reloaded
[EDT Oct 26 02:27:19] debug    : Processing postponed events queue
[EDT Oct 26 02:27:19] debug    : 'pihole-FTL' process is running with pid 10646
[EDT Oct 26 02:27:19] debug    : 'pihole-FTL' zombie check succeeded
[EDT Oct 26 02:27:19] debug    : 'pihole-FTL' succeeded testing protocol [DNS] at [127.0.0.1]:53 [TCP/IP] [response time 52.965 ms]
[EDT Oct 26 02:27:19] debug    : 'pihole-FTL' connection succeeded to [127.0.0.1]:53 [TCP/IP]
[EDT Oct 26 02:27:19] debug    : 'openvpn' process is running with pid 32359
[EDT Oct 26 02:27:19] debug    : 'openvpn' zombie check succeeded
[EDT Oct 26 02:27:19] debug    : 'openvpn' succeeded testing protocol [DNS] at [9.9.9.9]:53 [TCP/IP] [response time 49.761 ms]
[EDT Oct 26 02:27:19] debug    : 'openvpn' connection succeeded to [9.9.9.9]:53 [TCP/IP]
[EDT Oct 26 02:27:19] debug    : 'vpn' link data collection succeeded
[EDT Oct 26 02:27:19] debug    : 'vpn' link up
[EDT Oct 26 02:27:19] debug    : 'vpn' upload errors check succeeded
[EDT Oct 26 02:27:19] debug    : 'vpn' download errors check succeeded
[EDT Oct 26 02:27:19] debug    : 'internet' succeeded testing protocol [DNS] at [192.5.5.241]:53 [TCP/IP] [response time 53.899 ms]
[EDT Oct 26 02:27:19] debug    : 'internet' connection succeeded to [192.5.5.241]:53 [TCP/IP]

‌

Comments (8)

Lutz Mader
Hello js290,
from my point of view your state file is not stale. Your way, to do the restart does not fit well to monit.

Based on your configuration.
```
check network vpn with interface tun0
  start program = "/bin/systemctl start openvpn"
  stop program = "/bin/systemctl stop openvpn"
  if failed link then restart
```
This will monitor the interface and do a restart via systemd if something is going wrong. But you use a additional service definition to monitor the application too.
```
check process openvpn with pidfile /run/openvpn/protonvpn.pid
  start program = "/bin/systemctl start openvpn"
  stop program = "/bin/systemctl stop openvpn"
  if failed host 9.9.9.9 port 53 type tcp protocol dns retry 5 then stop
```
As long as everything works well, this service will be monitored by monit. But if the connection to the host (you check the dns service) is not available, this will stopped.

From my point of view,
if you restart “vpn”, the openvpn process dies and the host can not reaced for a short time now. This start the recovery of the “openvpn” service and will stop the “openvpn” service after five cycles. You must enable the monitoring therefore again.
```
check network vpn with interface tun0
  start program "/usr/local/bin/monit start openvpn"
  stop program "/usr/local/bin/monit stop openvpn"
  if failed link then restart
```
To make monit aware of the restart, you should use monit to do the stop and start of the “openvpn” service.

A suggestion only,
Lutz
- 2020-10-26T16:31:15+00:00
js290 reporter
Oh, nice! I will modify my config and report back. Thanks for the tip!
- 2020-10-26T18:05:31+00:00
Tildeslash repo owner
- changed status to resolved
Lutz described the correct solution (the problem is in action "stop" which disables the monitoring and requires "start" or "monitor" to enable it again)
- 2020-10-27T17:22:24+00:00
js290 reporter
Thanks, the updated config performs as you guys described. Is it possible to have the subsequent monit check delayed since openvpn does not start immediately? Notice in the output below monit tries to restart the vpn check a few times because the tun0 interface had not finished initializing from the first attempt.

[EDT Oct 30 11:53:30] warning [EDT Oct 30 11:53:35] warning [EDT Oct 30 11:53:40] warning [EDT Oct 30 11:53:45] warning [EDT Oct 30 11:53:50] error [EDT Oct 30 11:53:50] info [EDT Oct 30 11:53:51] error [EDT Oct 30 11:53:51] info [EDT Oct 30 11:53:51] info [EDT Oct 30 11:53:51] info [EDT Oct 30 11:53:51] info [EDT Oct 30 11:53:51] info [EDT Oct 30 11:53:51] info [EDT Oct 30 11:53:51] info [EDT Oct 30 11:53:51] info [EDT Oct 30 11:53:51] info [EDT Oct 30 11:53:51] info [EDT Oct 30 11:53:51] error [EDT Oct 30 11:53:51] info [EDT Oct 30 11:53:51] info [EDT Oct 30 11:53:51] info [EDT Oct 30 11:53:51] info [EDT Oct 30 11:53:51] info [EDT Oct 30 11:53:51] info [EDT Oct 30 11:53:51] info [EDT Oct 30 11:53:51] info [EDT Oct 30 11:53:51] info : 'openvpn' failed protocol test [DNS] at [9.9.9.9]:53 [TCP/IP] -- Connection timed out (attempt 1/5) : 'openvpn' failed protocol test [DNS] at [9.9.9.9]:53 [TCP/IP] -- Connection timed out (attempt 2/5) : 'openvpn' failed protocol test [DNS] at [9.9.9.9]:53 [TCP/IP] -- Connection timed out (attempt 3/5) : 'openvpn' failed protocol test [DNS] at [9.9.9.9]:53 [TCP/IP] -- Connection timed out (attempt 4/5) : 'openvpn' failed protocol test [DNS] at [9.9.9.9]:53 [TCP/IP] -- Connection timed out : 'openvpn' stop: '/bin/systemctl stop openvpn' : 'vpn' link data collection failed -- Cannot read /sys/class/net/tun0/operstate -- No such file or directory : 'vpn' trying to restart : 'vpn' stop: '/usr/bin/monit stop openvpn' : 'openvpn' stop on user request : Monit daemon with PID 505 awakened : 'vpn' start: '/usr/bin/monit start openvpn' : 'openvpn' start on user request : Monit daemon with PID 505 awakened : Awakened by User defined signal 1 : 'openvpn' start: '/bin/systemctl start openvpn' : 'openvpn' start action done : 'vpn' link data collection failed -- Cannot read /sys/class/net/tun0/operstate -- No such file or directory : 'vpn' trying to restart : 'vpn' stop: '/usr/bin/monit stop openvpn' : 'openvpn' stop on user request : Monit daemon with PID 505 awakened : 'vpn' start: '/usr/bin/monit start openvpn' : 'openvpn' start on user request : Monit daemon with PID 505 awakened : Awakened by User defined signal 1 : 'openvpn' start action done

[EDT Oct 30 11:53:52] error : 'vpn' link data collection failed -- Cannot read /sys/class/net/tun0/operstate -- No such file or directory
[EDT Oct 30 11:53:52] info : 'vpn' trying to restart
[EDT Oct 30 11:53:52] info : 'vpn' stop: '/usr/bin/monit stop openvpn'
[EDT Oct 30 11:53:52] info : 'openvpn' stop on user request
[EDT Oct 30 11:53:52] info : Monit daemon with PID 505 awakened
[EDT Oct 30 11:53:52] info : 'vpn' start: '/usr/bin/monit start openvpn'
[EDT Oct 30 11:53:53] info : 'openvpn' start on user request
[EDT Oct 30 11:53:53] info : Monit daemon with PID 505 awakened
[EDT Oct 30 11:53:53] info : Awakened by User defined signal 1
[EDT Oct 30 11:53:53] info : 'openvpn' start action done
[EDT Oct 30 11:53:53] info : 'vpn' link data collection succeeded
- 2020-10-30T18:10:10+00:00
Lutz Mader
Hello js290,
this does not look well, you are right.
Unfortunately there is no way to set a service to "OK" to prevent useless internal monitoring, but you can increase the monitoring cycles or/and the number of cycles.
```
check process openvpn with pidfile /run/openvpn/protonvpn.pid
  every 5 cycles
  start program = "/bin/systemctl start openvpn"
  stop program = "/bin/systemctl stop openvpn"
  if failed host 9.9.9.9 port 53 type tcp protocol dns retry 5 then stop
```
Or you increase the number of retries (but 5 is useful), but a slower monitoring cycles seems to me more useful.

From my point of view the used monitor interval is to short.
```
set daemon  30
```
The default 30 seconds interval is useful and fit (I prefer 60 seconds), but you set the interval to 5 seconds, this is very small.

Any reason to use such a fast/small monitor cycle?

With regards,
Lutz
- 2020-10-31T09:58:48+00:00

js290 reporter

@Lutz Mader , my daemon is actually set for 120 seconds with start delay of 240. The 5 second retry is the default timeout setting, from the man page:

The default connection timeout is 5 seconds. You can rise this limit using the TIMEOUT option.

I think this is what I want:

check network vpn with interface tun0
  start program = "/usr/bin/monit start openvpn" with timeout 30 seconds
  stop program = "/usr/bin/monit stop openvpn"
  if failed link then restart

Update:

So I tested the “with timeout 30 seconds” by disconnecting the physical network connection on this computer. The openvpn monit check goes haywire. The entire openvpn check ran incessantly; even the process check no longer honored the 5 second timeout. And, the “check network vpn…” with the new timeout value did not seem to help at all. The monit webUI says the start/stop has 30 s timeout, but does not honor it.

Here’s what I ended up doing, which seems to behave as I’d expect. I set the manual timeout to be less than 30 to avoid the script clashing with monit’s timeout.

check network vpn with interface tun0
  start program = "/etc/monit/monit-start.sh openvpn 20"
  stop program = "/usr/bin/monit stop openvpn"
  if failed link then restart

Where monit-start.sh is a simple shell script:

#!/bin/bash
/usr/bin/monit start $1
sleep $2

Now, the vpn interface restart behaves better, but the process check does not honor the 5s timeout after the initial fail, which may be a bug.

[EST Nov  1 11:21:38] warning  : 'openvpn' failed protocol test [DNS] at [9.9.9.9]:53 [TCP/IP] -- Connection timed ou
t (attempt 1/5)
[EST Nov  1 11:21:43] warning  : 'openvpn' failed protocol test [DNS] at [9.9.9.9]:53 [TCP/IP] -- Connection timed ou
t (attempt 2/5)
[EST Nov  1 11:21:48] warning  : 'openvpn' failed protocol test [DNS] at [9.9.9.9]:53 [TCP/IP] -- Connection timed ou
t (attempt 3/5)
[EST Nov  1 11:21:53] warning  : 'openvpn' failed protocol test [DNS] at [9.9.9.9]:53 [TCP/IP] -- Connection timed ou
t (attempt 4/5)
[EST Nov  1 11:21:58] error    : 'openvpn' failed protocol test [DNS] at [9.9.9.9]:53 [TCP/IP] -- Connection timed ou
t
[EST Nov  1 11:21:58] info     : 'openvpn' stop: '/bin/systemctl stop openvpn'
[EST Nov  1 11:21:58] error    : 'vpn' link data collection failed -- Cannot read /sys/class/net/tun0/operstate -- No
 such file or directory
[EST Nov  1 11:21:58] info     : 'vpn' trying to restart
[EST Nov  1 11:21:58] info     : 'vpn' stop: '/usr/bin/monit stop openvpn'
[EST Nov  1 11:21:58] info     : 'openvpn' stop on user request
[EST Nov  1 11:21:58] info     : Monit daemon with PID 10030 awakened
[EST Nov  1 11:21:58] info     : 'vpn' start: '/etc/monit/monit-start.sh openvpn 20'
[EST Nov  1 11:21:58] info     : 'openvpn' start on user request
[EST Nov  1 11:21:58] info     : Monit daemon with PID 10030 awakened
[EST Nov  1 11:22:18] warning  : 'internet' failed protocol test [DNS] at [192.5.5.241]:53 [TCP/IP] -- Network is unr
eachable (attempt 1/5)
[EST Nov  1 11:22:18] warning  : 'internet' failed protocol test [DNS] at [192.5.5.241]:53 [TCP/IP] -- Network is unr
eachable (attempt 2/5)
[EST Nov  1 11:22:18] warning  : 'internet' failed protocol test [DNS] at [192.5.5.241]:53 [TCP/IP] -- Network is unr
eachable (attempt 3/5)
[EST Nov  1 11:22:18] warning  : 'internet' failed protocol test [DNS] at [192.5.5.241]:53 [TCP/IP] -- Network is unr
eachable (attempt 4/5)
[EST Nov  1 11:22:18] error    : 'internet' failed protocol test [DNS] at [192.5.5.241]:53 [TCP/IP] -- Network is unr
eachable
[EST Nov  1 11:22:18] info     : Awakened by User defined signal 1
[EST Nov  1 11:22:18] info     : 'openvpn' start: '/bin/systemctl start openvpn'
[EST Nov  1 11:22:18] info     : 'openvpn' start action done
[EST Nov  1 11:22:18] error    : 'vpn' link data collection failed -- Cannot read /sys/class/net/tun0/operstate -- No
 such file or directory
[EST Nov  1 11:22:18] info     : 'vpn' trying to restart
[EST Nov  1 11:22:18] info     : 'vpn' stop: '/usr/bin/monit stop openvpn'
[EST Nov  1 11:22:18] info     : 'openvpn' stop on user request
[EST Nov  1 11:22:18] info     : Monit daemon with PID 10030 awakened
[EST Nov  1 11:22:19] info     : 'vpn' start: '/etc/monit/monit-start.sh openvpn 20'
[EST Nov  1 11:22:19] info     : 'openvpn' start on user request
[EST Nov  1 11:22:19] info     : Monit daemon with PID 10030 awakened
[EST Nov  1 11:22:39] warning  : 'internet' failed protocol test [DNS] at [192.5.5.241]:53 [TCP/IP] -- Network is unr
eachable (attempt 1/5)
[EST Nov  1 11:22:39] warning  : 'internet' failed protocol test [DNS] at [192.5.5.241]:53 [TCP/IP] -- Network is unr
eachable (attempt 2/5)
[EST Nov  1 11:22:39] warning  : 'internet' failed protocol test [DNS] at [192.5.5.241]:53 [TCP/IP] -- Network is unr
eachable (attempt 3/5)
[EST Nov  1 11:22:39] warning  : 'internet' failed protocol test [DNS] at [192.5.5.241]:53 [TCP/IP] -- Network is unr
eachable (attempt 4/5)
[EST Nov  1 11:22:39] error    : 'internet' failed protocol test [DNS] at [192.5.5.241]:53 [TCP/IP] -- Network is unr
eachable
[EST Nov  1 11:22:39] info     : Awakened by User defined signal 1
[EST Nov  1 11:22:39] info     : 'openvpn' start action done
[EST Nov  1 11:22:39] error    : 'vpn' link data collection failed -- Cannot read /sys/class/net/tun0/operstate -- No such file or directory
[EST Nov  1 11:22:39] info     : 'vpn' trying to restart
[EST Nov  1 11:22:39] info     : 'vpn' stop: '/usr/bin/monit stop openvpn'
[EST Nov  1 11:22:39] info     : 'openvpn' stop on user request
[EST Nov  1 11:22:39] info     : Monit daemon with PID 10030 awakened
[EST Nov  1 11:22:39] info     : 'vpn' start: '/etc/monit/monit-start.sh openvpn 20'
[EST Nov  1 11:22:39] info     : 'openvpn' start on user request
[EST Nov  1 11:22:39] info     : Monit daemon with PID 10030 awakened
[EST Nov  1 11:22:59] warning  : 'internet' failed protocol test [DNS] at [192.5.5.241]:53 [TCP/IP] -- Network is unreachable (attempt 1/5)
[EST Nov  1 11:22:59] warning  : 'internet' failed protocol test [DNS] at [192.5.5.241]:53 [TCP/IP] -- Network is unreachable (attempt 2/5)
[EST Nov  1 11:22:59] warning  : 'internet' failed protocol test [DNS] at [192.5.5.241]:53 [TCP/IP] -- Network is unreachable (attempt 3/5)
[EST Nov  1 11:22:59] warning  : 'internet' failed protocol test [DNS] at [192.5.5.241]:53 [TCP/IP] -- Network is unreachable (attempt 4/5)
[EST Nov  1 11:22:59] error    : 'internet' failed protocol test [DNS] at [192.5.5.241]:53 [TCP/IP] -- Network is unreachable
[EST Nov  1 11:22:59] info     : Awakened by User defined signal 1
[EST Nov  1 11:22:59] info     : 'openvpn' start action done
[EST Nov  1 11:22:59] warning  : 'openvpn' failed protocol test [DNS] at [9.9.9.9]:53 [TCP/IP] -- Network is unreachable (attempt 1/5)
[EST Nov  1 11:22:59] warning  : 'openvpn' failed protocol test [DNS] at [9.9.9.9]:53 [TCP/IP] -- Network is unreachable (attempt 2/5)
[EST Nov  1 11:22:59] warning  : 'openvpn' failed protocol test [DNS] at [9.9.9.9]:53 [TCP/IP] -- Network is unreachable (attempt 3/5)
[EST Nov  1 11:22:59] warning  : 'openvpn' failed protocol test [DNS] at [9.9.9.9]:53 [TCP/IP] -- Network is unreachable (attempt 4/5)
[EST Nov  1 11:22:59] error    : 'openvpn' failed protocol test [DNS] at [9.9.9.9]:53 [TCP/IP] -- Network is unreachable
[EST Nov  1 11:22:59] info     : 'openvpn' stop: '/bin/systemctl stop openvpn'
[EST Nov  1 11:22:59] error    : 'vpn' link data collection failed -- Cannot read /sys/class/net/tun0/operstate -- No such file or directory
[EST Nov  1 11:22:59] info     : 'vpn' trying to restart
[EST Nov  1 11:22:59] info     : 'vpn' stop: '/usr/bin/monit stop openvpn'
[EST Nov  1 11:22:59] info     : 'openvpn' stop on user request
[EST Nov  1 11:22:59] info     : Monit daemon with PID 10030 awakened
[EST Nov  1 11:22:59] info     : 'vpn' start: '/etc/monit/monit-start.sh openvpn 20'
[EST Nov  1 11:22:59] info     : 'openvpn' start on user request
[EST Nov  1 11:22:59] info     : Monit daemon with PID 10030 awakened
[EST Nov  1 11:23:19] info     : 'internet' connection succeeded to [192.5.5.241]:53 [TCP/IP]
[EST Nov  1 11:23:19] info     : Awakened by User defined signal 1
[EST Nov  1 11:23:19] info     : 'openvpn' start: '/bin/systemctl start openvpn'
[EST Nov  1 11:23:19] info     : 'openvpn' start action done
[EST Nov  1 11:23:19] error    : 'vpn' link data collection failed -- Cannot read /sys/class/net/tun0/operstate -- No such file or directory
[EST Nov  1 11:23:19] info     : 'vpn' trying to restart
[EST Nov  1 11:23:19] info     : 'vpn' stop: '/usr/bin/monit stop openvpn'
[EST Nov  1 11:23:19] info     : 'openvpn' stop on user request
[EST Nov  1 11:23:19] info     : Monit daemon with PID 10030 awakened
[EST Nov  1 11:23:20] info     : 'vpn' start: '/etc/monit/monit-start.sh openvpn 20'
[EST Nov  1 11:23:20] info     : 'openvpn' start on user request
[EST Nov  1 11:23:20] info     : Monit daemon with PID 10030 awakened
[EST Nov  1 11:23:40] info     : Awakened by User defined signal 1
[EST Nov  1 11:23:40] info     : 'openvpn' start action done
[EST Nov  1 11:23:40] info     : 'vpn' link data collection succeeded

‌

2020-11-01T15:06:42+00:00

Lutz Mader
Hello js290,
nice trick, I use “sleep” to slow down start scripts too, sometimes.

I will check the timeout behavior, but I think “with timeout 30 seconds“ works well in the past.

Nice to see you are able to handle your vpn startup with Monit.
With regards,
Lutz
- 2020-11-01T20:52:08+00:00

Lutz Mader

Hello js290,
a question of understandig, were the logs came from.

[EST Nov  1 10:11:37] warning  : 'internet' failed protocol test [DNS] at [192.5.5.241]:53 [TCP/IP] -- Network is unreachable (attempt 1/5)
[EST Nov  1 10:11:37] warning  : 'internet' failed protocol test [DNS] at [192.5.5.241]:53 [TCP/IP] -- Network is unreachable (attempt 2/5)
[EST Nov  1 10:11:37] warning  : 'internet' failed protocol test [DNS] at [192.5.5.241]:53 [TCP/IP] -- Network is unreachable (attempt 3/5)
[EST Nov  1 10:11:37] warning  : 'internet' failed protocol test [DNS] at [192.5.5.241]:53 [TCP/IP] -- Network is unreachable (attempt 4/5)
[EST Nov  1 10:11:37] error    : 'internet' failed protocol test [DNS] at [192.5.5.241]:53 [TCP/IP] -- Network is unreachable
[EST Nov  1 10:11:37] info     : Awakened by User defined signal 1
[EST Nov  1 10:11:37] info     : 'openvpn' start: '/bin/systemctl start openvpn'
[EST Nov  1 10:11:37] info     : 'openvpn' start action done
[EST Nov  1 10:11:37] error    : 'vpn' link data collection failed -- Cannot read /sys/class/net/tun0/operstate -- No such file or directory
[EST Nov  1 10:11:37] info     : 'vpn' trying to restart
[EST Nov  1 10:11:37] info     : 'vpn' stop: '/usr/bin/monit stop openvpn'
[EST Nov  1 10:11:37] info     : 'openvpn' stop on user request
[EST Nov  1 10:11:37] info     : Monit daemon with PID 29453 awakened
[EST Nov  1 10:11:37] info     : 'vpn' start: '/usr/bin/monit start openvpn'
[EST Nov  1 10:11:37] info     : 'openvpn' start on user request
[EST Nov  1 10:11:37] info     : Monit daemon with PID 29453 awakened

All this messages are with the same timestamp written to the log. If I check my logs I find gaps of minutes between the monitor messages because I use a cycle of 60 seconds.

See ticket #945 also.

With regards,
Lutz

2020-11-02T07:57:42+00:00

Assignee: –

Type: bug

Priority: major

Status: resolved

Component: Monit

Version: 5.26.0

Votes: 0

Watchers: 1