Segmentation fault on Elastix 1.0

Discussion in 'General' started by vicsanca, Apr 18, 2008.

  1. vicsanca

    Joined:
    Feb 28, 2008
    Messages:
    27
    Likes Received:
    0
    Elastix 1.0 with all updates availables at 17/04/2008

    Code:
    /usr/sbin/safe_asterisk: line 117:  3525 Segmentation fault      (core dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS} >&/dev/${TTY} </dev/${TTY}
    Asterisk ended with exit status 139
    Asterisk exited on signal 11.
    Automatically restarting Asterisk.
    mpg123: no process killed
    
    This happens in a new installation without doing nothing strange with configuration. Only some sip extensions using TE121. I have read that asterisk could crash reloading configuration but this is not the case unless asterisk reloads alone.
    Why?<br><br>Post edited by: vicsanca, at: 2008/04/17 19:09
     
  2. vicsanca

    Joined:
    Feb 28, 2008
    Messages:
    27
    Likes Received:
    0
  3. vicsanca

    Joined:
    Feb 28, 2008
    Messages:
    27
    Likes Received:
    0
    Still having segmentation faults.

    /usr/sbin/safe_asterisk: line 117: 9266 Segmentation fault (core dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS} >&/dev/${TTY} </dev/${TTY}


    Could someone help me?
     
  4. chrisbryant

    Joined:
    Apr 25, 2008
    Messages:
    8
    Likes Received:
    0
    I saw the same Segfault error once as well, running Asterisk 1.4 and FreePBX 2.4 and Elastix 1.0. I'm not sure what was going one at the time (I think I was testing some extension features) but if it happens more I'll post back with more details.
     
  5. vicsanca

    Joined:
    Feb 28, 2008
    Messages:
    27
    Likes Received:
    0
    Removing jbenable=yes from zapata.conf seems to stabilize the system. No coredumps in the last 6 hours.
     
  6. lek

    lek Guest

    Please, update your box. There is a new asterisk version (1.4.19) in the repos.
     

Share This Page