[Xorp-users] XORP problems at boot

[Bruce Simpson]

Soucy, Ray wrote:
> Hi,
>
> When I run XORP at boot (as part of init) the log fills up with these messages:
>
> [ 2009/06/03 15:59:18  WARNING xorp_rtrmgr:1552 LIBXORP +94 eventloop.cc run ] 57601 seconds between calls to EventLoop::run
> [ 2009/06/03 15:59:18  WARNING xorp_rtrmgr:1552 LIBXORP +432 timer.cc expire_one ] Timer Expiry *much* later than scheduled: behind by 57599.955934 seconds
> [ 2009/06/03 15:59:18  WARNING xorp_rtrmgr:1552 LIBXORP +432 timer.cc expire_one ] Timer Expiry *much* later than scheduled: behind by 57599.940032 seconds
> [ 2009/06/03 15:59:18  WARNING xorp_rtrmgr:1552 LIBXORP +432 timer.cc expire_one ] Timer Expiry *much* later than scheduled: behind by 57599.883755 seconds
>
> --8<--
>
> These messages go on for 470,716 lines within a few min.
>
> If I kill XORP and restart it, or manually start it after the system
> is booted, I don't see these messages and XORP has no problems.
> Anyone else ever see this?
>   

Is the host you're running XORP on NTP synchronized?
How fast is the host? Which OS/version is it running?
Does the output of the 'uptime' shell command change during system boot 
significantly?

You should only see these messages if there's a timing problem. I 
refactored the code involved some time ago to use POSIX CLOCK_MONOTONIC, 
as there was a classic problem with the EventLoop being blown away as it 
used to depend on wallclock time.

If your system doesn't support CLOCK_MONOTONIC then XORP will fall back 
to the wallclock time as the time base. If it does, then this shouldn't 
ever be an issue -- unless your OS does something to CLOCK_MONOTONIC.