Best Practices for executing Package Updates: Difference between revisions
mNo edit summary |
|||
Line 10: | Line 10: | ||
==Update the Zimbra Packages list== | ==Update the Zimbra Packages list== | ||
First step to follow before run a package update on Zimbra Collaboration is to run '''apt-get''' or '''yum update''' on the server, as this can take some minutes, as root: | 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''' | '''* Note, we recommend to run all the next commands in a screen session, just run the command screen, and start working from there''' | ||
Revision as of 17:06, 4 October 2016
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
Services that need to be stopped before the upgrade
amavis | antispam |
antivirus | convertd |
dnscache | logger |
mailbox | memcached |
mta | opendkim |
proxy | service webapp |
snmp | spell |
stats | zimbra webapp |
zimbraAdmin webapp | zimlet webapp |
Stop the components using CLI
You can find handy to have this CLI commands to stop the services before run the upgrade, please note that you might not have some of this services, depending on which services you have in each Zimbra node:
zmamavisdctl stop zmantispamctl stop zmantivirusctl stop zmconvertctl stop zmdnscachectl stop zmloggerctl stop zmmailboxdctl stop zmmemcachedctl stop zmmtactl stop zmopendkimctl stop zmproxyctl stop zmspellctl stop zmstatctl stop zmstorectl stop
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.