I appear to be completely up to date on Postgrey and its dependencies as well (running libdb4.4 4.4.20-8.1ubuntu3.1), and as of right now, it is STILL broken as evidenced by the following:
Mar 16 02:22:36 haruhi postgrey[4042]: cleaning up old logs...
Mar 16 02:22:36 haruhi postgrey[4042]: cleaning up old entries...
Mar 16 02:22:37 haruhi postgrey[4042]: cleaning main database finished. before: 6394, after: 1424
Mar 16 02:22:37 haruhi postgrey[4042]: fatal: Can't call method "txn_commit" on an undefined value at /usr/sbin/postgrey line 223.
I just reenabled Postgrey on this machine after not using it for a while (the process had been running the whole time, but I just started using it again on Saturday, March 15, 2008). My users are complaining about mounting spam. About the only way I can fix this is a cronned restart of postgrey every night after its scheduled cleanup time, which is not an acceptable solution.
I appear to be completely up to date on Postgrey and its dependencies as well (running libdb4.4 4.4.20- 8.1ubuntu3. 1), and as of right now, it is STILL broken as evidenced by the following:
Mar 16 02:22:36 haruhi postgrey[4042]: cleaning up old logs...
Mar 16 02:22:36 haruhi postgrey[4042]: cleaning up old entries...
Mar 16 02:22:37 haruhi postgrey[4042]: cleaning main database finished. before: 6394, after: 1424
Mar 16 02:22:37 haruhi postgrey[4042]: fatal: Can't call method "txn_commit" on an undefined value at /usr/sbin/postgrey line 223.
I just reenabled Postgrey on this machine after not using it for a while (the process had been running the whole time, but I just started using it again on Saturday, March 15, 2008). My users are complaining about mounting spam. About the only way I can fix this is a cronned restart of postgrey every night after its scheduled cleanup time, which is not an acceptable solution.
Thank you for your assistance with this matter.
--Ian.