| Summary: | ASTERISK-28998: Segfault in pj/timer.c | ||
| Reporter: | Gregory Massel (gmza) | Labels: | |
| Date Opened: | 2020-07-21 08:46:07 | Date Closed: | 2020-08-04 12:00:01 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | pjproject/pjsip |
| Versions: | 16.11.1 | Frequency of Occurrence | Frequent |
| Related Issues: | |||
| Environment: | Ubuntu 18.04.4 LTS, kernel 5.3.0-62-generic, Asterisk 16.11.1 | Attachments: | ( 0) backtraces.tgz |
| Description: | Repeated, erratic unprovoked segfaults.
The backtraces all seem to show a similar pattern. Occurs on average daily, although it has sometimes gone days at a time without happening and sometimes multiple times within a single day. | ||
| Comments: | By: Asterisk Team (asteriskteam) 2020-07-21 08:46:10.500-0500 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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. 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]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. By: Gregory Massel (gmza) 2020-07-21 08:47:09.952-0500 Please find attached six different backtraces of the same issue. By: Joshua C. Colp (jcolp) 2020-07-21 08:59:58.304-0500 Please upgrade to Asterisk 16.12.0. This includes the latest version of PJSIP which has a major refactor of timer support to resolve these problems. Others have reported no more timer crashes after doing the upgrade. By: Gregory Massel (gmza) 2020-07-21 09:01:44.973-0500 The system has 24,215 PJSIP endpoints. Originally it was handling inbound registration, MWI and BLF subscriptions for 22,352 of these and qualifying them all every 60 seconds. A couple of days ago I offloaded all the inbound registration, OPTIONS (qualify) and BLF to OpenSIPS and changed all the PJSIP aors to statically point the the OpenSIPS proxy and disabled qualification (OPTIONS). With this, I also bypassed by far the bulk of the media (RTP) handling off Asterisk. Despite that dramatic reduction of workload on the Asterisk box, it still segfaulted again today in the exact same manner as it had done the previous five times. This would indicate to me that the issue is not load related and appears to be in the core of PJSIP (call handling) not in secondary functionality (e.g. qualification, presence, registration, etc.) MWI is still in Asterisk, however, looking at the backtrace, I don't see any indication that it relates to MWI. Looking at the timing, it is possible - although pure speculation - that this particular problem has started since upgrading to 16.11.1, however, I do have multiple other Asterisk systems running 16.11.1 and have not experienced similar issues with them. By: Gregory Massel (gmza) 2020-07-21 09:02:07.209-0500 Thank you; I will try upgrade now. By: Asterisk Team (asteriskteam) 2020-08-04 12:00:00.831-0500 Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. 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 | ||