radium fails on reconnect argus sometimes

Wolfgang Barth wob at swobspace.de
Sat Feb 24 11:11:47 EST 2007


Hi,

I'm using radium (rc.39) to collect data from distributed argus daemons. Here is
my radium.conf:

RADIUM_DAEMON=yes
RADIUM_MONITOR_ID=`hostname`
RADIUM_DEBUG_LEVEL=0
RADIUM_MAR_STATUS_INTERVAL=60
RADIUM_ARGUS_SERVER=elibridge_tsy:561
RADIUM_ARGUS_SERVER=elibridge_rzv:561
RADIUM_ARGUS_SERVER=elibridge_dmz:561
RADIUM_ARGUS_SERVER=eligate1:561
RADIUM_ARGUS_SERVER=eligate2:561
RADIUM_ARGUS_SERVER=eligate3:561
RADIUM_ACCESS_PORT="561"
RADIUM_BIND_IP="127.0.0.1"

argus on eligate1, eligate2 and eligate3 failed yesterday for some reasons.
radium automatically reconnects eligate2 and eligate3, but on eligate1
argus didn't restart. I restarted argus on eligate1 manually today, but
radium did not reconnect. My logfile shows:

2007-02-23 14:40:01 ArgusReadStream eligate1: idle stream: closing
2007-02-23 14:40:03 ArgusReadStream eligate3: idle stream: closing
2007-02-23 14:40:04 ArgusReadStream eligate2: idle stream: closing
2007-02-23 14:40:14 connect to 172.17.130.82:561 failed 'Connection timed out'
2007-02-23 14:40:18 connect to 172.17.130.97:561 failed 'Connection timed out'
2007-02-23 14:40:29 connect to 172.17.130.82:561 failed 'Connection timed out'
2007-02-23 14:40:33 connect to 172.17.130.97:561 failed 'Connection timed out'
2007-02-23 14:40:37 connect to 172.17.130.82:561 failed 'No route to host'

The last one is eligate1, may be in the case of "no route to host" radium
is stopping to reconnect?

wob
-- 
<wob (at) swobspace de> * http://www.swobspace.de



More information about the argus mailing list