Johan Andersson
Cc: Postfix users
Subject: Re: SV: SV: Strange Postfix error
Johan Andersson:
> The problem was solved with a full server reboot (rebooting the
> zone where Postfix is running did not help).
> Strangebut I'm happy for now.
I found a similar problem with Linux on some
>
> -Ursprungligt meddelande-
> Fr?n: owner-postfix-us...@postfix.org
> [mailto:owner-postfix-us...@postfix.org] F?r Johan Andersson
> Skickat: den 20 januari 2012 16:05
> Till: Postfix users
> ?mne: SV: SV: Strange Postfix error
>
> Hi.
>
> The binari
ickat: den 20 januari 2012 16:05
Till: Postfix users
Ämne: SV: SV: Strange Postfix error
Hi.
The binaries used are compiled on a Solaris server and have been in use since
September 21st last year without any problems until yesterday when they
suddenly stopped working. I replaced them with the exact
Wietse Venema:
> Your symptoms indicate a mis-match between the IN-MEMORY master
> daemon process, and the ON-DISK executable files for smtpd, cleanup,
> etc.
Famous last words. This may be the result of a Linux "misfeature"
where a pipe inode number goes over 32bit:
http://bugs.debian.org/cgi-bi
Your symptoms indicate a mis-match between the IN-MEMORY master
daemon process, and the ON-DISK executable files for smtpd, cleanup,
etc.
To fix, see the suggestion at the end of my first reply. This is
my final response.
Wietse
stfix users
Ämne: Re: SV: Strange Postfix error
Johan Andersson:
> Hi
>
> Thanks for your answer.
>
> I don't think that's the answerbecause i haven't replaced anything
> really (well, apart from replacing the binaries with a copy of the
> ones that were a
Johan Andersson:
> Hi
>
> Thanks for your answer.
>
> I don't think that's the answerbecause i haven't replaced
> anything really (well, apart from replacing the binaries with a
> copy of the ones that were already running).
My reply was 100% about the consequences of replacing Postfix binar
Hi
Thanks for your answer.
I don't think that's the answerbecause i haven't replaced anything really
(well, apart from replacing the binaries with a copy of the ones that were
already running).
I also have those binaries running on two more servers and I don't have this
problem there.
Thi
