Bug 79274 – Xinetd v 2.3.7-4.7x redirects fail to start

Bug 79274 - Xinetd v 2.3.7-4.7x redirects fail to start

Summary:	Xinetd v 2.3.7-4.7x redirects fail to start

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	xinetd (Show other bugs)
Sub Component:
Version:	7.3
Hardware:	i686 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Jay Fenlason
QA Contact:	Brock Organ
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2002-12-09 08:55 EST by Andrew Meredith
Modified:	2014-08-31 19:24 EDT (History)
CC List:	6 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2003-05-13 13:14:06 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Andrew Meredith 2002-12-09 08:55:27 EST

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
With xinetd 2.3.7-4.7x the /etc/xinetd.d/ entries that represent local services
start just fine, but the entries that represent redirects do not seem to be
recognised. The output from xinetd -d shos that the files are found and read
with no extra debug output showing an error.

Downgrading to 2.3.3-1 with the same xinfig files in xinetd.d brings the
redirects back into service.

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

How reproducible:
Always

Additional info:

An xinetd.d file that works under the old version of xinetd, but not the new one.

[root@zool root]# cd /etc/xinetd.d/
[root@zool xinetd.d]# cat http
# default: off
# description:  A port forward for http
service http
{
	disable	= no
	socket_type		= stream
	protocol		= tcp
	wait			= no
	user			= root
	redirect		= 192.168.15.1 80
}

Comment 1 Mike Baptiste 2003-01-08 15:31:58 EST

This is a known bug in v2.3.7 and I just got nailed by it this morning when we
updated xinetd.  Redhat really needs to fix this - all port redirects seem
broken with version 2.3.7

See 
http://marc.theaimsgroup.com/?l=xinetd&m=102996722420681&w=2
and
http://marc.theaimsgroup.com/?l=xinetd&m=102997330427341&w=2

where other users report this issue

We have backed down to v2.3.4 and everything with our redirects is working again

Comment 2 Andrew Meredith 2003-01-08 20:19:50 EST

A fix was formally released in 2.3.8 

* Reworked redirect to better detect problems
  in its configuration. Also, redirect now allows
  service names for port numbers. -Steve Grubb

cheers Steve

... and there is now a 2.3.9 (Released 24 Sep 2002)

This one will quite probably hurt Red Hat's corporate customers who are trying
to use RH7.2/7.3/8.0 as a proxy-firewall platform. It really isn't making Red
Hat's QA function look that good.

Comment 3 Mark J. Cox (Product Security) 2003-05-13 13:14:07 EDT

An errata 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 the 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/RHSA-2003-160.html

Note You need to log in before you can comment on or make changes to this bug.