| Summary: | ASTERISK-12121: Asterisk crashes when switch => Realtime/@ is specified in the head of a context | ||
| Reporter: | Nitzan Kon (nitzan) | Labels: | |
| Date Opened: | 2008-05-31 04:15:44 | Date Closed: | 2011-06-07 14:01:00 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | Addons/res_config_mysql |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | I'm not sure if this is a known issue or not, but we had to find it the hard way- we added some "hard" extensions to a context which had switch => Realtime/@ before those extensions (we around 20 extensions after the switch). It was working perfectly when we had 15 or so extensions, maybe less. But after adding a few more Asterisk crashed and would not start. Seg Fault all the way. It kept dying right after the switch and after successfully loading a couple of post-switch extensions. It almost seems like the switch and hard config are competing with each other and will work OK as long as the hard config can "win" and finish before the switch is loaded. ****** ADDITIONAL INFORMATION ****** A workaround we had was to bring asterisk up when the database is down, then bring the database up. This also makes me think that the hard config and realtime are competing and somehow creating a seg fault. | ||
| Comments: | By: Russell Bryant (russell) 2008-06-01 19:51:43 Can you provide the configuration that you used to cause the crash? Also, can you also provide a backtrace? To do so, compile Asterisk with DONT_OPTIMIZE turned on. Then, start asterisk with the -g option. After the crash, there should be a core dump. # gdb /usr/sbin/asterisk /path/to/core.12345 (gdb) bt (gdb) bt full By: Tilghman Lesher (tilghman) 2008-06-16 11:02:28 nitzan: we need more information from you to pursue this report. By: Tilghman Lesher (tilghman) 2008-06-27 15:08:59 No response from reporter. Please reopen if you're able to provide the requested information. If you are unable to reopen this issue, please contact one of the bug marshals in #asterisk-bugs on Freenode. | ||