|Main Archive Page > Month Archives > postfix-users archives|
> 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 underlying
> 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.