[Home]

Summary:ASTERISK-29400: ***CLI> *** stack smashing detected ***: <unknown> terminated**
Reporter:rahul kathet (rahulkathet)Labels:webrtc
Date Opened:2021-04-20 04:18:32Date Closed:2021-05-25 12:00:01
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Resources/res_http_websocket
Versions:16.15.1 Frequency of
Occurrence
Occasional
Related
Issues:
Environment:Attachments:
Description:This issue doesnt come always.
Whenever I tried to connect asterisk using wss connection asterisk is getting crashed.

***CLI> *** stack smashing detected ***: <unknown> terminated**

As soon as I refresh my web page to connect webrtc asterisk stopped. But this is not happening when connecting using linphone or zoiper.
Comments:By: Asterisk Team (asteriskteam) 2021-04-20 04:18:33.937-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) 2021-04-20 04:23:53.616-0500

Thank you for the crash report. However, we need more information to investigate the crash. Please provide:

1. A backtrace generated from a core dump using the instructions provided on the Asterisk wiki [1].
2. Specific steps taken that lead to the crash.
3. All configuration information necesary to reproduce the crash.

Thanks!

[1]: https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace

Additionally, what channel driver is in use for SIP?

Is there anything additional in the Asterisk logs?

What Linux distribution and system is this running on?

Does this happen on Asterisk 18 as well?

By: rahul kathet (rahulkathet) 2021-04-27 00:29:21.514-0500

As this problem is not constant, I will generate core dump and whenever it happen will share the details.
My system is live so I cannot switch on/off evertime because they have been used by agents.

By: rahul kathet (rahulkathet) 2021-04-30 15:13:17.555-0500

I have enabled my debug and found this whenever I tried to start my node ARI asterisk start crashing.

[2021-04-30 22:12:01] DEBUG[22194]: http.c:1953 httpd_helper_thread: HTTP opening session.  Top level
[2021-04-30 22:12:01] DEBUG[22194]: http.c:1483 handle_uri: Match made with [ari]
[2021-04-30 22:12:01] DEBUG[22194]: http.c:560 ast_http_send: HTTP closing session.  status_code:401
[2021-04-30 22:12:01] DEBUG[22194]: http.c:2010 httpd_helper_thread: HTTP closing session.  Top level
[2021-04-30 22:12:01] DEBUG[22194]: tcptls.c:845 ast_tcptls_close_session_file: ast_tcptls_close_session_file invoked on session instance without file or file descriptor

By: Benjamin Keith Ford (bford) 2021-05-10 12:59:42.398-0500

Unfortunately this doesn't give us much information to figure out what's going on. We're going to need the core dump / backtraces to really get an idea of what's happening.

By: Asterisk Team (asteriskteam) 2021-05-25 12:00:00.977-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