some nasty behaviour of ISPConfig 3.0.2.2.

Hi Till,
Today i dicovered some nasty behaviour of ISPConfig 3.0.2.2.
I try to tell you what i found out:

In ISPConfig3 on the master server, i added the new (additional) IP-addess 12.34.56.222 for an existing slave server.
Before i did that the slave server had the following content within /etc/network/interfaces:

This is a problem, because of this automatic modification the slave server can not connect to the master anymore, because only root@12.34.56.111 is valid to connect to the master server, NOT root@12.34.56.222
So ISPConfig3 should not move 12.34.56.111 to eth0:0. but the new IP 12.34.56.222 instead!

Today I locked myself out by doing something like you did.
I can not access my server anymore, and as it's a test server in Alphen a/d Rijn (grafix) I need to go there tomorrow and rewrite the file interfaces (add the correct info).

I'm using eth6 an eth7 in it, and ISPconfig changed it to eth0 and 0:0
(for some reason eth0 till eth5 do not work on my system).

@edge: I'am sorry that you have these problems. Thats the reason why the network configuration support is disabled by default. It can only be used for standard setups that use eth0. Other setups or network card names are not supported.

Hello Hans, regarding your networking issue: The problem is most likely related to the /etc/hosts configuration. It is required for mysql that you define the hostname and Ip addresses of all servers that are part of the mulriserver setups in all hosts files of these servers. If thats not the case, the issue you reported may occur as mysql does a forward and a reverse lookup and tries to match these two lookups.

Changing the order of IP addresses in the network configuration file is no solution as this causes other systems to fail which require the the main address is the last IP and not the first IP. The only working solution seems to be to use the /etc/hosts file as it is described in the multiserver setup tutorial or to ensure that the hostnames and their reverse records match the server IP addresses.

@Till,
Thanks for this useful information.
I do have all the IP-addresses, full qualified domain names and host names in the /etc/hosts file of every ISPConfig server.
In case i add additional (extra IP-addresses) for example a website with dedicated IP and SSL on a slave server, do i also need to add that extra IP-address to every single /etc/hosts file as well?

@Till,
Thanks for this useful information.
I do have all the IP-addresses, full qualified domain names and host names in the /etc/hosts file of every ISPConfig server.
In case i add additional (extra IP-addresses) for example a website with dedicated IP and SSL on a slave server, do i also need to add that extra IP-address to every single /etc/hosts file as well?

Click to expand...

No. Only the server hostname has to be added. I've changed it in ispconfig now so that the first IP stays as eth0. But I'am not sure if this breaks other setups as some other devs had reported thyt the main IP has to be always the last one on their servers or mysql will break in the way as you decribed.