Difference between revisions of "Amavisd not starting after upgrade from v8.0.x to higher versions(8.5.x,8.6.x and 8.7.x)"
| (6 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | {{BC|Certified}} | |
| − | + | __FORCETOC__ | |
| + | <div class="col-md-12 ibox-content"> | ||
= Amavisd not starting after upgrade from v8.0.x to higher versions(8.5.x,8.6.x and 8.7.x) = | = Amavisd not starting after upgrade from v8.0.x to higher versions(8.5.x,8.6.x and 8.7.x) = | ||
| + | {{KB|{{ZC}}|{{ZCS 8.7}}|{{ZCS 8.6}}|{{ZCS 8.5}}|}} | ||
==== Problem : ==== | ==== Problem : ==== | ||
| − | After upgrade Amavisd not | + | After upgrade Amavisd does not start and zimbra.log shows the following errors. |
Not able to start Amavis services, error : | Not able to start Amavis services, error : | ||
| Line 10: | Line 12: | ||
Dec 21 10:02:29 server amavis<nowiki>[7787]: (!!)TROUBLE in </nowiki>pre_loop_hook: config: no rules were found! Do you need to run 'sa-update'? | Dec 21 10:02:29 server amavis<nowiki>[7787]: (!!)TROUBLE in </nowiki>pre_loop_hook: config: no rules were found! Do you need to run 'sa-update'? | ||
Dec 21 10:02:29 server amavis<nowiki>[</nowiki>7787]: (!)_DIE: Suicide () TROUBLE in pre_loop_hook: config: no rules were found! Do you need to run 'sa-update'? | Dec 21 10:02:29 server amavis<nowiki>[</nowiki>7787]: (!)_DIE: Suicide () TROUBLE in pre_loop_hook: config: no rules were found! Do you need to run 'sa-update'? | ||
| − | |||
==== Solution : ==== | ==== Solution : ==== | ||
| − | + | The problem occurs due to the problems with the SpamAssassin database. | |
| + | To resolve this, we'll have to update the database. | ||
| − | su | + | * If the server has Internet access then running sa-update will resolve the issue: |
| − | /opt/zimbra/zimbramon/bin/sa-update -D | + | su - zimbra |
| − | zmamavisdctl restart | + | In 8.7 and prior: |
| + | /opt/zimbra/zimbramon/bin/sa-update -D | ||
| + | zmamavisdctl restart | ||
| + | In 8.8+: | ||
| + | /opt/zimbra/common/bin/sa-update -D | ||
| + | zmamavisdctl restart | ||
| − | + | * If the server is an isolated network, we'll regenerate the database: | |
| − | If | + | ** Check “state” directory in “/opt/zimbra/data/spamassassin/” |
| − | + | ** If the “state” directory is present, then move it to some other location and restart Amavisd service. | |
| − | * 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 | 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}} | ||
Latest revision as of 12:59, 15 May 2018
Contents
Amavisd not starting after upgrade from v8.0.x to higher versions(8.5.x,8.6.x and 8.7.x)
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
In 8.7 and prior:
/opt/zimbra/zimbramon/bin/sa-update -D zmamavisdctl restart
In 8.8+:
/opt/zimbra/common/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 the “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
