|
I am quite sure that we had this Problem on our test-cluster.
And I am quite sure that it has not been a real ldirectord-Problem.
Unfornatly I can't remember how it was solved (if it has been solved).
Can you please send some kind of Information about the webserver-logs ?
Oktay
On Sun, 14 Oct 2001, Horms wrote:
> On Sun, Oct 14, 2001 at 12:06:45PM -0500, Kelly Corbin wrote:
> > In my LVS cluster I think I may have found a bug in ldirectord.
> > It seems that if a web server opens a TCP/IP connection, but does not
> > respond on that connection, ldirectord hangs waiting for a response and
> > never continues checking the other servers. I had checking set to
> > 'negotiate' to detect that exact problem, but it ldirectord just sits
> > there. A stack trace on ldirectord just says:
> >
> > read 3)
> >
> > and sits there. I'm not sure if it's just for http or https connections
> > or both. I'll have to investigate more, but I think it's just https
> > connections.
>
> The read should eventually time out and ldirectord should
> be able to procede. Please let me know if this is not the case.
>
> --
> Horms
>
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to http://www.in-addr.de/mailman/listinfo/lvs-users
>
|
