|Summary:||ASTERISK-14931: Asterisk forks processes then locks up|
|Reporter:||Alistair Cunningham (acunningham)||Labels:|
|Date Opened:||2009-10-02 10:39:58||Date Closed:||2009-10-23 10:10:05|
|Description:||One particular Asterisk 184.108.40.206 machine occasionally forks off some child processes, goes to 100% CPU, and stops responding to calls and the console, and stops logging. During this time:|
test:~# ps -ef | grep asterisk | grep -v grep
root 4830 1 0 Sep07 ? 00:00:00 /bin/sh /usr/sbin/safe_asterisk -U enswitch -G enswitch
enswitch 25822 4830 55 Sep29 ? 1-16:05:51 /usr/sbin/asterisk -U enswitch -G enswitch -vvvg -c
enswitch 16080 25822 0 09:33 ? 00:00:00 [asterisk] <defunct>
enswitch 27846 25822 0 14:59 ? 00:00:00 [asterisk] <defunct>
enswitch 12656 25822 99 17:09 ? 00:19:04 /usr/sbin/asterisk -U enswitch -G enswitch -vvvg -c
The "top" command shows that both process 25822 and 12656 are using 100% CPU time.
Killing the processes and having safe_asterisk restart Asterisk fixes the problem in the short term.
Any ideas on how to debug this?
|Comments:||By: Leif Madsen (lmadsen) 2009-10-02 13:08:32|
Are you using SIP realtime?
By: Alistair Cunningham (acunningham) 2009-10-02 14:29:18
Yes, sippeers but not sipusers.
By: Leif Madsen (lmadsen) 2009-10-05 11:59:13
I think this is related, or a duplicate of, recently fixed 14309. Can you try the latest 1.4 branch and determine if your issue is resolved by the fix? Thanks!
By: Alistair Cunningham (acunningham) 2009-10-07 09:35:46
The owner of the system affected isn't happy about using subversion revisions. Let's wait for 1.4.27.
By: Leif Madsen (lmadsen) 2009-10-20 08:45:46
OK, I'm going to mark this as closed for now. Please reopen if the issue continues to present itself in 1.4.27. Thanks!