Re: Director Failover

I change the real server to another PC and it seems to
work. But still don't know why ??

 --- Sébastien Bonnet <[email protected]>
wrote: > > I have another problem here. I got the
following
> message in the log:
> > nanny[1228]: READ to 192.168.123.198:23 timed out
> 
> I guess that because you don't have a send string,
> nanny just connects
> to telnetd, which doesn't reply anything. If you
> really want to setup a
> telnet cluster, consider using approriate
> send/expect string or an
> external test program.
> 
> > I can telnet/ping 192.168.123.198 (the realserver)
> from the
> > director. What could be the problem ?
> 
> Exposed earlier. Just to make sure I've understood :
> it does work, but
> you get these nasty lines in the logs, right ?
> 
> > rsh_command = rsh
> >          load_monitor = uptime
> 
> Too bad ! This is the least efficient way to collect
> remote loads.
> Consider using (a modified) ruptime : start rwhod on
> all realservers,
> name them by their real, not FQDN, hostname in
> lvs.cf, and use the
> following script as load_monitor.
> 
> [sbt@ssca4010 sbt]$ cat
> /etc/sysconfig/ha/ruptime-piranha
> #! /bin/sh
> 
> ruptime | grep -E "^$1[[:space:]]+" | sed -e 's/
> load / load average:
> /g'
> 
> -- 
> Sébastien Bonnet
>   Centre de contacts - Experian France
> 
> 
> 
> _______________________________________________
> Piranha-list mailing list
> [email protected]
>
https://listman.redhat.com/mailman/listinfo/piranha-list 

__________________________________________________
Do You Yahoo!?
Promote your business from just $5 a month!
http://sg.biztools.yahoo.com