Summary: | ASTERISK-25436: Segmentation fault relating to JSON, stasis, and fax | ||
Reporter: | Charlie Smurthwaite (catphish) | Labels: | |
Date Opened: | 2015-09-30 08:54:49 | Date Closed: | 2018-02-20 05:43:30.000-0600 |
Priority: | Major | Regression? | |
Status: | Closed/Complete | Components: | Core/Channels Core/ManagerInterface |
Versions: | 13.5.0 | Frequency of Occurrence | |
Related Issues: | |||
Environment: | Linux 3.13.0-63-generic Ububtu 14.04.3 | Attachments: | ( 0) backtrace-13.5.0.txt |
Description: | I observed several crashes under asterisk 13.2. I did not record significant details about these, but instead upgraded to 13.5.0. Today under 13.5.0 I have experienced another crash (a segfault). The following is observed in the log immediately before the crash:
{code:title=Asterisk Log|borderStyle=solid} [2015-09-30 13:43:24] ERROR[6541][C-00000ee1] json.c: Error building JSON from '{s: s, s: s}': Invalid UTF-8 string. [2015-09-30 13:43:24] ERROR[6541][C-00000ee1] stasis_channels.c: Error creating message [2015-09-30 13:43:24] ERROR[6541][C-00000ee1] json.c: Error building JSON from '{s: s, s: s, s: s, s: i, s: i, s: i, s: o}': Invalid UTF-8 string. {code} I will attach a backtrace of this crash. Another instance of this crash (under Asterisk 13.2.0) included the following log entry, suggesting (as the backtrace does) that this crash is related to fax channels: {code:title=Asterisk Log|borderStyle=solid} [2015-09-22 16:44:44] WARNING[2646][C-0000bddf] app_fax.c: Transmission error {code} | ||
Comments: | By: Asterisk Team (asteriskteam) 2015-09-30 08:54:51.583-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. 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: Rusty Newton (rnewton) 2015-10-01 09:30:13.926-0500 [~catphish] can you please provide a full debug log as described here: https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information It is would be nice to have the last few thousand lines before the crash happens. By: Charlie Smurthwaite (catphish) 2015-10-01 09:35:01.302-0500 Unfortunately, I do not have debug logs from this incident, and will not be able to reproduce it at this stage as I have been forced to move my production systems away from v13. I realise this is entirely unhelpful, but I hope the information I have provided so far is in some way useful. By: Corey Farrell (coreyfarrell) 2018-02-20 05:43:30.306-0600 This was resolved by ASTERISK-26466 which added UTF-8 validation to ensure ast_json_pack does not fail for the app_fax.c events. |