Amavisd not starting after upgrade from v8.0.x to higher versions(8.5.x,8.6.x and 8.7.x): Difference between revisions
m (→Problem :) |
|||
Line 14: | Line 14: | ||
==== Solution : ==== | ==== Solution : ==== | ||
If the server | The problem occurs due to the problems with the SpamAssassin database. | ||
To resolve this, we'll have to update the database. | |||
If the server has Internet access then running sa-update will resolve the issue: | |||
su – zimbra | su – zimbra | ||
Line 20: | Line 23: | ||
zmamavisdctl restart | zmamavisdctl restart | ||
If the server is an isolated network, we'll regenerate the database: | |||
If | |||
* Check “state” directory in “/opt/zimbra/data/spamassassin/”. | * Check “state” directory in “/opt/zimbra/data/spamassassin/”. | ||
Line 30: | Line 31: | ||
mv /opt/zimbra/data/spamassassin/state /tmp/state | mv /opt/zimbra/data/spamassassin/state /tmp/state | ||
zmamavisdctl restart | zmamavisdctl restart | ||
{{Article Footer|Zimbra Collaboration 8.7, 8.6, 8.5| 17/07/2017}} | {{Article Footer|Zimbra Collaboration 8.7, 8.6, 8.5| 17/07/2017}} | ||
{{NeedSME|SME1|SME2|COPY EDITOR}} | {{NeedSME|SME1|SME2|COPY EDITOR}} |
Revision as of 11:57, 15 May 2018
Amavisd not starting after upgrade from v8.0.x to higher versions(8.5.x,8.6.x and 8.7.x)
- This article is a Work in Progress, and may be unfinished or missing sections.
Problem :
After upgrade Amavisd does not start and zimbra.log shows the following errors.
Not able to start Amavis services, error : Dec 21 10:02:29 server amavis[7787]: initializing Mail::SpamAssassin (0) Dec 21 10:02:29 server amavis[7787]: (!!)TROUBLE in pre_loop_hook: config: no rules were found! Do you need to run 'sa-update'? Dec 21 10:02:29 server amavis[7787]: (!)_DIE: Suicide () TROUBLE in pre_loop_hook: config: no rules were found! Do you need to run 'sa-update'?
Solution :
The problem occurs due to the problems with the SpamAssassin database. To resolve this, we'll have to update the database.
If the server has Internet access then running sa-update will resolve the issue:
su – zimbra /opt/zimbra/zimbramon/bin/sa-update -D zmamavisdctl restart
If the server is an isolated network, we'll regenerate the database:
- Check “state” directory in “/opt/zimbra/data/spamassassin/”.
- If “state” directory is present then move it to some other location and restart Amavisd service.
mv /opt/zimbra/data/spamassassin/state /tmp/state zmamavisdctl restart