at-ws.ten-34.net instabilities

["Michael H. Behringer" <]

For your information: Over the last days we have experienced several times
that mrouted dies (core dumped) on the at-ws.ten-34.net. Also, at times
tunnels appear to be down for some time, without obvious reason. The
mrouted version is currently 3.9-beta2. The whole set-up is exactly the
same as on the other TEN-34 mrouteds, which have no problem (knock on
wood). We will try upgrading to the new beta3 after the IETF. Any other
ideas: Please let us know ;-)

In the meantime, to get round this problem, we have installed a script that
automatically restarts mrouted when it dies. On the AT ws, I have just
increased the checking frequency from 15 to 5 min, since our "restart-log"
shows two resets yesterday:

# more mrout.restart-log
Thu Mar 26 16:30:00 MET 1998
Thu Mar 26 21:00:01 MET 1998

Meaning: NRNs "behind" at-ws should not have more than 5min outage max at
the moment. 

at-ws.ten-34.net 

193.203.254.14 (at-ws.ten-34.net) [version 3.255,prune,genid,mtrace]:
  193.203.254.14 -> 0.0.0.0 (local) [1/1/querier/leaf]
  193.203.254.14 -> 193.203.254.10 (ch-ws.ten-34.net) [1/48/tunnel/leaf]
  193.203.254.14 -> 192.153.181.1 (mbone.aco.net) [1/48/tunnel/leaf]
  193.203.254.14 -> 193.2.1.77 (rzenik.arnes.si) [1/48/tunnel/leaf]
  193.203.254.14 -> 193.225.12.9 (vhx.iif.hu) [1/48/tunnel/leaf]

Any comments or help welcome. 
Michael


PS: Yesterday the CH-WS went down hard (no telnet possible anymore) twice,
too, which is probably not related to mrouted, but will have had effects on
the mbone as well.