[Xorp-users] XORP problems at boot

[J.T. Conklin]

"Soucy, Ray" <rays at maine.edu> writes:

> 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?

What system are you running XORP on?

>From the log messages, it says that the event loop hasn't been run in
16 hours. I tend to doubt that's the case. Is there something in your
boot process that resets the clock after XORP has been started?

    --jtc

-- 
J.T. Conklin