[asterisk-bugs] [JIRA] (ASTERISK-22540) WARNING[2324] asterisk.c: Fork failed: Cannot allocate memory in /var/log/asterisk/messages then segfault

Matt Jordan (JIRA) noreply at issues.asterisk.org
Tue Sep 24 13:08:03 CDT 2013


    [ https://issues.asterisk.org/jira/browse/ASTERISK-22540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210535#comment-210535 ] 

Matt Jordan commented on ASTERISK-22540:
----------------------------------------

{quote}
This is a really service affecting problem, so if there is anything I can do to move this forward then I need to know what that is.
*CLI> core show uptime
System uptime: 7 minutes, 19 seconds
Last reload: 7 minutes, 19 seconds
And went from 0.9% ram to 63.8%.
No reloads and only 1 outgoing call was placed.

The memory leak happens when the system is idle.
{quote}

Since you were also testing the log system changes for remote consoles, I have a feeling you ran smack into ASTERISK-22560. I'm guessing that with the system updates, you also updated Asterisk to the latest SVN?

If not, definitely grab the patch for commit 399513 and apply it to your system:

{noformat}
svn diff -c 399513 https://origsvn.digium.com/svn/asterisk/branches/11
{noformat}

                
> WARNING[2324] asterisk.c: Fork failed: Cannot allocate memory in /var/log/asterisk/messages then segfault
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-22540
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22540
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: General
>    Affects Versions: 11.5.1
>         Environment: SVN r398885
>            Reporter: David Brillert
>         Attachments: gdb-c core asterisk.txt, messages.rar, valgrind.rar
>
>
> Asterisk eats memory until it crashes.
> Attached valgrind log and bt full from core file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list