Re: [courier-users] Pythonfilter going defunct

This is a discussion on Re: [courier-users] Pythonfilter going defunct within the Courier-Imap forums, part of the Mail Servers and Related category; Tim Lyth wrote: > But WHY did it take TWO days before Courier started to play up... > Because "...


Go Back   Usenet Forums > Mail Servers and Related > Courier-Imap

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 03-07-2008
Gordon Messmer
 
Posts: n/a
Default Re: [courier-users] Pythonfilter going defunct

Tim Lyth wrote:
> But WHY did it take TWO days before Courier started to play up...
>


Because "dist-upgrade" doesn't restart running services. If you remove
the libraries used by a running process, the files stay on disk and
available until the process exits. That's why you should probably
reboot after a "dist-upgrade" and verify that each service is still
functional. "dist-upgrade" is not a trivial operation, and should only
be done by hand when you're upgrading your system.

> 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.
>


That makes a lot more sense.

>> 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.
>


I was thinking more along the lines of "why did courierfilter restart at
1am". courierd doesn't restart the filters. There wasn't any real
reason for that problem to start at 1am based on the information that
you provided. If the host restarted earlier due to a power problem, and
filters stopped working at that point, then there is no mystery.

>> ...
>> 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)
>


So, after a "dist-upgrade", python is now linked against a different
(older?) version of libdb.

I think that's ridiculous, but that's why you ought not casually do
"dist-upgrade"s.

I certainly hope that wouldn't have happened by an "upgrade" alone.
Does your log indicate any libdb updates?


-------------------------------------------------------------------------
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/.../courier-users
Reply With Quote
Reply
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT +1. The time now is 10:31 AM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0