Don't bind it to an IP (so listen shows 0.0.0.0) on either node of the cluster? When the IP address is floated across it will still accept requests on that then - in additional the the real node IP address..... Given that you are talking a public IP address however it depends on your network configuration and ISP setup... 2010/1/8 <avi at myphonebook.co.in> > I want to set up a cluster that is used for web hosting (RHCS cluster). > Recently, > I experimented with a 2 node cluster and was able to run it successfully. > However, > I have started facing some issues with Apache, which I had configured as a > service > using the Cluster configuration tool. To do this Apache needs a floating IP > address. > This address is in addition to the network interface IP address. For > example if my > NIC IP is 192.168.1.1, then I need 192.168.1.2 as a floating IP address, > and this > has to be bound to apache. At least this is what I understood after several > hours > of experimentation. I also figured that if I configured 192.168.1.1 as a > cluster > resource and bound it to apache, the cluster manager failed to start apache > and the > NIC was put "off". ( In effect 192.168.1.1 was removed from the NIC ). > > However, the Apache service ran fine when bound to the ADDITIONAL IP i.e. > 192.168.1.2 > ( the floating IP ). > > The above example was just a lab setup to test the cluster. > > My problem is that I only have a single public IP address, to serve my web > server > and my question is this: > > Is this the end of the road, for installing apache as a service with ONE > public IP > address?? > > I am willing to give further info, if required. > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20100108/acdbd7f9/attachment-0004.html>