| Summary: | ASTERISK-28822: chan_unistim.c: Recv error 9 (Bad file descriptor) | ||
| Reporter: | Cody G (zermus) | Labels: | |
| Date Opened: | 2020-04-11 05:43:56 | Date Closed: | 2020-05-04 12:00:01 |
| Priority: | Critical | Regression? | |
| Status: | Closed/Complete | Components: | Channels/chan_unistim |
| Versions: | 16.9.0 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | CentOS 8 | Attachments: | |
| Description: | Asterisk log is spammed with this:
[Apr 11 05:06:43] WARNING[2179] chan_unistim.c: Recv error 9 (Bad file descriptor) [Apr 11 05:06:43] WARNING[2179] chan_unistim.c: Recv error 9 (Bad file descriptor) [Apr 11 05:06:43] WARNING[2179] chan_unistim.c: Recv error 9 (Bad file descriptor) [Apr 11 05:06:43] WARNING[2179] chan_unistim.c: Recv error 9 (Bad file descriptor) [Apr 11 05:06:43] WARNING[2179] chan_unistim.c: Recv error 9 (Bad file descriptor) Seems to make my CPU spike like crazy and my log file maxes out my file system in about an hour lol. | ||
| Comments: | By: Asterisk Team (asteriskteam) 2020-04-11 05:43:59.283-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]. 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. By: Igor Goncharovsky (igorg) 2020-04-11 08:15:08.020-0500 Hello, Do you use unistim channel and what is your unistim.conf configuration? In case you do not use it, probably you have a lot of unexpected UDP traffic received by chan_unistim. You need to check incoming traffic, disable chan_unistim or configure firewall. By: Alexander Traud (traud) 2020-04-20 05:32:47.532-0500 According to the reporter, this is CentOS 8 specific and does not happen in CentOS 7, see https://community.asterisk.org/t/83535 By: Igor Goncharovsky (igorg) 2020-04-20 06:54:05.708-0500 Thanks, I see. I'll try to reproduce it when would have CentOS 8 installed. By: Asterisk Team (asteriskteam) 2020-05-04 12:00:00.629-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 | ||