Ubuntu
postgrey package

postgrey crash cleaning main database during delivery

Bug #177389 reported by Ketil Malde
4
Affects Status Importance Assigned to Milestone
postgrey (Ubuntu)
Invalid
Medium
Daniel Hahler

Bug Description

Postgrey crashed, causing my server to subsequently refuse to accept mail. Possibly this happened because postgrey did the cleaning up routine while there was an active connection? Here are the relevant log entries:

Dec 19 02:17:29 localhost postfix/smtpd[30172]: connect from pool-71-163-35-39.washdc.fios.verizon.net[71.163.35.39]
Dec 19 02:17:29 localhost postgrey[4821]: cleaning up old logs...
Dec 19 02:17:29 localhost postgrey[4821]: cleaning up old entries...
Dec 19 02:17:29 localhost postgrey[4821]: cleaning main database finished. before: 121, after: 121
Dec 19 02:17:29 localhost postgrey[4821]: fatal: Can't call method "txn_commit" on an undefined value at /usr/sbin/postgrey line 223.
Dec 19 02:17:30 localhost postfix/smtpd[30172]: warning: connect to 127.0.0.1:60000: Connection refused
Dec 19 02:17:30 localhost postfix/smtpd[30172]: warning: problem talking to server 127.0.0.1:60000: Connection refused
Dec 19 02:17:30 localhost postfix/smtpd[30172]: NOQUEUE: reject: RCPT from pool-71-163-35-39.washdc.fios.verizon.net[71.163.35.39]: 451 4.3.5 Server configuration problem; from=<xxxxxxxxx> to=<xxxxxxxx> proto=ESMTP helo=<pool-71-163-35-39.washdc.fios.verizon.net>
Dec 19 02:17:30 localhost postfix/smtpd[30172]: lost connection after DATA from pool-71-163-35-39.washdc.fios.verizon.net[71.163.35.39]
Dec 19 02:17:30 localhost postfix/smtpd[30172]: disconnect from pool-71-163-35-39.washdc.fios.verizon.net[71.163.35.39]

Revision history for this message
Daniel Hahler (blueyed) wrote :

This is caused by libdb4.4 and filed in bug 153996.
I'm marking it as duplicate.
There is a fix available in gutsy-proposed already.

Revision history for this message
Ketil Malde (ketil-ii) wrote :

Ah, missed that. Thanks for the quick response. Amazing that after two months, Gutsy still comes with mission-critical failures like this, especially when a fix exists.

Revision history for this message
Brian J. Murrell (brian-interlinx) wrote : Re: [Bug 177389] Re: postgrey crash cleaning main database during delivery

On Wed, 2007-12-19 at 07:40 +0000, Ketil Malde wrote:
> *** This bug is a duplicate of bug 153996 ***
> https://bugs.launchpad.net/bugs/153996
>
> Ah, missed that. Thanks for the quick response. Amazing that after two
> months, Gutsy still comes with mission-critical failures like this,
> especially when a fix exists.

Not only exists, but has been sitting in proposed for nearly (if not
more) than a month! So the fix is out there, you just have to know how
to find it. Pretty sad situation in fact.

I dunno what the point of making a fix is if it's never going to get
promoted from proposed to main.

b.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.