I've a second server as a mirror to provide a failover. However, the auto updates of Ubuntu (from Ubuntu Pro) on the main server are not propagating to the mirror. Also a colleague tells me that the mirror is broken because the main server has an ISPCONFIG update. Please could you clarify.
All systems in a multiserver setup must run the same ISPCnfig version; if the database structure on all systems does not match, data stops being transferred between the nodes until all are updated to the same version again. If your master node has a newer version than the mirror, then please update ISPConfig on the mirror node.
Thanks Till, I've just tried to update the failover mirror server and it is refusing to log into the main server mysql. I've checked the password is ok and can log into the main server mysql from Puty on it but can't log into it from the failover server in the ispconfig update.sh using the same root password. Is there something I'm missing?
Mysql on your main server must have user records for the IP and hostname of the slave node to allow login from the mirror node for the update. They must have existed at the time you installed the mirror node, maybe you removed them or they have a different password.
I just realised the actual problem is that just after I created the fallback mirror I'd moved its IP to a different network for security reasons . I'm guessing that's almost certainly what orphaned the grants and broke sync, independent of the version question. If I reinstall the ISPConfig mirror component (to force a clean rejoin at the new IP) is that the right fix, or is there a lighter resync command that just needs the grants/host config redone for the new IP, or do I have to do something else? Currently, there is almost no data in the mirror and only a few entries in the database compared to the server being mirrored.
The IP address change is the most likely reason indeed. Change the IP address in the hosts files on both servers. Then edit the root and ispcsrv* user for this IP in the master mariadb database using phpmadmin user editor. The system should start syncing then again. A resync is not needed unless the sync is broken for more than 30 days.
Thank you Till. that is very helpful. The sync has been broken for several months so I'm presuming a resync is necessary once I've fixed the IP addresses. I'm new to this aspect of ISPCONFIG and I'm assuming the resync is the one under Tools in the master server and its is necessary to resync everything? Its not a huge transfer - only 30 or so websites and 25 emails and within the same infrastructure.
