RE: "opendkim dead but subsys locked" yet there are opendkim processes

From: Murray S. Kucherawy <msk_at_blackops.org>
Date: Thu, 17 Jan 2013 12:52:34 -0800 (PST)

On Thu, 17 Jan 2013, Tracy Wise wrote:
> So, from my very limited knowledge, it appears that opendkim did indeed
> bind to that port, not another process.  Or am I wrong on that?  

In that case it looks like there's an opendkim up and providing service,
but there's also another one trying (and failing) to start up on the same
port, and that's caught in a restart loop. Since you tried a reboot, it
looks like your startup environment is starting opendkim twice; the first
one works, the second one enters a restart loop.

Since AutoRestartRate is set to 10/1h, then I'm left to conclude that the
second opendkim instance will give up after ten quick retries (or at
least, it should). The parent will then terminate. That you have 30Gb of
logs in one case suggests that there's something watching even the parent
and restarting it, which is where the loop really comes from. This could
be Plesk, but that's merely a guess since I've never used it.

Focusing for a moment on the opendkim that is up and listening on 8891,
your postfix instance should be talking to it and getting mail signed
outbound. Is either postfix or opendkim logging anything that might
explain why it's not allowing mail to depart?

-MSK
Received on Thu Jan 17 2013 - 20:52:53 PST