Database replication errors on some actions in ISPconfig3
On some actions, ie creating or deleting a mysql table (for a client), and when using mirrored servers that also have mysql active-active replication, replication often breaks as the command is sent to both servers, while mysql replication replicates it to the other server. One of the mirrored servers then gets the same command twice then.
This might be overcome by adding "IF EXISTS" or "WHERE NOT EXISTS" to queries sent by ISPconfig3.