View Single Post
Old 12th May 2010, 11:49
stevegjacobs stevegjacobs is offline
Junior Member
Join Date: Sep 2008
Posts: 28
Thanks: 1
Thanked 1 Time in 1 Post
Default Ispconfig3 High availability cluster: mysql problem

This is my second attempt to set up a high availability cluster with Ispconfig3. What I want is no single point of failure, so I have two separate servers, webserver1 and webserver2, set up with DRBD/Heartbeat.

The first attempt was with Centos, which didn't work out due to problems with mail packages. I have started over with Debian. I have everything working on the Debian install, EXCEPT that when I force a failover, mysql won't start on webserver2.

Here is what I have done:

1. set up webserver1 and webserver2 with drbd/Heartbeat for clustering.
2. Installed all packages and and Ispconfig on each server according to the 'Perfect server tutorial.
3. Moved folders www, vmail, and mysql data folder from webserver1 to the drbd storage area (/mnt/drbd/ on my system)
4. Created appropriate sym links and edited config files on each system to reflect the above changes.
5. Started all services on webserver1, logged into ispconfig, added a website, installed Joomla on the site, added an email address and an extra ip address, and tested all. Everything worked!
6. Forced a failover to webserver 2. Mysql won't start.

The thing is, that when I first tried it on Centos, I did the same thing with everything, including mysql, everything worked except for mail. If I forced a failover, ispconfig, mysql, my websites and ip addresses all moved to webserver2. I gave up on Centos because I couldn't get mail to work on either server.

Would anybody have any suggestions about what to do to get mysql to work?

Reply With Quote
Sponsored Links