[Home]

Summary:ASTERISK-24684: crash during sip reload
Reporter:Peter Katzmann (pk16208)Labels:
Date Opened:2015-01-14 08:42:44.000-0600Date Closed:2018-01-02 08:44:18.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:Channels/chan_sip/General
Versions:11.15.0 Frequency of
Occurrence
Frequent
Related
Issues:
is duplicated byASTERISK-24690 crash during sip reload
is related toASTERISK-24683 Crash in PBX ast_hashtab_lookup_internal during core restart now
Environment:ubuntu preciseAttachments:( 0) backtrace-cn.txt
( 1) crash.txt
Description:Occasional segfault during sip reload or core restart now

Comments:By: Matt Jordan (mjordan) 2015-01-14 09:25:51.938-0600

Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description did not include enough information. You may find it helpful to read the Asterisk Issue Guidelines http://www.asterisk.org/developers/bug-guidelines. We would be grateful if you would then provide a more complete description of the problem. At a minimum, we need:

1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).

This likely includes output from the console with debug level logging, a SIP trace (if this is SIP related), and configuration information such as dialplan (e.g. extensions.conf) and channel configuration (e.g. sip.conf). Thanks!



By: Peter Katzmann (pk16208) 2015-01-14 09:34:52.073-0600

Sorry,
attachement missed. Please reopen

By: Michael L. Young (elguero) 2015-01-15 07:16:18.681-0600

This stood out to me:

{quote}
full:[Jan 14 01:00:01] WARNING[4539] db.c: Couldn't bind key to stmt: out of memory
{quote}

You might want to check into your memory issues?

By: Peter Katzmann (pk16208) 2015-01-15 07:48:34.094-0600

I looked through the logfiles, because my 2 reports are from 2 different server (hw) with different asterisk versions.
What i found on this one is the following in the server logs. I know this is not ok, but probably could lead to the problem ?
Jan 14 00:59:48 lnx32-asterisk1 snmpd[1309]: Connection from Uarisk -rx 'core restart now')
Jan 14 01:00:01 lnx32-asterisk1 CRON[5059]: (root) CMD (/usr/sbin/rasterisk -rx 'sip reload')
Jan 14 01:00:01 lnx32-asterisk1 CRON[5058]: (root) CMD (/usr/local/bin/sip_check_status.sh)
Jan 14 01:00:01 lnx32-asterisk1 CRON[5054]: (CRON) info (No MTA installed, discarding output)
Jan 14 01:00:01 lnx32-asterisk1 kernel: [ 3487.760182] show_signal_msg: 39 callbacks suppressed
Jan 14 01:00:01 lnx32-asterisk1 kernel: [ 3487.760186] asterisk[4539]: segfault at 0 ip 0810d410 sp b3f55220 error 4 in asterisk[8048000+1cc000]

By: Joshua C. Colp (jcolp) 2017-12-18 09:17:09.768-0600

Based on the comment by [~elguero] did you look into anything in regards to memory usage and uncover anything?

By: Asterisk Team (asteriskteam) 2018-01-02 08:44:18.845-0600

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines