Summary:	ASTERISK-28996: chan_sip: TLS - Bad file descriptor errors
Reporter:	Cody G (zermus)	Labels:
Date Opened:	2020-07-19 21:15:56	Date Closed:	2020-09-30 12:41:34
Priority:	Trivial	Regression?
Status:	Closed/Complete	Components:	Channels/chan_sip/TCP-TLS
Versions:	16.11.0	Frequency of Occurrence	Constant
Related Issues:	duplicates ASTERISK-28430 res_rtp_asterisk.c: FRACK!, Failed assertion errno != EBADF
Environment:	CentOS 8 - VMWare ESXi 6.7 U2 host	Attachments:
Description:	This is a new CentOS 8/Asterisk 16 setup. This worked fine with CentOS7/Asterisk 13, but in the CentOS 8/Asterisk 16 setup Asterisk won’t start and seems to stall out on this: [Jul 19 17:36:27] ERROR[1728] iostream.c: SSL_shutdown() failed: error:00000005:lib(0):func(0):DH lib, Underlying BIO error: Bad file descriptor [Jul 19 17:36:27] ERROR[1728] iostream.c: close() failed: Bad file descriptor [Jul 19 17:36:28] ERROR[1726] iostream.c: close() failed: Bad file descriptor More debug info: [Jul 19 17:44:26] ERROR[2341]: iostream.c:552 ast_iostream_close: SSL_shutdown() failed: error:00000005:lib(0):func(0):DH lib, Underlying BIO error: Bad file descriptor [Jul 19 17:44:26] ERROR[2341]: iostream.c:583 ast_iostream_close: close() failed: Bad file descriptor [Jul 19 17:44:26] ERROR[2338]: iostream.c:583 ast_iostream_close: close() failed: Bad file descriptor Even though this was compiled with pjsip, I'm using chansip, if that matters.
Comments:	By: Asterisk Team (asteriskteam) 2020-07-19 21:15:57.776-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. By: Benjamin Keith Ford (bford) 2020-07-20 09:49:04.563-0500 Have you tried any versions of Asterisk other than 16.11 on this new machine to confirm whether or not it's a problem with the OS rather than Asterisk? Trying earlier versions of 16 (and 13) to see if the problem goes away can help us see if it's a change that was introduced that broke it. By: Cody G (zermus) 2020-07-20 14:14:06.562-0500 I can play around with that as time permits.  Might take a week or two. By: Cody G (zermus) 2020-07-20 21:08:47.008-0500 Well asterisk 13 init.d script barfs on CentOS 8 so testing that isn't going well since it has no systemd scripts.  Asterisk 16.10 seems to have the issue as well, though. By: Cody G (zermus) 2020-07-21 03:19:25.340-0500 Confirmed down to 16.5.0 as having this issue, possibly below.  I just haven't tried below that version. By: Joshua C. Colp (jcolp) 2020-07-21 10:37:17.722-0500 The chan_sip channel driver is in 'extended' support status and is supported only by community members.  Your issue is in the queue. Your patience is appreciated as a community developer may work the issue when time and resources become available. Asterisk is an open source project and community members work the issues on a voluntary basis. You are welcome to develop your own patches and submit them to the project.[1] If you are not a programmer and you are in a hurry to see a patch provided then you might try rallying support on the Asterisk users mailing list or forums.[2] Another alternative is offering a bug bounty on the asterisk-dev mailing list.[3] Often a little incentive can go a long way. [1]: https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process [2]: http://www.asterisk.org/community/discuss [3]: https://wiki.asterisk.org/wiki/display/AST/Asterisk+Bug+Bounties By: Cody G (zermus) 2020-07-21 19:04:13.905-0500 Thanks!  I appreciate it.