monit startup and system time

[Gerrit Kühn]

Hi all,

I am running monit on Gentoo systems, installed via portage and using the
startup scripts provided by that.
I just noticed one strange behaviour: starting up at boot time, monit
gets the wrong time, probably due to a (at that point) wrong time zone
setting (at least that would explain the offset it shows). It then sits
there for ages because I configured it to wait for 60 seconds after startup
before starting to do anything. When the system is running, giving monit a
"restart" makes everything running fine again (time is correct then).
I am not entirely sure where I have to look for the problem. Where does
monit get its time from, and how does it consider time zone settings? Is
it just started too early during the boot process?

This is an excerpt from the logfile:

---
[CET Mar  2 19:20:57] info     : Starting monit daemon with http interface at 
[*:8080]
[CET Mar  2 19:20:57] info     : Monit start delay set -- pause for 60s
[CET Mar  2 17:22:15] info     : Starting monit daemon with http interface at 
[*:8080]
[CET Mar  2 17:22:15] info     : Monit start delay set -- pause for 60s
[CET Mar  2 17:23:15] info     : Starting monit HTTP server at [*:8080]
[CET Mar  2 17:23:15] info     : monit HTTP server started
---


The time monit reports when starting is 2 hours too late. However, when the 
system is fully up and I log in, "date" gives me the correct time (17:20 in the 
case above). But monit is waiting for the clock to become 19:21:57, which takes 
two hours. When I issue a "/etc/init.d/monit restart" after booting it comes 
back with the correct time (17:22) as you can see (and everything is fine from 
there on).

This is monit v5.2.3. Any hints how to get this right are of course greatly 
appeciated.


cu
  Gerrit