| Summary: | ASTERISK-30423: Problem with segfault | ||
| Reporter: | Bruno da Rocha (Bruno da Rocha) | Labels: | |
| Date Opened: | 2023-02-10 06:44:48.000-0600 | Date Closed: | 2023-02-10 06:47:57.000-0600 |
| Priority: | Critical | Regression? | |
| Status: | Closed/Complete | Components: | . I did not set the category correctly. |
| Versions: | 17.1.0 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | Linux server Asterisk works on Debian 10. RAM memory 15Gi Processing: 4 cores Disk memory (HD): 945G virtualized server | Attachments: | |
| Description: | This problem never happened before, but last month it started to give this problem in this informed asterisk and in other machines as well. I increased the RAM memory for testing, but it didn't work. I need a quick update from the Asterisk team to see if the only solution is to update the version to a more current one.
Erro: asterisk[16875]: segfault at 88 | ||
| Comments: | By: Asterisk Team (asteriskteam) 2023-02-10 06:44:51.243-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. 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) 2023-02-10 06:47:57.343-0600 This is not something we're going to investigate or sink time into at all, to even figure out if upgrading to a new version will resolve it. We only accept issues against current supported versions. | ||