Policyd'ers,
I have postfix-policyd running on three PF servers,
connected to a dual master set of MySQL servers. Two of the PFs are on the
local subnet of the MySQL servers. One of the PF servers (a low MX,
secondary server) resides in another data center. (180-220ms away).
For the past three months the setup has been performing brilliantly, and
have only recently noticed problems. After restarting the postfix-policyd
daemon it will function as normal for 2-5 minutes before it starts to
return:
-----
Jun 15 11:59:00 secondary postfix-policyd: shutdown(11): Transport endpoint
is not connected
-----
A little while longer and Postfix begins to defer *most* client connections:
-----
Jun 15 12:01:28 secondary postfix/smtpd[32590]: NOQUEUE: reject: RCPT from
mta2.mes2.com[210.9.188.146]: 451 4.3.5 Server configuration problem;
from=<[EMAIL PROTECTED]> to=<xxxx> proto=ESMTP
helo=<mta2.mes2.com>
Jun 15 12:02:47 secondary postfix/smtpd[2603]: warning: problem talking to
server 127.0.0.1:10031: Connection timed out Jun 15 12:02:48 secondary
postfix/smtpd[2601]: warning: timeout on 127.0.0.1:10031 while reading input
attribute name
-----
When trawling through debug=3 logs, this the interesting snippets:
-----
Jun 15 12:02:55 secondary postfix-policyd: connection from: 127.0.0.1 port:
49516 slots: 8 of 4096 used Jun 15 12:02:55 secondary postfix-policyd:
DEBUG: fd: 8 select(): fd 8 is ready for read Jun 15 12:02:55 secondary
postfix-policyd: DEBUG: fd: 8 connection got an EOF, data_read = 0 Jun 15
12:02:55 secondary postfix-policyd: DEBUG: fd: 8 shutting down fd 8 Jun 15
12:02:55 secondary postfix-policyd: DEBUG: fd: 9 select(): fd 9 is ready for
write Jun 15 12:02:55 secondary postfix-policyd: DEBUG: fd: 9 returning
after 14 bytes of data written Jun 15 12:02:55 secondary postfix-policyd:
DEBUG: fd: 10 select(): fd 10 is ready for write Jun 15 12:02:55 secondary
postfix-policyd: DEBUG: fd: 10 returning after 14 bytes of data written Jun
15 12:02:55 secondary postfix-policyd: DEBUG: fd: 11 select(): fd 11 is
ready for read Jun 15 12:02:55 secondary postfix-policyd: DEBUG: fd: 11
connection got an EOF, data_read = 0 Jun 15 12:02:55 secondary
postfix-policyd: DEBUG: fd: 11 shutting down fd 11 Jun 15 12:02:55 secondary
postfix-policyd: shutdown(11): Transport endpoint is not connected
-----
Relevant Postfix config used:
-----
# Set a sensible timeout for our policy daemons smtpd_policy_service_timeout
= 60s ...
# Decisions made after Rcpt To
smtpd_recipient_restrictions =
...
# Query policyd (costs SELECTs,INSERTs,UPDATEs)
check_policy_service inet:127.0.0.1:10031
-----
Relevant policyd config used:
-----
MYSQLHOST="xxxx"
MYSQLDBASE="policyd"
MYSQLUSER="policyd"
MYSQLPASS="xxxx"
MYSQLOPT=""
FAILSAFE=1
DATABASE_KEEPALIVE=1
DEBUG=0
DAEMON=1
BINDHOST=127.0.0.1
BINDPORT=10031
PIDFILE=/var/run/policyd.pid
-----
Monitoring the network inbetween the MySQL servers this machine, there is no
packet loss, and consistent latency (as above ~200ms). Using mysql client
from the same server, logged policyd queries all return in .25 sec:
-----
mysql> SELECT COUNT(*) FROM whitelist_dnsname WHERE
mysql> 'cmx03.servicemail24.de' LIKE _whitelist;
+----------+
| COUNT(*) |
+----------+
| 0 |
+----------+
1 row in set (0.23 sec)
-----
Any ideas on what to try?
Regards
__________________________________________
Dean Manners
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
policyd-users mailing list
policyd-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/policyd-users
