ISPConfig 3 Master-Master Upgrade

Discussion in 'Installation/Configuration' started by mphayesuk, Sep 29, 2017.

  1. mphayesuk

    mphayesuk Member HowtoForge Supporter

    Hi everyone, I have a master master configuration. 2 Debian system configured as per the "perfect setup guide", using mysql replication and Unison.

    My question is what is the upgrade order? Do I need to stop any replication first?

  2. Brett Wilton

    Brett Wilton Member

    interested in recommendations on this as well
  3. concept21

    concept21 Active Member HowtoForge Supporter

    Build a Mysql cluster with 3 members. It is the simplest.
    Try Percona mysql Cluster. :cool:
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    In regard to ISPConfig, the master should always be updated first. The reason is that when you update a slave and choose "reconfigure permissions in master database", then the assignment of new rights to the ispcsrv* user of the slave will fail when the database column that shall be configured does not exist on the master yet. Of course, sould should try to not use ISPConfig until both nodes are updated.

    I guess a question is also if you want to update just ISPConfig or the OS as well. For an ISPConfig update it should be fine to keep the replication running. But I'm not sure what the best option for an OS upgrade with a major MySQL change is, probably one should stop replication first. But you might find more info on this in the mysql docs.
  5. Brett Wilton

    Brett Wilton Member

    thanks tim. I suspect concept21's response is spam.
  6. ISPConfig Developer ISPConfig Developer

    @till major upgrade for mysql is not an issue, highly depends on what databases are replicated ofc, replicating the mysql database usually causes issues in the update process for debian [ update on master is replicated to 2nd master or slave, so database is up2date, then update on 2nd server may fail ]
    master-master replication on mysql does work pretty good ( or percona or maria, doesn't matter much for most common use cases ).

    @Brett Wilton it's not really spam, just not very well explained ;)
    another issue might be, if you don't have failover IP configured ( both master have the same IP configured and you set IP to point to one or the other server ) master master might uhm yeah leave you with webs configured for a wrong IP ;)
    but besides that there shouldn't be much of an issue doing that without the support of ISPConfig, just rsync backup folder, vmail, webs and passwd/group files and you should be good to go.
  7. mphayesuk

    mphayesuk Member HowtoForge Supporter

    Thanks all for your comments, I will try an ISPConfig upgrade in the next couple of days.
    I did however try an OS upgrade from Debian 6 to 7 which failed (I had backuped up the vm's first though), its probably a question for another forum/topic but I was faced with questions related to configuration files have been changed manually and what I would like to do, leave them or upgrade them, I selected leave them and SQL broke. I will stick with an ISPConfig upgrade for now.

    Thanks again for the answers.
  8. ISPConfig Developer ISPConfig Developer

    debian 6 to 7 really? should work flawlessly, however take a backup and use that to find the issue, shouldn't be too complicated. Maybe post the files the upgrade process wants to change and you're not sure about?
  9. mphayesuk

    mphayesuk Member HowtoForge Supporter

    FYI the upgrade to v3.1 worked with no real issues, master first and then slave, the slave upgrade did ask me for the master mysql details (server, user, pass) so not sure if that is something to do with my configuration or not. Thanks for the help and advice.
  10. Brett Wilton

    Brett Wilton Member

    I performed the upgrade last night from 3.1.6 to 3.1.7p1 on the master then the slave (master) I had an issue with the mail failing after upgrade so I rolled back the VM and made sure I didn't select "Reconfigure services" and all worked correctly.
    Issue with the mail was that postgrey was rejecting all received emails.

Share This Page