Hello, On 02/05/2012 01:57 AM, mike wrote: > Hi all, > > I've got a very simple 2 node setup. It runs a few VIPs and uses > ldirectord to load balance. That part works perfectly. > > On the same 2 node cluster I have apache running and it fails back and > forth fine as long as ports.conf is set to listen on all ip's. I do have > a VIP - 192.168.2.2 that I want Apache to start up on. I have tested > apache manually on both nodes by editing ports.conf and setting it to > 192.168.2.2 and starting apache from the command line - works fine. When
Please share your config if you want authoritative answers ... without any further information it looks like a missing order constraint between apache and its IP. You should find logging output from apache RA in your syslogs .... Regards, Andreas -- Need help with Pacemaker? http://www.hastexo.com/now > I try to get Apache to start with HA it fails. Here is what my current > set up looks like: > ============ > Last updated: Sat Feb 4 20:50:25 2012 > Stack: Heartbeat > Current DC: firethorn (3125c95a-33d1-4923-a5c0-38b228f90ecf) - partition > with quorum > Version: 1.0.9-74392a28b7f31d7ddc86689598bd23114f58978b > 2 Nodes configured, unknown expected votes > 3 Resources configured. > ============ > > Online: [ firethorn vanderbilt ] > > Resource Group: Web_Cluster_IP > ApacheIP (ocf::heartbeat:IPaddr2): Started firethorn > Resource Group: Web_Cluster > WebSite (ocf::heartbeat:apache): Started firethorn > ClusterIP (ocf::heartbeat:IPaddr2): Started firethorn > ClusterIP2 (ocf::heartbeat:IPaddr2): Started firethorn > Resource Group: LVS_Cluster > LdirectorIP (ocf::heartbeat:IPaddr2): Started firethorn > ldirectord (ocf::heartbeat:ldirectord): Started firethorn > > ApacheIP starts up first before apache does so I'm at a loss to > understand why HA has issues starting apache. The logs are not revealing > unfortunately. Initially I had the ApacheIP and apache in the same > resource group so I thought maybe if I break the IP out into its own > group then I'd know it comes up first and apache should follow. It > doesn't sadly. > > So am I missing something obvious here? Why does apache start from the > command line but not in HA unless ports.conf is set to listen on all > interfaces? > > Thanks > -mike > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
