[ris-int] riswhois: did nagios report outdated info?
Rene Wilhelm wilhelm at ripe.net
Tue Sep 21 18:40:50 CEST 2004
Hi Ops, This one might be for Gerard (as he did the nagios config for this): I noticed that riswhoisd (on halfweg) is no longer refreshing it's data: whois -h riswhois sources % This is RIPE NCC's Routing Information Service % whois gateway to collected BGP Routing Tables % IPv4 or IPv6 address to origin prefix match % % For more information visit http://www.ripe.net/ris/riswhois.html rrc00 20040915 1600Z rrc01 20040915 1600Z rrc03 20040915 1600Z rrc04 20040915 1600Z rrc05 20040915 1600Z rrc06 20040915 1600Z rrc07 20040915 1600Z rrc10 20040915 1600Z rrc11 20040915 1600Z rrc12 20040915 1600Z It's 6 days ago since riswhoisd last parsed the BGP dump data files. When this happened a few months ago, Gerard implemented rules in nagios that should check for outdated timestamps. Question: did nagios give you such a report in the last days ???? If not, please consider this a request to fix it. I will not restart riswhoisd until tomorrow this time, to give you a chance to test the nagios setup for the up-to-date check. ris-int: it's not clear why riswhoisd can't refresh; it used to work fine; probably it somehow cannot fork a new process that refreshes data while the main daemon continues listening. more debug code will have to be added to riswhois to be able to track this in future. For now the only remedy is a cold restart of the daemon. -- Rene
[ Ris-int Archives ]