Javier Marcon Servilink Web Hosting wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello, I have some servers working with policyd 1.82, postfix and
> amavis. In one of the servers, mostly every day, policyd stops working
> and logs this error message:
>
> cat /var/log/syslog | grep policy
> Oct 15 16:52:31 server10 policyd: rcpt=22507, whitelist=bypass,
> host=127.0.0.1 (localhost.localdomain),
> [EMAIL PROTECTED], [EMAIL PROTECTED], size=0
> Oct 15 16:52:31 server10 policyd: shutdown(11): Transport endpoint is
> not connected
> Oct 15 16:52:31 server10 policyd: shutdown(10): Transport endpoint is
> not connected
> Oct 15 16:56:27 server10 policyd: connection from: 127.0.0.1 port: 38250
> slots: 0 of 4096 used
> Oct 15 16:56:27 server10 policyd: connection from: 127.0.0.1 port: 38251
> slots: 1 of 4096 used
> Oct 15 16:56:29 server10 policyd: connecting to mysql database: 127.0.0.1
> Oct 15 17:00:21 server10 /USR/SBIN/CRON[27790]: (policyd) CMD
> (/usr/local/policyd/cleanup -c /usr/local/policyd/policyd.conf)Oct 15
> 17:00:28 server10 cleanup: clean up process starting: policyd v1.82
> Oct 15 17:27:37 server10 policyd: starting policyd v1.82
> Oct 15 17:27:37 server10 policyd: connecting to mysql database: 127.0.0.1
> Oct 15 17:27:37 server10 policyd: connected..
> Oct 15 17:31:45 server10 stats: processing statistics: policyd v1.82
> Oct 15 18:00:01 server10 /USR/SBIN/CRON[21898]: (policyd) CMD
> (/usr/local/policyd/cleanup -c /usr/local/policyd/policyd.conf)Oct 15
> 18:00:02 server10 cleanup: clean up process starting: policyd v1.82
> Oct 15 19:00:02 server10 /USR/SBIN/CRON[11533]: (policyd) CMD
> (/usr/local/policyd/cleanup -c /usr/local/policyd/policyd.conf)Oct 15
> 19:00:02 server10 cleanup: clean up process starting: policyd v1.82
>
> When it happens, it stucks all the mail queue of the server.
>
> How can I fix this, what is causing it?
>
> Thanks.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFI907c7aXmWTCrWxoRAqm9AJ92E7Jb6GG7U2vnxMy+zm5dis5QpQCZAaDk
> gAPtaebWQzGtGg9XfxjKMMA=
> =ckC3
> -----END PGP SIGNATURE-----
> _______________________________________________
> Users mailing list
> [email protected]
> http://lists.policyd.org/mailman/listinfo/users
>
>
I'm only guessing, but it seems to me that you have failsafe turned off
in your policyd.conf file. When the cleanup process starts, most likely
the mysql server fails to respond to policyd in a timely manner and so
policyd thinks the there is something wrong with the database.
If you have failsafe turned on, policyd doesn't throw any error and mail
gets accepted anyway (it all gets automatically temporarily
whitelisted). If failsafe is set to off, policyd returns a temp fail.
Could that be it?
Regards,
Hugo Monteiro.
--
ci.fct.unl.pt:~# cat .signature
Hugo Monteiro
Email : [EMAIL PROTECTED]
Telefone : +351 212948300 Ext.15307
Centro de Informática
Faculdade de Ciências e Tecnologia da
Universidade Nova de Lisboa
Quinta da Torre 2829-516 Caparica Portugal
Telefone: +351 212948596 Fax: +351 212948548
www.ci.fct.unl.pt [EMAIL PROTECTED]
ci.fct.unl.pt:~# _
_______________________________________________
Users mailing list
[email protected]
http://lists.policyd.org/mailman/listinfo/users
