- changed status to resolved
Monit startup delay on boot
Add option to allow a one-time start delay when the system uptime is less than a specified number of seconds or minutes.
This is helpful to allow the "with start delay" to be disabled for config reloads but causes false alerts when a system is booted.
Putting this delay in the systemd/init/upstart/etc scripts is difficult to impossible and not practicle for every sysadmin to do when it's a universal need.
Comments (3)
-
repo owner -
repo owner Merged in feature/startdelay (pull request #70)
Fixed Issue
#829: The start delay is now in effect just on first monit start after machine reboot.Approved-by: Jan-Henrik Haukeland hauk@tildeslash.com
→ <<cset 2aa5ca19a563>>
-
Hello Jan-Henrik,
nice to know (but a bad idea, from my point of view, sorry).Monit daemon with pid [67] stopped 'Mac' Monit 5.26.0 stopped Starting Monit 5.26.0 daemon with http interface at [macbookpro.local]:2812 Monit will delay for 240s on first start after reboot ...
It seems to me ist does not work well, after a reboot the startup was delayed and some times later I restart monit and the monit start was delayed again.
But several times later, the restart was not delayed.
Monit daemon with pid [628] stopped 'Mac' Monit 5.26.0 stopped Starting Monit 5.26.0 daemon with http interface at [macbookpro.local]:2812 'Mac' Monit 5.26.0 started
How monit detect a start after a reboot?
From my point of view the "kern.boottime" (MacOS) is used, but I can not find the used reboot test.With regards,
Lutzp.s.
See the post "Monit start delay only on boot" from 01 Jun 2019.Back to your suggestion,
an additional monit start option to give the deplay is more fexible than an additional "monitrc" statement to do this, I think.Sometimes it is useful to delay the monit start all the time, but you are right, a longer/additional startup delay is useful.
- Log in to comment
Fixed Issue
#829: The start delay is now in effect just on first monit start after machine reboot.→ <<cset 1143ccd3d37d>>