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: Code: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 12.34.56.111 netmask 255.255.255.0 network 12.34.56.0 broadcast 12.34.56.255 gateway 12.34.56.129 After adding the additional IP-address on the master server, the content of /etc/network/interfaces on the slave changed into: Code: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 12.34.56.222 netmask 255.255.255.0 network 12.34.56.0 broadcast 12.34.56.255 gateway 12.34.56.129 auto eth0:0 iface eth0:0 inet static address 12.34.56.111 netmask 255.255.255.0 network 12.34.56.0 broadcast 12.34.56.255 gateway 12.34.56.129 This is a problem, because of this automatic modification the slave server can not connect to the master anymore, because only [email protected] is valid to connect to the master server, NOT [email protected] So ISPConfig3 should not move 12.34.56.111 to eth0:0. but the new IP 12.34.56.222 instead! So the right file content of /etc/networking/interfaces should be: Code: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 12.34.56.111 netmask 255.255.255.0 network 12.34.56.0 broadcast 12.34.56.255 gateway 12.34.56.129 auto eth0:0 iface eth0:0 inet static address 12.34.56.222 netmask 255.255.255.0 network 12.34.56.0 broadcast 12.34.56.255 gateway 12.34.56.129 It would be nice if this behaviour can be changed in the next release of ISPConfig3.
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). Long car drive tomorrow :-(
@Hans: Please post it to the bugtracker so that we can check it. @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.
@edge. I've added a warning text to tthe network settings option to explain when it can not be used. @hans: thanks for the bugtracker entry. Will fix that until 3.0.3 final.
Thank you both. After a +2 hr car drive I managed to fix the server again! (normally it only takes 50 minutes, but I got stuck in a 11 KM traffic jam) On the way back I took a quick lunch at the Mcdonalds (the only fun part about the trip today). I'm now talking to the DC about getting KVM over IP. PS. I've seen a lot of DC's here in the Netherlands, and for sure the girl behind the desk at the DC where I was today is the best looking one! Damn she was cute...
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. http://dev.mysql.com/doc/refman/5.1/en/dns.html 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?
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.
Ok Till, Then i understood everything well. I have only the IPaddresses, FQDNames and hostnames in the /etc/hosts file not the additional IP-addresses. I do hope that the IP-address of the host can stay the first one in /etc/default/interfaces, otherwise I have to change everything after adding additional IPs.
