Corey Edwards writes:
Just last night it started issuing these messages:
Oct 7 16:23:32 imap1 authdaemond.ldap: authdaemon: modules="authldap", daemons=40 Oct 7 16:28:55 imap2 authdaemond.ldap: authdaemon: modules="authldap", daemons=40
And they've been continuing about every hour since. Sometimes they skip an hour, but they don't ever occur more frequently than that. Sometimes it's both imap1 and imap2, and sometimes just one of them.
Looking at the process table I see 40 of these:
UID PID PPID C STIME TTY TIME CMD root 2312 233 0 16:28 ? 00:00:00 /usr/lib/courier/authlib/authdaemond.ldap start
And the parent, 233, looks like this:
UID PID PPID C STIME TTY TIME CMD root 233 1 0 Aug02 ? 00:00:00 /usr/lib/courier/authlib/authdaemond.ldap start
The parent has been running for over two months but has decided that it needs to restart all of its children. What would cause this behavior?
One of the child process is crashing, and the parent restarts it.
I'm not aware of any LDAP outages, but could that be the culprit?
Put an strace on every one of these 40 child processes of the parent authdaemond.ldap. Find out why it's crashing.
pgpdcK0qzHseu.pgp
Description: PGP signature
