DARP TCP slave issue
Jeff Weisberg
jaw+arguslist at tcp4me.com
Fri Jul 29 09:51:00 EDT 2005
On 29 Jul, 2005, at 3:15, Jeremy Kister wrote:
> I've got DARP-3.4_RC20050419 running on my master and slave, both
> running Argus 3.4.
>
> on the master, all of the objects have slave status "unknown" -- I'm
> trying to fix this.
>
> interesting data:
>
> on the slave, I can connect to the master on port 2055
> on the slave, I cannot connect to localhost on port 2055
> on the master, I can connect to localhost on port 2055
> on the master, I cannot connect to the slave on port 2055
this is normal. only the master listens for connections.
> relevant config entries on the master:
> darp_mode: failover
> [...]
>
> any ideas why all the slave statuses on the master are all unknown?
>
this is normal.
in failover mode, the slaves will not monitor anything until the master
dies.
since they aren't doing any monitoring, they have no statuses to report.
More information about the Arguslist
mailing list