| Summary: | ASTERISK-24034: Asterisk restarted with seg fault | ||
| Reporter: | André César de Sá (acsa) | Labels: | |
| Date Opened: | 2014-07-12 12:31:55 | Date Closed: | 2014-07-31 10:40:43 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | |
| Versions: | 11.5.1 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Debian 7.2, Asterisk compiled from Source. Calls are delivered from a E1 PRI to a Sangoma A116DE interface card. WANPIPE Release: 7.0.3 | Attachments: | |
| Description: | Our system was answering 25 calls and had a segmentation fault and restarted.
From the system logs we can't find any issue that could cause this segfault. Logs: From verbose: [Jul 12 16:47:22] VERBOSE[13043][C-0003523c] pbx.c: -- Executing [h@NEW_VOTATION_HANDLER:34] NoOp("DAHDI/i10/913653905-30e0", "---------- registration ended ----------") in new stack [Jul 12 16:47:22] VERBOSE[13043][C-0003523c] pbx.c: -- Executing [h@NEW_VOTATION_HANDLER:35] NoOp("DAHDI/i10/913653905-30e0", "--------------- Hangup ended ") in new stack [Jul 12 16:47:22] VERBOSE[13043][C-0003523c] pbx.c: -- Executing [h@NEW_VOTATION_HANDLER:36] NoOp("DAHDI/i10/913653905-30e0", "") in new stack [Jul 12 16:47:22] VERBOSE[13043][C-0003523c] chan_dahdi.c: -- Hungup 'DAHDI/i10/913653905-30e0' [Jul 12 16:48:28] Asterisk 11.5.1 built by root @ obelix on a x86_64 running Linux on 2013-10-21 09:52:30 UTC [Jul 12 16:48:28] VERBOSE[14179] config.c: == Parsing '/etc/asterisk/asterisk.conf': Found From kernel.log ul 12 16:47:22 obelix kernel: [1472422.955640] asterisk[9140]: segfault at 9f0 ip 0000000000498290 sp 00007fbaa3977a08 error 6 in asterisk[400000+202000] If more information is needed, please feel free to ask. Thank you. Best Regards, //Andre Cesar de Sa | ||
| Comments: | By: Matt Jordan (mjordan) 2014-07-12 16:53:45.854-0500 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: André César de Sá (acsa) 2014-07-14 04:57:31.729-0500 Hello Matt, Thank you for your reply. This system is part of a live production environment that works 24/7. Changing a configuration like DONT_OPTIMIZE at this moment, isn't doable. It has 16 PRI attached. The restarts and segfaults are random and impossible to reproduce. By: Rusty Newton (rnewton) 2014-07-31 10:39:44.915-0500 Thank you for the bug report. However I am unable to reproduce this issue. We are now going to close this report - please feel free to reopen when you have more information at hand. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested. | ||