| Summary: | ASTERISK-24708: Unable to connect to the asterisk CLI and after a while asterisk creates a core dump | ||
| Reporter: | Willem Ankersmit (WillemAnkersmit) | Labels: | |
| Date Opened: | 2015-01-21 12:33:52.000-0600 | Date Closed: | 2015-02-25 08:56:30.000-0600 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | |
| Versions: | 11.6.0 | Frequency of Occurrence | Occasional |
| Related Issues: | |||
| Environment: | Centos 5.10. Running asterisk 11.6 | Attachments: | |
| Description: | Unable to connect to the asterisk CLI and after a while asterisk creates a core dump. The following error can e seen while tailing the logs
[Jan 21 18:16:01] WARNING[27588] asterisk.c: No more connections allowed [Jan 21 18:16:01] WARNING[27588] asterisk.c: No more connections allowed [Jan 21 18:16:01] WARNING[27588] asterisk.c: No more connections allowed No more sip registrations allowed either | ||
| Comments: | By: Matt Jordan (mjordan) 2015-01-22 08:25:19.012-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 Note that if Asterisk is in a state where it is crashing, then the inability to connect a CLI is a symptom of a much larger problem. By: Rusty Newton (rnewton) 2015-02-10 16:47:44.151-0600 Willem, we haven't heard from you for a couple weeks. Let us know if you can't provide further debug and we'll close this out. By: Rusty Newton (rnewton) 2015-02-25 08:56:11.601-0600 Suspended due to lack of activity. 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. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1]. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines | ||