RE: thread leakage

From: Andreas Schulze <sca_at_andreasschulze.de>
Date: Mon, 14 Mar 2011 10:55:29 +0100 (CET)

Hi,

I think I have a thread problem too.
produktionsystem, opendkim-2.3.0

log:Mar 12 22:06:22 idvmailin04 opendkim[5699]: OpenDKIM Filter:
thread_create() failed: 11, try again
Mar 12 22:10:09 idvmailin04 opendkim[5699]: OpenDKIM Filter:
thread_create() failed: 11, try again
Mar 12 22:10:43 idvmailin04 opendkim[5699]: OpenDKIM Filter:
thread_create() failed: 11, try again
Mar 12 22:14:57 idvmailin04 opendkim[5699]: OpenDKIM Filter:
thread_create() failed: 11, try again
Mar 12 22:16:16 idvmailin04 opendkim[5699]: OpenDKIM Filter:
thread_create() failed: 11, try again
Mar 12 22:17:00 idvmailin04 opendkim[5699]: OpenDKIM Filter:
thread_create() failed: 11, try again
Mar 12 22:22:06 idvmailin04 opendkim[5699]: OpenDKIM Filter:
thread_create() failed: 11, try again
Mar 12 22:22:13 idvmailin04 opendkim[5699]: OpenDKIM Filter:
thread_create() failed: 11, try again
Mar 12 22:23:04 idvmailin04 opendkim[5699]: OpenDKIM Filter:
thread_create() failed: 11, try again
Mar 12 22:23:13 idvmailin04 opendkim[5699]: OpenDKIM Filter:
thread_create() failed: 11, try again
Mar 12 22:28:48 idvmailin04 opendkim[5699]: OpenDKIM Filter:
thread_create() failed: 11, try again
Mar 12 22:29:53 idvmailin04 opendkim[5699]: OpenDKIM Filter:
thread_create() failed: 11, try again
Mar 12 22:31:08 idvmailin04 opendkim[5699]: OpenDKIM Filter:
thread_create() failed: 11, try again
Mar 12 22:31:21 idvmailin04 opendkim[5699]: OpenDKIM Filter:
thread_create() failed: 11, try again
Mar 12 22:31:35 idvmailin04 opendkim[5699]: OpenDKIM Filter:
thread_create() failed: 11, try again
Mar 12 22:37:27 idvmailin04 opendkim[5699]: OpenDKIM Filter:
thread_create() failed: 11, abort
Mar 12 22:37:43 idvmailin04 opendkim[5699]: OpenDKIM Filter v2.3.0
terminating with status -1, errno = 11

...
problem noticed and SIGKILL
...

Mar 14 10:23:41 idvmailin04 opendkim[25462]: OpenDKIM Filter v2.3.0
starting (args: -x /etc/opendkim/opendkim.conf)

I run opendkim supervised ( Background no in o.conf )
But process 5699 did not realy terminate. It hung arround.

ls -la /proc/5699/tasks | wc -l -> 202
It did not respond to a SIGTERM. After SIGKILL the process was really dead
and restarted by the supervisor.

> Are you able to attach to the process when it's leaked some threads and
> get a dump of all the thread stacks? This would show where the threads
> are being created (i.e. if it's libmilter, opendkim or unbound) and
> indicate where and why they're stuck.

How do I do this in deatail ?
do I need a binary with debug-symbols ?

-- 
Viele Gre
Andreas Schulze
Received on Mon Mar 14 2011 - 09:55:47 PST

This archive was generated by hypermail 2.3.0 : Mon Oct 29 2012 - 23:33:09 PST