[Xorp-users] "gmake check" error messages "timer expired..." etc.

[Atanu Ghosh]

Hi,

The XORP IPC scheme by default runs over TCP. The first set of errors
are due to TCP connections terminating. I think we send our own
keepalive message on the these TCP connections. We use a timer to send
and monitor the keepalive messages.

The later errors are reporting that some timers have fired 406 seconds
late. If the timer code misbehaved this maybe the reason the TCP
connections were dropped.

Is the problem repeatable, which operating system are you using?

We have seen an occasional problem that on a heavily loaded FreeBSD
machine an occasional call to gettimeofday will return a value 695
seconds behind real time.
<http://archives.postgresql.org/pgsql-hackers/2003-11/msg01526.php>

     Atanu.

>>>>> "Yonghong" == Yonghong Ren <ren@sandmail.sandburst.com> writes:

    Yonghong> Running "gmake check" got the following errors. What do
    Yonghong> they mean?  Thanks!  

    Yonghong> [ 2004/12/31 10:16:35 ERROR xorp_bgp:6010 XRL +628
    Yonghong> xrl_pf_stcp.cc die ]
    Yonghong> XrlPFSTCPSender died: end of file ive timeout /12/31
    Yonghong> 10:16:35 ERROR xorp_rib:6008 XRL +329 xrl_pf_stcp.cc die ]
    Yonghong> STCPRequestHandler died: life timer expired [ 2004/12/31
    Yonghong> 10:16:35 ERROR xorp_rib:6008 XRL +329 xrl_pf_stcp.cc die ]
    Yonghong> STCPRequestHandler died: life timer expired =20 And many
    Yonghong> lines of ... 

    Yonghong> Timer Expiry *much* later than
    Yonghong> scheduled: behind by 407.523750 seconds

    Yonghong> Timer Expiry *much* later than
    Yonghong> scheduled: behind by 406.523750 seconds