Recovering from upgrade failure: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
= Recovering from upgrade failure due to remote package installation issues = | {{BC|Certified}} | ||
__FORCETOC__ | |||
<div class="col-md-12 ibox-content"> | |||
=Recovering from upgrade failure due to remote package installation issues= | |||
{{KB|{{ZC}}|{{ZCS 8.7}}|||}} | |||
With ZCS 8.7 and later, various packages are installed via a remote repository. If installation of these packages fail during the upgrade process, the system can end up in an irrecoverable state unless the proper steps are followed. | With ZCS 8.7 and later, various packages are installed via a remote repository. If installation of these packages fail during the upgrade process, the system can end up in an irrecoverable state unless the proper steps are followed. | ||
During the installation process, an install log is written to /tmp. The exact name of the log file is displayed. For example: | During the installation process, an install log is written to '''/tmp'''. The exact name of the log file is displayed. For example: | ||
<pre>Local packages zimbra-core zimbra-ldap zimbra-logger zimbra-mta zimbra-dnscache zimbra-snmp zimbra-store zimbra-apache zimbra-spell zimbra-convertd zimbra-proxy zimbra-archiving selected for installation | |||
< | |||
Local packages zimbra-core zimbra-ldap zimbra-logger zimbra-mta zimbra-dnscache zimbra-snmp zimbra-store zimbra-apache zimbra-spell zimbra-convertd zimbra-proxy zimbra-archiving selected for installation | |||
Monitor /tmp/install.log.9eeEI4KR for package installation progress | Monitor /tmp/install.log.9eeEI4KR for package installation progress | ||
Remote package installation started | Remote package installation started | ||
Installing zimbra-core-components zimbra-ldap-components zimbra-mta-components zimbra-dnscache-components zimbra-snmp-components zimbra-store-components zimbra-apache-components zimbra-spell-components zimbra-memcached zimbra-proxy-components.... | Installing zimbra-core-components zimbra-ldap-components zimbra-mta-components zimbra-dnscache-components zimbra-snmp-components zimbra-store-components zimbra-apache-components zimbra-spell-components zimbra-memcached zimbra-proxy-components.... | ||
</ | </pre> | ||
So in this case, if things break, we would examine /tmp/install.log.9eeEI4KR for the reason as to why it failed. It will be necessary to resolve the logged issue before proceeding. Once the issue is resolved, the upgrade process can be restarted using special options passed to the installer: | So in this case, if things break, we would examine '''/tmp/install.log.9eeEI4KR''' for the reason as to why it failed. It will be necessary to resolve the logged issue before proceeding. Once the issue is resolved, the upgrade process can be restarted using special options passed to the installer: | ||
./install.sh --force-upgrade --skip-activation-check --skip-upgrade-check | |||
./install.sh --force-upgrade --skip-activation-check --skip-upgrade-check | |||
When installing, package selection will have to be manually chosen, as the information about what used to be installed will have been lost. Note that this is logged as part of the original install process so it is easy to recover. From the above example, we see: | When installing, package selection will have to be manually chosen, as the information about what used to be installed will have been lost. Note that this is logged as part of the original install process so it is easy to recover. From the above example, we see: | ||
<pre> | |||
< | |||
Installing zimbra-core-components zimbra-ldap-components zimbra-mta-components zimbra-dnscache-components zimbra-snmp-components zimbra-store-components zimbra-apache-components zimbra-spell-components zimbra-memcached zimbra-proxy-components.... | Installing zimbra-core-components zimbra-ldap-components zimbra-mta-components zimbra-dnscache-components zimbra-snmp-components zimbra-store-components zimbra-apache-components zimbra-spell-components zimbra-memcached zimbra-proxy-components.... | ||
Local packages zimbra-core zimbra-ldap zimbra-logger zimbra-mta zimbra-dnscache zimbra-snmp zimbra-store zimbra-apache zimbra-spell zimbra-convertd zimbra-proxy zimbra-archiving | Local packages zimbra-core zimbra-ldap zimbra-logger zimbra-mta zimbra-dnscache zimbra-snmp zimbra-store zimbra-apache zimbra-spell zimbra-convertd zimbra-proxy zimbra-archiving | ||
</ | </pre> | ||
It is possible then to put together what packages are required to recover. | It is possible then to put together what packages are required to recover. | ||
<pre>zimbra-memcached from REMOTE components means zimbra-memcached was installed | |||
< | |||
zimbra-memcached from REMOTE components means zimbra-memcached was installed | |||
zimbra-core can be ignored, it is always included | zimbra-core can be ignored, it is always included | ||
zimbra-ldap from LOCAL components means zimbra-ldap was installed | zimbra-ldap from LOCAL components means zimbra-ldap was installed | ||
| Line 41: | Line 37: | ||
zimbra-archiving from LOCAL compoents means zimbra-archiving was installed. | zimbra-archiving from LOCAL compoents means zimbra-archiving was installed. | ||
zimbra-apache from LOCAL components is picked up automatically if zimbra-spell for zimbra-convertd was installed, and is not uniquely selectable | zimbra-apache from LOCAL components is picked up automatically if zimbra-spell for zimbra-convertd was installed, and is not uniquely selectable | ||
</ | </pre> | ||
When the menu system prompts for packages to be installed, correctly match the above list to the package installation questions. | When the menu system prompts for packages to be installed, correctly match the above list to the package installation questions. | ||
{{Article Footer|Zimbra Collaboration Suite 8.7|26/04/2016}} | |||
{{NeedSME|Quanah|SME2|Copyeditor}} | |||
[[Category:Upgrade]] | |||
[[Category:ZCS 8.7]] | |||
Revision as of 15:59, 26 April 2016
Recovering from upgrade failure due to remote package installation issues
With ZCS 8.7 and later, various packages are installed via a remote repository. If installation of these packages fail during the upgrade process, the system can end up in an irrecoverable state unless the proper steps are followed.
During the installation process, an install log is written to /tmp. The exact name of the log file is displayed. For example:
Local packages zimbra-core zimbra-ldap zimbra-logger zimbra-mta zimbra-dnscache zimbra-snmp zimbra-store zimbra-apache zimbra-spell zimbra-convertd zimbra-proxy zimbra-archiving selected for installation Monitor /tmp/install.log.9eeEI4KR for package installation progress Remote package installation started Installing zimbra-core-components zimbra-ldap-components zimbra-mta-components zimbra-dnscache-components zimbra-snmp-components zimbra-store-components zimbra-apache-components zimbra-spell-components zimbra-memcached zimbra-proxy-components....
So in this case, if things break, we would examine /tmp/install.log.9eeEI4KR for the reason as to why it failed. It will be necessary to resolve the logged issue before proceeding. Once the issue is resolved, the upgrade process can be restarted using special options passed to the installer:
./install.sh --force-upgrade --skip-activation-check --skip-upgrade-check
When installing, package selection will have to be manually chosen, as the information about what used to be installed will have been lost. Note that this is logged as part of the original install process so it is easy to recover. From the above example, we see:
Installing zimbra-core-components zimbra-ldap-components zimbra-mta-components zimbra-dnscache-components zimbra-snmp-components zimbra-store-components zimbra-apache-components zimbra-spell-components zimbra-memcached zimbra-proxy-components.... Local packages zimbra-core zimbra-ldap zimbra-logger zimbra-mta zimbra-dnscache zimbra-snmp zimbra-store zimbra-apache zimbra-spell zimbra-convertd zimbra-proxy zimbra-archiving
It is possible then to put together what packages are required to recover.
zimbra-memcached from REMOTE components means zimbra-memcached was installed zimbra-core can be ignored, it is always included zimbra-ldap from LOCAL components means zimbra-ldap was installed zimbra-logger from LOCAL components means zimbra-logger was installed zimbra-mta from LOCAL components means zimbra-mta was installed zimbra-dnscache from LOCAL components means zimbra-dnscache was installed zibmra-snmp from LOCAL components means zimbra-snmp was installed zimbra-store from LOCAL components means zimbra-store was installed zimbra-spell from LOCAL components means zimbra-spell was installed. This will also include zimbra-apache automatically zimbra-convertd from LOCAL components means zimbra-convertd was installed. This will also include zimbra-apache automatically zimbra-proxy from LOCAL components means zimbra-proxy was installed. zimbra-archiving from LOCAL compoents means zimbra-archiving was installed. zimbra-apache from LOCAL components is picked up automatically if zimbra-spell for zimbra-convertd was installed, and is not uniquely selectable
When the menu system prompts for packages to be installed, correctly match the above list to the package installation questions.
