| Summary: | ASTERISK-26746: pjsip: Repeated segfaults with not responding nameserver | ||||
| Reporter: | Michael Maier (micha) | Labels: | |||
| Date Opened: | 2017-01-24 06:26:00.000-0600 | Date Closed: | 2017-01-24 06:38:52.000-0600 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | pjproject/pjsip | ||
| Versions: | 13.13.1 | Frequency of Occurrence | Constant | ||
| Related Issues: |
| ||||
| Environment: | Centos 6 dual core processor FreePBX 13.0.190.7 | Attachments: | ( 0) backtrace-2017-01-24T08.30.27+0100.txt ( 1) backtrace-2017-01-24T08.51.21+0100.txt ( 2) backtrace-2017-01-24T08.54.06+0100.txt | ||
| Description: | Asterisk was started while DNS was not functional: local named (configured in /etc/resolv.conf) was reachable, but named couldn't resolve any hostnames, because of broken INPUT iptables rules (the answer of the provider DNS was never seen by named). Therefore request timed out.
There have been trunks configured using SRV and not SRV entries. I can't say, which of both types (or even both) caused the segfaults. Unfortunately, no debug was activated at the time the crashes appeared. | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2017-01-24 06:26:01.594-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: Michael Maier (micha) 2017-01-24 06:36:34.701-0600 These are the backtraces of the segfaults. Unfortunately, there is no debug output, but some errors in logfile: [2017-01-24 08:30:17] ERROR[8143] res_pjsip.c: Error 320046 'No working DNS nameserver (PJLIB_UTIL_EDNSNOWORKINGNS)' sending OPTIONS request to endpoint telekomPJSIP [2017-01-24 08:30:17] ERROR[8143] astobj2.c: FRACK!, Failed assertion bad magic number 0x0 for object 0x7f6214011260 (0) [2017-01-24 08:51:13] ERROR[2255] res_pjsip.c: Error 320052 'DNS "Server failure" (PJLIB_UTIL_EDNS_SERVFAIL)' sending OPTIONS request to endpoint telekomPJSIP-xxx [2017-01-24 08:51:13] ERROR[2255] astobj2.c: FRACK!, Failed assertion bad magic number 0x0 for object 0x7f267400a4b0 (0) [2017-01-24 08:53:58] ERROR[4150] res_pjsip.c: Error 320052 'DNS "Server failure" (PJLIB_UTIL_EDNS_SERVFAIL)' sending OPTIONS request to endpoint easybellPJSIP [2017-01-24 08:53:58] ERROR[4150] astobj2.c: FRACK!, Failed assertion bad magic number 0x0 for object 0x7fe0b800b3f0 (0) easybell uses SRV lookups, telekom classical lookups. By: Joshua C. Colp (jcolp) 2017-01-24 06:38:52.546-0600 Closing as same underlying issue as ASTERISK-26679. Please add yourself as a watcher to that issue to see any progress or updates. | ||||