policyd crashing unexpectedly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pypolicyd-spf |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I'm using "1.2: JULY 25, 2013" under Ubuntu 14.04, setup as per this page: https:/
I've noticed the following exceptions...
Mar 3 11:24:28 ubuntu postfix/
Mar 3 11:26:08 ubuntu postfix/
Mar 3 11:26:36 ubuntu policyd-spf[22979]: Temperror; identity=helo; client-
Mar 3 11:26:36 ubuntu policyd-spf[22979]: Pass; identity=mailfrom; client-
Mar 3 11:26:36 ubuntu policyd-spf[22979]: Traceback (most recent call last):
Mar 3 11:26:36 ubuntu policyd-spf[22979]: File "/usr/bin/
Mar 3 11:26:36 ubuntu policyd-spf[22979]: sys.stdout.flush()
Mar 3 11:26:36 ubuntu policyd-spf[22979]: BrokenPipeError: [Errno 32] Broken pipe
Mar 3 11:26:36 ubuntu postfix/
Mar 3 11:27:49 ubuntu postfix/
Mar 3 11:27:49 ubuntu postfix/
Mar 3 11:27:50 ubuntu postfix/
Mar 3 13:58:17 ubuntu policyd-spf[2594]: Temperror; identity=helo; client-
Mar 3 13:58:18 ubuntu policyd-spf[2594]: Pass; identity=mailfrom; client-
Mar 3 13:58:18 ubuntu policyd-spf[2594]: Traceback (most recent call last):
Mar 3 13:58:18 ubuntu policyd-spf[2594]: File "/usr/bin/
Mar 3 13:58:18 ubuntu policyd-spf[2594]: line = sys.stdin.
Mar 3 13:58:18 ubuntu policyd-spf[2594]: ConnectionReset
Mar 3 13:58:18 ubuntu postfix/
Changed in pypolicyd-spf: | |
status: | New → Incomplete |
That's an odd one. Based on the logs you provide, the policy server is producing results, but also timing out. The two points where it times out are both lines related to logging. Is there a chance there's a problem with your syslog service? The warning that postfix/spawn killed it is normal when something is taking too long.