[Home]

Summary:ASTERISK-24770: Astersk segfault when reload SNMP service
Reporter:Ingenierie (ingenierie)Labels:
Date Opened:2015-02-09 09:05:37.000-0600Date Closed:2015-03-09 11:17:54
Priority:MajorRegression?
Status:Closed/CompleteComponents:Resources/res_snmp
Versions:13.1.0 Frequency of
Occurrence		One Time
Related
Issues:
Environment:CentOS release 5.9 Kernel 2.6.18-348.2.1 x86_64Attachments:( 0) v13.1.0_snmp_segfault_backtrace.txt
Description:Hello,

I made the running snmpd service reload the configuration and asterisk service did a segfault :
{noformat}
Feb  6 14:23:22 * snmpd[30214]: accepted smux peer: oid SNMPv2-SMI::enterprises.674.10892.1, descr Systems Management SNMP MIB Plug-in Manager
Feb  6 14:23:34 * snmptrapd[15848]: NET-SNMP version 5.3.2.2 AgentX subagent connected
Feb  6 14:23:34 * kernel: asterisk[17188]: segfault at 0000026708000000 rip 0000003cfe073f56 rsp 00002ae71685a720 error 6
{noformat}

I can give backtrace if I am allowed to.

Regards,
Comments:By: Matt Jordan (mjordan) 2015-02-09 10:41:22.398-0600

Thank you for your bug report. In order to move your issue forward, we require a backtrace[1] from the core file produced after the crash. Also, be sure you have DONT_OPTIMIZE enabled in menuselect within the Compiler Flags section, then:

make install

After enabling, reproduce the crash, and then execute the backtrace[1] instructions. When complete, attach that file to this issue report.

[1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace


By: Ingenierie (ingenierie) 2015-02-10 02:00:08.016-0600

Hello,

Here is the backtrace from the core file produced after the crash. How can I know if DONT_OPTIMIZE flag was enabled ?

Regards,
By: Ingenierie (ingenierie) 2015-02-10 09:23:57.402-0600

Hello,

Here is the backtrace from the core file produced after the crash. How can I know if DONT_OPTIMIZE flag was enabled ?

Regards,

By: Matt Jordan (mjordan) 2015-02-16 11:33:07.463-0600

# First, the backtrace was not generated using the instructions that were linked. Please use the wiki page instructions for generating a proper backtrace.
# You will know if DONT_OPTIMIZE was enabled by looking at menuselect. In your trace, it does not appear as if it was.
# The fact that this is dying in {{malloc}} (from what we can see in the backtrace) may mean this is a memory corruption. You may need to test with valgrind as well.
By: Ingenierie (ingenierie) 2015-02-17 02:54:17.785-0600

I understand that but I can't reproduce this problem in lab. This segfault had happen in a production environment. I activated DONTOPTIMIZE flags for the next time.
By: Rusty Newton (rnewton) 2015-02-20 12:36:58.044-0600

I'm going to put this issue into Waiting for Feedback until you can get further debug as requested. Be sure to use "Send Back" or "Enter Feedback" to make sure the issue comes back to us in a timely fashion. Thanks.
By: Rusty Newton (rnewton) 2015-03-06 16:02:15.168-0600

Has the issue occurred again? Do you have the requested data?

If not we'll close this out and if the issue happens again then we can re-open the issue.
By: Ingenierie (ingenierie) 2015-03-09 06:03:47.962-0500

This issue did not happen later. You close this case.