Best Practices for executing Package Updates
Best Practices for executing Package Updates
Starting in Zimbra Collaboration 8.7, Zimbra uses repositories for 3rd party packages, in the first step towards having the whole product fully installable from repositories.
Update the Zimbra Packages list
First step to follow before run a package update on Zimbra Collaboration, using the third package repository, is to run apt-get or yum update on the server, as this can take some minutes, as root:
* Note, we recommend to run all the next commands in a screen session, just run the command screen, and start working from there
Ubuntu
apt-get update
Red Hat/CentOS
yum update
Stopping the components before run the Zimbra Package upgrade
Before run the upgrade on the Zimbra Serverm it's really important that the next components are in stop mode, depending on the type of Zimbra Node (LDAP, MTA, Proxy or Mailbox), you should stop some services:
Services that need to keep running during the upgrade
It's really important to keep the ldap and zmconfigd packages up during the upgrade process:
- ldap
- zmconfigd
Stop the components using CLI
Before run the Zimbra upgrade for third party packaging, stop the Zimbra Services and once finished, please start the ldap and zmconfigd service like this:
zmcontrol stop ldap start zmconfigdctl start
Run the Zimbra Package upgrade
Once the services are properly stopped, you can run the upgrade on the server, as this can take some minutes, as root:
Ubuntu
apt-get dist-upgrade
Red Hat/CentOS
yum upgrade
Starting the components after run the Zimbra Package upgrade
After run the upgrade process, the best command to restart all the services on the Zimbra node is:
zmcontrol restart
So you will restart all the services with just one command.
Additonal Content
Identified Support Issues
- No Support issues reported yet.