Difference between revisions of "Upgrade to 8.6 fails with "Error: assertion '-r/opt/zimbra/conf/my.cnf' failed""
(2 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
− | == | + | {{BC|Certified}} |
+ | __FORCETOC__ | ||
+ | <div class="col-md-12 ibox-content"> | ||
+ | =Upgrade to 8.6 fails with "Error: assertion '-r /opt/zimbra/conf/my.cnf' failed"= | ||
<hr> | <hr> | ||
− | + | {{KB|{{ZC}}|{{ZCS 8.6}}|||}} | |
− | |||
− | |||
− | + | ====Problem==== | |
+ | |||
+ | After an upgrade, starting Zimbra services fails with the following error in /var/log/zimbra.log | ||
Error: assertion '-r /opt/zimbra/conf/my.cnf' failed | Error: assertion '-r /opt/zimbra/conf/my.cnf' failed | ||
− | + | ||
+ | ====Solution==== | ||
This usually comes up when the store package is selected to be upgraded on a non-mailbox server. | This usually comes up when the store package is selected to be upgraded on a non-mailbox server. | ||
Line 26: | Line 30: | ||
rpm -e <package-name> | rpm -e <package-name> | ||
− | + | {{Article Footer|ZCS 8.6|2018-08-13}} | |
− | |||
− |
Latest revision as of 14:45, 31 August 2018
Contents
Upgrade to 8.6 fails with "Error: assertion '-r /opt/zimbra/conf/my.cnf' failed"
Problem
After an upgrade, starting Zimbra services fails with the following error in /var/log/zimbra.log
Error: assertion '-r /opt/zimbra/conf/my.cnf' failed
Solution
This usually comes up when the store package is selected to be upgraded on a non-mailbox server.
For example if the server contains only the LDAP server on 8.0.8, and then during upgrade the mailbox store component is selected, the error comes up and the upgrade does not continue.
To fix this, remove the zimbra-store package using the OS' package manager.
For example, on Redhat/CentOS systems, first get the mailbox package name :
rpm -qa | grep zimbra-store
And then remove it:
rpm -e <package-name>