[Home]

Summary:ASTERISK-25747: Crash on "restart when convenient"
Reporter:Michaƫl Arnauts (michaelarnauts)Labels:
Date Opened:2016-02-05 03:00:08.000-0600Date Closed:2016-02-05 06:03:09.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:Core/General
Versions:11.6.0 Frequency of
Occurrence
One Time
Related
Issues:
Environment:Ubuntu 12.04.5 LTSAttachments:
Description:Asterisk crashed when I did a "core restart when convenient".

root@bru3-trunk:/tmp/crash# gdb asterisk CoreDump
GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2.1) 7.4-2012.04
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.launchpad.net/gdb-linaro/>...
Reading symbols from /usr/sbin/asterisk...done.
[New LWP 15250]
[New LWP 9829]
[New LWP 16127]
[New LWP 9835]
[New LWP 9842]
[New LWP 10383]
[New LWP 9838]
[New LWP 9831]
[New LWP 9840]
[New LWP 9841]
[New LWP 9847]
[New LWP 9846]
[New LWP 9849]
[New LWP 9848]
[New LWP 9844]
[New LWP 9839]
[New LWP 9833]
[New LWP 9832]
[New LWP 9843]

warning: Can't read pathname for load map: Input/output error.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff67952000
Core was generated by `/usr/sbin/asterisk -U asterisk -G asterisk'.
Program terminated with signal 11, Segmentation fault.
#0  0x00007f4201d16f60 in pthread_kill () from /lib/x86_64-linux-gnu/libpthread.so.0
(gdb) bt
#0  0x00007f4201d16f60 in pthread_kill () from /lib/x86_64-linux-gnu/libpthread.so.0
#1  0x00007f41e8b0878c in unload_module () at chan_sip.c:34681
#2  0x00000000004f404a in ast_module_shutdown () at loader.c:528
#3  0x0000000000425835 in really_quit (num=0, niceness=<optimized out>, restart=1) at asterisk.c:1807
#4  0x0000000000443d6f in quit_handler (restart=1, niceness=SHUTDOWN_REALLY_NICE, num=<optimized out>) at asterisk.c:1725
#5  handle_restart_when_convenient (a=<optimized out>, e=<optimized out>, cmd=<optimized out>) at asterisk.c:2299
#6  handle_restart_when_convenient (e=<optimized out>, cmd=<optimized out>, a=<optimized out>) at asterisk.c:2283
#7  0x0000000000498837 in ast_cli_command_full (uid=0, gid=1001, fd=13, s=0x7f41d16e5700 "core restart when convenient") at cli.c:2691
#8  0x0000000000498a85 in ast_cli_command_multiple_full (uid=0, gid=1001, fd=13, size=29, s=0x7f41d16e59af "core restart when convenient") at cli.c:2714
#9  0x00000000004433f2 in netconsole (vconsole=0x8493c0) at asterisk.c:1367
#10 0x0000000000577e57 in dummy_start (data=<optimized out>) at utils.c:1162
#11 0x00007f4201d11e9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#12 0x00007f4202e5638d in clone () from /lib/x86_64-linux-gnu/libc.so.6
#13 0x0000000000000000 in ?? ()
(gdb) quit
Comments:By: Asterisk Team (asteriskteam) 2016-02-05 03:00:10.490-0600

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

By: Joshua C. Colp (jcolp) 2016-02-05 06:02:55.158-0600

It appears the bug you have submitted is against a rather old version of a supported branch of Asterisk. There have been many issues fixed between the version you are using and the current version of your branch. Please test with the latest version in your Asterisk branch and report whether the issue persists.

Please see the Asterisk Versions [1] wiki page for info on which versions of Asterisk are supported.
[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions