| Summary: | ASTERISK-18846: Asterisk crash on issuing Asterisk-CLI 'reload' command multiple times | ||||
| Reporter: | Abhishek Naidu (abhishek.naidu@gs.com) | Labels: | |||
| Date Opened: | 2011-11-10 00:40:05.000-0600 | Date Closed: | 2011-12-20 09:01:34.000-0600 | ||
| Priority: | Major | Regression? | No | ||
| Status: | Closed/Complete | Components: | Core/General | ||
| Versions: | 1.8.4 | Frequency of Occurrence | Frequent | ||
| Related Issues: |
| ||||
| Environment: | Red Hat Linux 5.5.2 64 bit | Attachments: | ( 0) backtrace.txt ( 1) backtrace-1.txt ( 2) gdb.txt ( 3) reload.txt | ||
| Description: | Asterisk source 1.8.4.3 (release version) is downloaded from Asterisk.org and compiled on Red Hat Linux 5.5.2 64 bit Asterisk is then started After manually updating the configuration files given below, 'reload' command is issued on CLI. We get the following error: WARNING[5043]: cli.c:2013 __ast_cli_unregister: Can't remove command that is in use On executing 'reload' again without any change in configuration, Asterisk crashes Following Asterisk configuratin files are present in /etc/asterisk syslog.conf sip.conf rtp.conf res_snmp.conf modules.conf manager.conf logger.conf indications.conf extensions.conf cli_permissions.conf cli.conf cli_aliases.conf cdr_custom.conf cdr.conf asterisk.conf Thanks a million for you support! | ||||
| Comments: | By: Abhishek Naidu (abhishek.naidu@gs.com) 2011-11-10 00:46:29.396-0600 Here are the backtrace files backtrace.txt generated with command: gdb -se "asterisk" -ex "bt full" -ex "thread apply all bt" --batch -c core.nytadla01.ny.fw.gs.com-2011-11-09T13\:38\:14-0500 > backtrace.txt backtrace-1.txt and gdb.txt generated with command: gdb -se "asterisk" -c core.nytadla01.ny.fw.gs.com-2011-11-09T13\:38\:14-0500 | tee backtrace-1.txt reload.txt is the Asterisk CLI output before the crash By: Matt Jordan (mjordan) 2011-11-30 13:27:28.233-0600 Can you retest with the latest from the 1.8 branch to see if it has this same problem? Some fixes have gone into chan_sip since 1.8.4.1 that may address this. By: Abhishek Naidu (abhishek.naidu@gs.com) 2011-12-01 08:14:34.142-0600 I have installed the latest Asterisk 1.8.7. I will let you know if i see the observation in this version Thanks for your time! By: Jonathan Rose (jrose) 2011-12-08 15:39:07.061-0600 If you can, please elaborate on this by some time next week. I'm eager to hear if this is still a problem. By: Jonathan Rose (jrose) 2011-12-19 15:55:49.991-0600 Please respond by Friday or this issue will be closed with the assumption the assumption that you would have brought any failures to our attention if they had been happening. By: Abhishek Naidu (abhishek.naidu@gs.com) 2011-12-19 23:24:09.863-0600 Thank you for the analysis I havent seen the problem since upgrading to 1.8.7 By: Jonathan Rose (jrose) 2011-12-20 08:59:03.345-0600 Awesome, thanks for the feedback. By: Jonathan Rose (jrose) 2011-12-20 09:01:34.892-0600 Closing: Appears to have already been fixed at some point when testing with 1.8.7 | ||||