| Summary: | ASTERISK-29098: pjsip: Crash in pjnath on cache timeout | ||||
| Reporter: | 钟明星 (zmxzmxzmxzmx) | Labels: | webrtc | ||
| Date Opened: | 2020-09-26 21:21:17 | Date Closed: | 2020-11-20 12:00:01.000-0600 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | pjproject/pjsip | ||
| Versions: | 17.6.0 17.8.0 | Frequency of Occurrence | Frequent | ||
| Related Issues: |
| ||||
| Environment: | centos 6.10 | Attachments: | ( 0) bt.txt ( 1) core.alast1-2020-09-26T15-00-47+0800-brief.txt ( 2) core.alast1-2020-09-26T15-00-47+0800-full.txt ( 3) core.alast1-2020-09-26T15-00-47+0800-info.txt ( 4) core.alast1-2020-09-26T15-00-47+0800-locks.txt ( 5) core.alast1-2020-09-26T15-00-47+0800-thread1.txt | ||
| Description: | asterisk Frequency crash
according to https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2020-09-26 21:21:19.313-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. Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/]. By: Joshua C. Colp (jcolp) 2020-09-27 04:53:16.604-0500 Is there a PJSIP install on the system itself? By: 钟明星 (zmxzmxzmxzmx) 2020-09-27 04:58:35.863-0500 compile with --with-pjproject-bundled . ./configure --with-ssl=/usr/local/ssl --with-crypto=/usr/local/ssl --with-srtp=/root/crm64/linux/libsrtp-2.3.0 openssl is OpenSSL 1.1.1g By: Joshua C. Colp (jcolp) 2020-09-28 07:52:54.897-0500 We require additional debug to continue with triage of your issue. Please follow the instructions on the wiki [1] for how to collect debugging information from Asterisk. For expediency, where possible, attach the debug with a '.txt' file extension so that the debug will be usable for further analysis. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information As well - How much WebRTC traffic is being done? What kind of environment? By: 钟明星 (zmxzmxzmxzmx) 2020-09-29 15:09:14.379-0500 environment : I use realtime chan_sip and webrtc by jssip.js . How much WebRTC traffic is being done : about 130 link. I will enable the debug log right now ,thanks! By: Sean Bright (seanbright) 2020-09-29 17:05:53.898-0500 Linked a related Github issue By: 钟明星 (zmxzmxzmxzmx) 2020-09-29 19:41:28.254-0500 I see one patch in the Github issue . Can it work well with the bug? By: Sean Bright (seanbright) 2020-09-29 19:43:56.915-0500 No need to paste the patch here. If someone is interested in it they can look at the Github issue. If you want to try and patch your installation and test, that would be helpful. By: 钟明星 (zmxzmxzmxzmx) 2020-10-07 12:07:03.956-0500 The debug log is too big .. More than 1GB By: Kevin Harwell (kharwell) 2020-10-07 18:09:31.349-0500 [~zmxzmxzmxzmx] Is that debug log compressed? If not try compressing it before attaching. It would also be helpful to filter the log and only include debug output relevant to the issue. Lastly, if you set the debug level really high >10 then try lowering it to something like 5, or 3. Before doing that though, have you tried the patch [~seanbright] mentioned above? If not please try it and see if that fixes the issue. Thanks! By: 钟明星 (zmxzmxzmxzmx) 2020-10-07 23:38:20.013-0500 according to https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information [logfiles] debug_log_123456 => notice,warning,error,debug,verbose,dtmf *CLI> core set verbose 5 *CLI> core set debug 5 *CLI> module reload logger In one day , it will produce more than 2GB~5GB log . How to compress it? Now I only record the debug log and set debug 5 , but it still too big. When the problem occur ,it will past a few days,about 3-4 days,so the log is too big to upload. I had tried the patch,but the bug is not resolved. By: Kevin Harwell (kharwell) 2020-10-08 11:03:43.340-0500 We'd probably only need the last portion of the log during in which time the bug occurred. Also to compress things you can use a "zip" program like GNU zip. By: Asterisk Team (asteriskteam) 2020-10-23 12:00:01.376-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 By: 钟明星 (zmxzmxzmxzmx) 2020-11-02 00:06:53.973-0600 If I enable the debug log, it is too much about 10GB one day . How to reduce it ? And the patch is not resolved . By: Asterisk Team (asteriskteam) 2020-11-02 00:06:54.663-0600 This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable. By: Benjamin Keith Ford (bford) 2020-11-04 12:30:05.144-0600 Unfortunately there's not really a way to reduce the size of the log files produced. If 10GB is too large, you could try just debug logs (not verbose), but ultimately both enabled would be best. As Kevin mentioned, we would probably just need the last portion of the logs. Do you have a log leading up to the crash? It can be compressed into something (like a tar file) and attached here if the file is too large. By: 钟明星 (zmxzmxzmxzmx) 2020-11-06 05:12:53.992-0600 I want to confirm one thing. When the asterisk crash,the debug log file can auto to produce a new one? If so, I can use "tail " command to the old debug log file to give you what you want . Now I got a new patch in github ,I will try it . By: Benjamin Keith Ford (bford) 2020-11-06 09:59:03.339-0600 When it crashes, you'll want to use the most recent debug file. This should have the information in it that's relevant to the crash. You may want to consider having your logs rotate to reduce the size of each individual log file. That way, when too many build up, you can remove the older ones to make room for the new ones leading up to the crash. By: Asterisk Team (asteriskteam) 2020-11-20 12:00:00.975-0600 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 | ||||