| Summary: | ASTERISK-27401: Random crashs during the automatic calendars refresh | ||
| Reporter: | Benoît Dereck-Tricot (krells) | Labels: | |
| Date Opened: | 2017-11-07 09:30:38.000-0600 | Date Closed: | 2020-01-14 11:13:54.000-0600 |
| Priority: | Major | Regression? | Yes |
| Status: | Closed/Complete | Components: | Resources/res_calendar |
| Versions: | 13.18.0 | Frequency of Occurrence | Frequent |
| Related Issues: | |||
| Environment: | SMP Debian 4.9.51-1 (2017-09-28) x86_64 GNU/Linux | Attachments: | ( 0) core-brief.txt ( 1) core-full.txt ( 2) core-thread1.txt |
| Description: | Hello, we are having random crashes on all of our servers.
According to the backtrace from the core dump, it is happening during a do_refresh in the calendar module. While most of the crashes happened at midnight, there are exceptions (with similar backtraces) I tried to find a way to reproduce the crash, playing with timedatectl to loop back just before midnight every few seconds and forcing the calendars to reload at the same time, with litte success : I could only get a crash on purpose once... I think I can use some help :) | ||
| Comments: | By: Asterisk Team (asteriskteam) 2017-11-07 09:30:39.212-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: Benoît Dereck-Tricot (krells) 2017-11-07 10:10:24.007-0600 the ast_coredumper files By: George Joseph (gjoseph) 2017-11-08 08:51:08.275-0600 It looks like the event owner is NULL by the time the event is actually run. We can prevent the crash by checking for the NULL but we also need to figure out why it's NULL in the first place. Please run with "core set debug 5 res_calendar.so" and "core set debug 5 res_calendar_???.so" where "???" is whichever implementation you're using and attach the debug output to this issue. That should give us more info. By: Asterisk Team (asteriskteam) 2017-11-22 12:00:01.121-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 | ||