Hi, On Mon, Aug 23, 2010 at 01:34:08PM +0200, XANi wrote: > Dnia 2010-08-23, pon o godzinie 13:11 +0200, Sebastian Harl pisze: > > On Mon, Aug 23, 2010 at 04:02:57AM +0200, XANi wrote: > > > So after running something like: > > > while sleep 30 ; do /etc/init.d/collectd restart; done > > > after some time (sometimes few minutes sometimes an hour or more) i get > > > tons of collectd processes lying around (ive added output of ps aux as > > > attachment) and sometimes after restart. > > […] > > > It seems to trigger when both exec and unixsock plugins are on, if i > > > turn off one of them it works fine. Ah and im using 64 bit debian > > > testing. > > > > Uhm, strange. Could you please check (e.g. using "strace -p <pid>") what > > those collectd processes are doing? What's the parent of those processes > > (PPID in "ps ax -l" or use something like "ps axjf")? Are you able to > > kill those processes using signal SIGINT or SIGTERM?
> Ok so: > -- > # ps ax |grep col > 4792 ? SLsl 0:00 /usr/sbin/collectd > -C /etc/collectd/collectd.conf -P /var/run/collectd.pid > 4800 ? S 0:00 /usr/sbin/collectd > -C /etc/collectd/collectd.conf -P /var/run/collectd.pid > -- > as attachment result of strace -t -ff -o /tmp/4792 -p 4792 and > strace -t -ff -o /tmp/4800 -p 4800 > > parent of PID 4800 is 4792 > 4792 reacts on sigterm, 4800 both SIGTERM and SIGQUIT doesn't work, only > SIGKILL > 4800.4800: > 13:25:33 futex(0x7fe9098f7550, FUTEX_WAIT_PRIVATE, 2, NULL <unfinished ...> Thanks. Looks like some kind of deadlock :-/ I'll look into that. Cheers, Sebastian -- Sebastian "tokkee" Harl +++ GnuPG-ID: 0x8501C7FC +++ http://tokkee.org/ Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin
signature.asc
Description: Digital signature
_______________________________________________ collectd mailing list [email protected] http://mailman.verplant.org/listinfo/collectd
