Loadbalanced ISPconfig - Apache2 users/ groups

[Key4ce]

Hello,

I have been working on this for quite a while.. but.. i'm neaarrllyyy there haha.
I have got a nearly full functioning ISPconfig (fully loadbalanced) running.

But i have hit a little bumb in the road: apache2 plus the users created/ configured by ispconfig.

So.. to keep things simple.. how can i make ISPconfig panel duplicate the username/group on 2 servers? (or use LDAP for this)

Basically on every site creation it's my understanding that it creates a new user/group.. this causes my apache on the second server to fail to start unless i manually replicate the user.

The second little glitch (less seriouse) mySQL: it only creates databases and users from the Primary server.. is there a way to make it use a global address to create it with? (at the moment mysql in failover mode has to be on host1 inorder for ISPconfig to create the user/pass - Other then that the full mysql continues to function fine on every other server - in other words the mysql server has to pick favoures by being loaded on primary server - indead of any random server JUST for ISP panel)

Hopefully i'm making enough sence for some of you to help me out who got a greater understanding of how ISPconfig works.

Once my setup is fully done i will post the full setup howto

[till]

Ispconfig creates the users and groups on both servers with the same name, so mirroring works fine and there is already. Howto published on this topic. Just ensure that you use identical setups for both servers especially that the uid and gid of the last user before you install ispconfig on the servers is the same. This ensures thant all additional users created by ispconfig has the same uid and gid on boh severs.

Ispconfig creates the mysql users on all mirrors auomatically. Just ensure that the mysql interface can only be installed on the master and may not be installed on the slaves. See mirroring totorial.

[Key4ce]

Hey and thanx for your quick reply.

I used the mirroring tutorial as a guideline however this is very incomplete and out of date in some cases like quorum.

with loadbalancing there is a need for equal sites (files) , users (usr db) etc.

the primary server (initially) is configured following the guidelines of the mirror tutorial.

The secondary server has drbd + ocfs2 storage for live sync (instead of glusterFS which is outdated and.. blocklevel tends to be the better party :P)

This however in the tutorial missed the log files area.. apache config is not synced etc.. (so where the site existed on one server - it didn't on the other).

so in addition to that tutorial i figured to sync apache's files (so the vhosts etc is all correct) -
This is where you hit issues with the username and group.

The test site is missing web1 and client0 (user // group)

this is created in Host1 --> Host2 is not updated.

However i have to admit host2 is a little bit modified: it is using the same database as host1 --> therefor has the same functions as host1.

at the moment their both perfect for loadbalancing besides the apache2 user// group and mysql creation of databases (just the creating part inside ispconfig)..

host2 is set as mirror server in isppanel.

Any idea what might of gone wrong here? (ps for me it never synced even before the modifications --> Host1 showed the welcome page while Host2 showed the IT WORKS! page of apache.)


At the moment host1 shows the welcome page and host2 shows 403 forbidden (because of the user/ group issue)

Passwd file:
Host1:
ispconfig:x:5003:5004::/usr/local/ispconfig:/bin/sh
web3:x:5004:5005::/var/www/clients/client0/web3:/bin/false
web4:x:5005:5005::/var/www/clients/client0/web4:/bin/false

Host2:
ispconfig:x:5003:5004::/usr/local/ispconfig:/bin/sh

Another handy info:
I'm using Debian Squeeze x64

-------
In addition to this -->
mySQL is set to Failover using heartbeat (master-master simply is not functioning that well and hits issues with high loads)
So host1 OR host2 is only running mySQL and not BOTH
Their both configured to use linsql --> Which is pointing to the failover SQL ip.

------
In the end mySQL == Failover and the rest (EVERYTHING) is loadbalanced.
I'm not talking about a backup or active/passive server.. for web servers thats just a complete waste of resources.
however Loadbalancing requires identical servers.. this includes the panel (which is now nearly identical with my setup - just got this 1 real issue left and 1 to be improved :P).

[till]

The mirror setup is complte, i know several setups that uses it. Your servers are configured wrong hen, as users, apache config logfiles etc is synced by ispconfig internally, so they may not be synced by another method or he systm must fail.

As far as i can see, you have a mysql auth problem and a wrong setup regarding mysql so hat the secondary mysql instance can not connect to mysql on the master server to sync he data ss you have no secondary mysql intance.

The first step to fix that is to remove all syncing hat you added beside he irectories /var/www and /var/vmail. Then uninstall idpconfig on h lave and follow th mirror tutorisl to instsll it again by using two separat mysql servers as described in the guide.

Ispconfig can not work if both servers use the same database. Asispconfig can not mirror the onfiguration between the servs then as it thinks hat the data is mirrored already.it is a must that each server has its mysql server and ispconfig has to connect to the datbase on localhost.

[till]

Just anoher hint, each step in the mirror guide is required, especially the editing of he hosts files in exact the way described there. If you dont o hat, no changes will get mirrored as mysql auth fails.

Using drbd instead of glustrfs is fine, i wold use hat as well for a new setup. Everything else has to be as in the guide and thas working for debian 6 as well, so its not outdated at all.

[Key4ce]

well the setup is incomplete on behalf of MAINLY the mysql.
you can not keep 2 mysql's up2date using that setup without either a reload or restart command. (if you load/save data OUTSIDE ispconfig that is on either mysql on host1 or mysql on host2)

Secondary --> Quota on debian squeeze with UID disks does not function like that neither, etc:
How it works in debian squeeze : errors=remount-ro,usrjquota=aquota.user,grpjquota=aquota.group,jq fmt=vfsv0

Third --> once i completed the setup using drbd + ocfs2 instead of glusterFS --> the site log (created new site) did not sync.

located in :/var/log/ispconfig/ --> without this host2 apache did not start.

Fourth:
Fail2ban is left relatively unconfigured.. leaving alot of improvements on security (ssh / mysql / apache)

However .. i must say it was a great guide and helped me alot so far.

BUT
I'm not a big fan of mysql master-master .. i have seen many corperations obtaining huge dataloss duo to minor bugs with this setup.

Failover mysql is from our expirience the best "bullet proof" setup.
This means either use a seperated 2 Servers for mysql storage OR simply find a way around the defaults.

Also a single master panel - is not load balanced thats an old fashion cluster with 1 master and slaves (loadbalanced == master master )

So to keep this simple - ispconfig can not be edited in such a way to create users / groups WITHOUT a master AND slave database?

(remember my setup uses master // master database).

If so.. where's the scripts located responsible for creating users/groups?

-----
Hosts file we got it a bit more advanced with 2 different networks for each servers, shared ip's etc
In addition to that we got our internal DNS servers (3x) linked to the hostnames as a fall back.

If you want i can send you the entire txt file with every single step i took. (also got screenshots of some areas like the drbd setup using LCMC)
The file system section is still a bit messy duo to the user perms tho.