Originally Posted by wxman
This first problem I found was when you add a new site to the primary server using ISPConfig, it mirrors the database to the second server so now ISPConfig has the entry there as well. The problem is the site doesn't actually get made on the second server, just the entry in the DB so it looks to ISPConfig that it's there.
Yes, that happens because the /home/admispconfig/ispconfig/.run file is missing - it gets created whenever you change anything in ISPConfig, so that the backend knows that it has to write some configuration files. If you mirror that file over to the second server as well, everything should be fine.