|Main Archive Page > Month Archives > postfix-users archives|
Thanks again for your help. Also thanks to Viktor for his thoughts about the
I checked and I see I do in fact have an old version of postfix installed, which
is 2.3.3. This is surprising because I installed it using "yum install
postfix", which I had assumed would install the most recent version.
Anyway, what would be the best way to upgrade? I see from some Google searches
that there can be issues if you try to do a yum install while postfix is
running. Could I just stop postfix and do "yum install postfix-2.7.1"? Would I
need to uninstall the current postfix first then re-install the correct version?
I am on centos:
Linux version 2.6.18-194.11.4.el5xen (email@example.com) (gcc
version 4.1.2 20080704 (Red Hat 4.1.2-48)) #1 SMP Tue Sep 21 05:40:24 EDT 2010
----- Original Message ----
From: Wietse Venema <firstname.lastname@example.org>
To: Postfix users <email@example.com>
Sent: Fri, October 15, 2010 11:25:47 AM
Subject: Re: intermittent hang on "postfix stop"; doesn't return "terminating on
> Awesome response - thank you very much!
> You have really demystified a lot of what's going on for me.
> I see what you're saying about there being better ways to update the Berkeley
> .db files. It does seem like an upgrade to a less disruptive approach would be
> in order.
> But at the same time, whatever is causing this hanging is probably an
> issue that I should resolve as it could pop up elsewhere. I will take your
> advice and run the gnu debugger next time I get a hang, and report the results.
> I'd like to get to the bottom of this problem, but then I agree it would make
> sense to come up with a better .db update scheme.
> Thanks again
As Victor mentioned, we put in workarounds in Postfix 2.4 for
hanging master processes while logging "terminating on signal".
At the time, master logged "terminating on signal" BEFORE terminating
its child processes (including trivial-rewrite). This is consistent
with the behavior that you observe: no "terminating on signal"
message and no child process termination.
I suspect that you're running an older Postfix version, in which
case the problem will not be fixed. The oldest supported release
is Postfix 2.4.