Re: Odd Failover Predicament
"Peter J. Milanese" <[email protected]>
| Newsgroups | gmane.linux.redhat.piranha |
|---|---|
| Message-ID | <[email protected]> |
Alrighty... Found the problem, going to note it here incase anyone ever runs into it... I'm running with Apache Vhost configs... nanny hits the real server IP address, which tends to mean that it hits the FIRST vhost it encounters in the config file. It happens that the first vhost on our config is a coldfusion page, which hits a database on another network. Our network boys allowed lvs01 to pass the sql port, but not lvs02. Thus, being the silliness of coldfusion, the hit timed out for nanny before it timed out through the coldfusion dbase connection. 2 measures were taken to fix this: First, open the port for the dbase connectivity Second, create a vhost (and make it the first one) that only the backend of the lvs's can hit. Anyhow, incase someone is as silly as me, there ya go- Have a good weekend- P On Wed, 19 Mar 2003, Peter J. Milanese wrote: > Hello folks- > > I've gotten lvs stable with the exception of one thing... > > The Backup LVS box cannot do an HTTP get AFTER failing over. > > It can prior to the failover, which leads me to believe that > it may be an apache thing.. Running 2.0.44... FTP is not > hit with Nanny either though... > > Confirming this, coldfusion (yes.. cf) is hit fine on failover. > > In short (after failing over): > > Cold Fusion's web server works . > Apache and FTP do not. > > Trust is established between ALL servers (ssh and http). > > Real Server can hit external sites (so routing works) > > > All else seems to failover correctly. New interfaces come up, > nanny starts, nanny gets bad results and it cannot enable the real > servers because of this. It appears NOT to be an lvs config > issue, although I'm not completely convinced since I haven't > actually found any problem. > > Anyone know where I may have mussed up? > > Thanks- > > Peter > > > > _______________________________________________ > Piranha-list mailing list > [email protected] > https://listman.redhat.com/mailman/listinfo/piranha-list >