Postfix 2.2, CentOS 4 (yes, I want to upgrade; can't for now).
Note: I have a course of action, but not completely confident I
understand the problem so seeking other eyes on it. See bottom.
On a fallback relay serving several first-pass postfix servers, qmgr
seems to sometimes stop and rest whi
Ofer Inbar:
> Postfix 2.2, CentOS 4 (yes, I want to upgrade; can't for now).
Perhaps you should upgrade.
> # strace -p 31741
> Process 31741 attached - interrupt to quit
> futex(0x2a96b46930, FUTEX_WAIT, 2, NULL ^C
Postfix does not manipulate futexes. The word futex appears
nowhere in Postfix so
Wietse Venema <[EMAIL PROTECTED]> wrote:
> > # strace -p 31741
> > Process 31741 attached - interrupt to quit
> > futex(0x2a96b46930, FUTEX_WAIT, 2, NULL ^C
>
> Postfix does not manipulate futexes. The word futex appears
> nowhere in Postfix source code.
>
> However, there's a mutex deadlock in t
On Tue, Oct 21, 2008 at 07:07:02PM -0400, Ofer Inbar wrote:
> I have noticed occasional qmgr crashes with the "watchdog timer" error
> occurring, usually when it's in the middle of deferring thousands of
> messages for one domain all at once. I meant to investigate those.
>
> However, based on t
Victor Duchovni <[EMAIL PROTECTED]> wrote:
> You can skip waiting for future occurences, the behaviour you describe
> (especially on fallback relays where dead destinations are to be expected)
> fits the known issue like a glove (and we are not at the OJ trial :-).
Regardless, I definitely sometim
On Wed, Oct 22, 2008 at 12:06:40AM -0400, Ofer Inbar wrote:
> Victor Duchovni <[EMAIL PROTECTED]> wrote:
> > You can skip waiting for future occurences, the behaviour you describe
> > (especially on fallback relays where dead destinations are to be expected)
> > fits the known issue like a glove (
Victor Duchovni <[EMAIL PROTECTED]> wrote:
> > However, I'm puzzled - it defaults to 18000s but the watchdog timer
> > seems to kill qmgr during these incidents after about a half hour,
> > which is 1800 seconds.
>
> Wrong timer. The watchdog timeout is hard-coded to 1000s.
Ahhh. I was going on
Ofer Inbar:
> Victor Duchovni <[EMAIL PROTECTED]> wrote:
> > > However, I'm puzzled - it defaults to 18000s but the watchdog timer
> > > seems to kill qmgr during these incidents after about a half hour,
> > > which is 1800 seconds.
> >
> > Wrong timer. The watchdog timeout is hard-coded to 1000s.
