Gordon Messmer wrote: > ... > > My guess is that "apt-get dist-upgrade" updated your python, and the new > version doesn't support whichever DBM was the default in the old > version. Since Debian packages python-gdbm separately from python, I'd > guess further that you don't have that package installed now. > > Any time you use "dist-upgrade", you should carefully check the results, > and restart all of the services on your system to make sure that they > continue to function. For a stable system, "dist-upgrade" is not > something you should do often. > But WHY did it take TWO days before Courier started to play up...
Further analysis of the log files shows that the problem actually started earlier. At 21:46:53 on March 5 the system was rebooted due to a power outage. In the syslog spamage that occurs when a Linux box starts up, I can see Courier complaining about pythonfilter being unable to handle /var/state/pythonfilter/auto_whitelist. At 22:02:04, 5 emails locally generated from the server were successfully delivered - they aren't filtered for greylisting so the fact that pythonfilter wasn't working wasn't noticed. At 22:17:51, the first email to be rejected with "432 Mail filters temporarily unavailable" is rejected. The plot thickens.... > The only question is: why did courier restart at 1AM? Probably a cron > job of some type. > Sam's answered it perfectly well - it does it all itself. > ... > You can use "file" on the old DBMs and the new ones to confirm (or not) > that the type of DBM changed. This is where things get interesting. The saved out copy of one of the non-overwritten "faulty" files via `file greylist_whitelistDomains` gives: greylist_whitelistDomains: Berkeley DB (Hash, version 9, native byte-order) `file /var/state/pythonfilter/greylist_whitelistDomains` gives: /var/state/pythonfilter/greylist_whitelistDomains: Berkeley DB (Hash, version 8, native byte-order) It seems that when the server was rebooted either the version of the file changed, or when pythonfilter was restarted it wasn't expecting a version 9 file. Looking at /var/log/apt/term.log it shows that in the update on the 4th of March, python2.4-minimal and python2.4 were both upgraded from 2.4.4-7 to 2.4.4-8 - I'm suspecting that this has changed some of the default values which pythonfilter depends on. In either case, something changed and I was able to fix it ultimately, so I'm happy. Cheers, Tim Lyth ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
