ASTERISK-23194: Segfault when loading module func

[Home]

Summary: ASTERISK-23194: Segfault when loading module func_enum

Reporter: Matteo (mpiazzatnetbug) Labels:

Date Opened: 2014-01-28 03:45:44.000-0600 Date Closed: 2014-02-13 11:57:26.000-0600

Priority: Major Regression?

Status: Closed/Complete Components: Resources/res_xmpp

Versions: 11.6.1 Frequency of
Occurrence Frequent

Related
Issues:

Environment: Debian 6.0.8 running on PROXMOX 3.x Attachments: ( 0) backtrace.txt

Description: Asterisk crash.
Jan 28 10:26:32 asterisk-cen-3 kernel: [4585685.452972] asterisk[24509]: segfault at 10c ip b77d66a3 sp bf82401c error 4 in ld-2.11.3.so[b77c0000+1b000]

The machine is installed in a test enviroment. We have three asterisk sharing the device state with xmpp protocol (we are using a tigase server).

The machine are doing nothing (no load) only sharing the device state. After some minutes asterisk goes in segfault. I can reproduce the issue in both machines. So it will be easy to make more test and excute some debug if someone drive me.

As attachment you will find the backtrace file.

Comments: By: Matteo (mpiazzatnetbug) 2014-01-28 10:09:48.683-0600

I have no idea if can help. The hostname of the machine is not resolved by the dns and is not define into /etc/hosts file.

By: Rusty Newton (rnewton) 2014-01-28 17:29:30.501-0600

Please provide minimal configuration files with a configuration that reproduces the issue. Attach them to the issue in .txt format.

Additionally, if you can provide Asterisk debug logs demonstrating the issue as is within your environment that would be extremely helpful. That is, a log captured showing what is going on up until the time of the crash. Please gather logs following the instructions here: https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information

You might gather one log without DEBUG type messages, and one with DEBUG type messages turned up to level 5.

If possible, also install debugging symbols/devel packages for the objects showing "in ?? () from" within your trace, and then get a new trace so that the developers will have further information.

Thanks!

By: Rusty Newton (rnewton) 2014-02-13 11:57:05.916-0600

We are unable to reproduce this issue. There has been no response in a few weeks, so we'll close this out until you are able to provide further debug. Contact a bug marshal in #asterisk-bugs or #asterisk-dev on irc.freenode.net to get the issue re-opened.