Comparez les prix des domaines et des services informatiques des vendeurs du monde entier

Échec Amavis resolve_mail_destiny

Après la mise à niveau vers FreeBSD 12 J'ai des problèmes avec

amavis

de temps en temps.

La cause de l'accident n'est toujours pas claire.

Plaine

kill -9 $amavispid && service amavids start

Fait son travail, mais après quelques heures, tout recommence.

C'est la conclusion d'un magazine d'échec:

Dec 19 02:51:14 mailserver postfix/pickup[9697]: 75223B166: uid=58 from=<mailer-daemon>
Dec 19 02:51:14 mailserver postfix/pipe[17647]: 7A3F1B162: to=<some.user@example.org>, relay=spamassassin, delay=1.1, delays=0.44/0/0/0.68, dsn=2.0.0, status=sent (delivered via spamassassin service)
Dec 19 02:51:14 mailserver postfix/qmgr[850]: 7A3F1B162: removed
Dec 19 02:51:14 mailserver postfix/cleanup[17644]: 75223B166: message-id=&lt;20181219015108.935034EB31B@emlqa-msgrly001.reyqa.reyrey.net&gt;
Dec 19 02:51:14 mailserver postfix/qmgr[850]: 75223B166: from=&lt;&gt;, size=7592, nrcpt=1 (queue active)
Dec 19 02:51:14 mailserver spamd[758]: prefork: child states: II
Dec 19 02:51:15 mailserver amavis[772]: (00772-07) (!!)TROUBLE in check_mail: decide_mail_destiny FAILED: register_proc: BDB N c_get: BDB0061 PANIC: Invalid argument, No such process. at (eval 93) line 222.
Dec 19 02:51:15 mailserver amavis[772]: (00772-07) (!!)TROUBLE in process_request: register_proc: BDB N db_cursor: BDB0060 PANIC: fatal region error detected; run recovery, . at (eval 93) line 220.
Dec 19 02:51:15 mailserver amavis[772]: (00772-07) (!)Requesting process rundown after fatal error
Dec 19 02:51:15 mailserver amavis[772]: (00772-07) (!)TempDir removal: tempdir is to be PRESERVED: /var/amavis/tmp/amavis-20181218T235619-00772-TJFdgQp3
Dec 19 02:51:15 mailserver amavis[772]: (00772-07) (!)_DIE: register_proc: BDB N db_cursor: BDB0060 PANIC: fatal region error detected; run recovery, . at (eval 93) line 220.
Dec 19 02:51:15 mailserver postfix/lmtp[17651]: 6CB9FB164: to=<some.user@example.org>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.87, delays=0.01/0.01/0/0.85, dsn=4.3.2, status=deferred (host 127.0.0.1[127.0.0.1] said: 421 4.3.2 Service shutting down, closing channel (in reply to end of DATA command))
Dec 19 02:51:15 mailserver amavis[772]: (00772-07) (!)Amavis::END: DB unregistering failed:
Dec 19 02:51:15 mailserver amavis[17658]: (!!)TROUBLE in child_init_hook: BDB can't connect db env. at /var/amavis/db: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery, No such file or directory. at (eval 93) line 338.
Dec 19 02:51:15 mailserver amavis[17658]: (!)_DIE: Suicide in child_init_hook: BDB can't connect db env. at /var/amavis/db: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery, No such file or directory. at (eval 93) line 338.
Dec 19 02:51:15 mailserver amavis[17659]: (!!)TROUBLE in child_init_hook: BDB can't connect db env. at /var/amavis/db: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery, No such file or directory. at (eval 93) line 338.
Dec 19 02:51:15 mailserver amavis[17659]: (!)_DIE: Suicide in child_init_hook: BDB can't connect db env. at /var/amavis/db: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery, No such file or directory. at (eval 93) line 338.
Dec 19 02:51:15 mailserver amavis[17660]: (!!)TROUBLE in child_init_hook: BDB can't connect db env. at /var/amavis/db: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery, No such file or directory. at (eval 93) line 338.
Dec 19 02:51:15 mailserver amavis[17660]: (!)_DIE: Suicide in child_init_hook: BDB can't connect db env. at /var/amavis/db: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery, No such file or directory. at (eval 93) line 338.
Dec 19 02:51:15 mailserver amavis[17661]: (!!)TROUBLE in child_init_hook: BDB can't connect db env. at /var/amavis/db: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery, No such file or directory. at (eval 93) line 338.
Dec 19 02:51:15 mailserver amavis[17661]: (!)_DIE: Suicide in child_init_hook: BDB can't connect db env. at /var/amavis/db: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery, No such file or directory. at (eval 93) line 338.
Dec 19 02:51:15 mailserver amavis[17662]: (!!)TROUBLE in child_init_hook: BDB can't connect db env. at /var/amavis/db: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery, No such file or directory. at (eval 93) line 338.
Dec 19 02:51:15 mailserver amavis[17662]: (!)_DIE: Suicide in child_init_hook: BDB can't connect db env. at /var/amavis/db: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery, No such file or directory. at (eval 93) line 338.

Les dernières lignes continuent jusqu'à ce que je tue le service et que je ne spâte pas au fichier journal.

Encore une fois, après avoir redémarré le service, tout est en ordre. Les ressources système ne sont pas épuisées. Télécharger le processeur 0.5, La mémoire reste beaucoup (~ 20%), Les disques ne sont pas remplis.

Je ne sais pas où regarder ...

PS: Bien sûr, les noms des hôtes et des domaines changent

Edit: Juste si quelqu'un d'autre est confronté à ce problème, j'ai trouvé une solution de contournement. Vous pouvez simplement désactiver la fonction de base de données Berkley, qui met en cache des résultats à travers

$enable_db = 0;

Ce n'est pas une solution, mais le chemin de dérivation!
</some.user@example.org></some.user@example.org></mailer-daemon>
Invité:

Pour répondre aux questions, connectez-vous ou registre