I don't know about the high port issue, but you can set the health check to expect a certain value or string - that should take care of the proxy issue.
Take a look at this page, it explains more about setting the health check status code. http://www.foundrynet.com/solutions/appNotes/HealthChecks.html ----- Original Message ----- From: <[EMAIL PROTECTED]> To: "Bill McCaffrey" <[EMAIL PROTECTED]> Cc: <[email protected]> Sent: Thursday, December 05, 2002 3:10 AM Subject: serveriron http on ports other than 80 > Greetings, > > I'm running several instances of Apache per server. Many of them on > ports above 1024. (so that normal users can start/stop them.) Two > issues I've run into: > > I've tried configuring TCP health checks on the high ports (10000, > 10010, etc.) via the TCP/UDP port config and it seems to fail the health > checks on the real server every time. (and thus serves nothing.) If I > connect directly to the servers on the high ports I get the pages I expect. > > The second issue is that I cannot bind from a low point to a high > point. I was kind of hoping to be able to bind port 80 on the virtual > server to port 10000 (or whatever) on the real server. This is > necessary because right now I use apache on port 80 to proxy up to port > 10000 (or whatever) on the individual webservers. So... if the health > checks just check port 80, the proxy may be up just fine, but the high > port server may not be up. Thus the client may see a "proxy failure" > page if the port 80 server is alive and the port 10000 server is dead. > > Sorry about all the questions. I just got this serveriron recently > and despite reading through most of the docs on the website, there is > still much I am having trouble figuring out. ;-) > > Cheers, > > ~Ethan B. > > -------------------------- > Ethan Burnside - Founder > Kattare Internet Services > http://www.kattare.com > -------------------------- >
