Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 450344

Summary: Confusing error by stunnel if service name unknown
Product: Red Hat Enterprise Linux 5 Reporter: David Tonhofer <bughunt>
Component: stunnelAssignee: Miloslav Trmač <mitr>
Status: CLOSED ERRATA QA Contact: Brian Brock <bbrock>
Severity: low Docs Contact:
Priority: low    
Version: 5.2CC: kwirth
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-09-24 15:11:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
The patch submitted upstream none

Description David Tonhofer 2008-06-06 20:07:30 UTC 
Description of problem:

(actually an upstream bug)

If you give an "accept" value to the stunnel server on which it is supposed to
listen (in stunnel.conf) with an unknown "service" port, e.g.:

-------
accept  = 80.92.62.11:mysql-SSL
-------

then stunnel-server says:

2008.06.06 21:53:54 LOG3[29997:47517674664128]: Error resolving '80.90.63.37':
servname is not supported for ai_socktype (EAI_SERVICE)

This error message is confusing. It should complain about "unknown service name
mysql-SSL" or something.

Adding a definition for "mysql-SSL" to /etc/services fixes the problem.

Version-Release number of selected component (if applicable):

stunnel-4.15-2

How reproducible:

Always
Comment 1 Miloslav Trmač 2008-06-06 20:16:20 UTC 
Thanks for your report.

If you are a RHEL customer and have an active support entitlement, please
contact official Red Hat Support at https://www.redhat.com/apps/support/ to
allow correct prioritization of this issue.
Comment 2 Miloslav Trmač 2008-06-08 04:54:02 UTC 
Created attachment 308633 [details]
The patch submitted upstream
Comment 9 errata-xmlrpc 2008-09-24 15:11:46 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2008-0894.html