Bug 38951

Summary:	Apache segfaults in Servername unset and no DNS name exists
Product:	[Retired] Red Hat Linux	Reporter:	Mark Levitt <melevittfl>
Component:	apache	Assignee:	Nalin Dahyabhai <nalin>
Status:	CLOSED CURRENTRELEASE	QA Contact:	David Lawrence <dkl>
Severity:	low	Docs Contact:
Priority:	medium
Version:	7.1
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2001-05-03 14:15:07 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:

Description Mark Levitt 2001-05-03 14:15:03 UTC

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0)

Description of problem:
Running /etc/rc.d/init.d/http start   produced:
Starting.....[FAILED]

Directly attempting to start Apache with /usr/sbin/httpd produced a 
segfault in httpd.

Once I set the Servername variable in httpd.conf, Apache started 
correctly. My machine has a DHCP assigned IP address and no DNS name.

I understand the Servername variable is supposed to be set, but I would 
not expect Apache to Segfault. 

How reproducible:
Always

Steps to Reproduce:
1.On a machine without a DNS name, start Httpd
2.
3.
	

Actual Results:  Segfault in httpd

Expected Results:  Apache starts

Additional info:

Comment 1 Joe Orton 2001-11-23 15:20:38 UTC

Thanks for the report. The segfault was a bug in Apache 1.3.19; it was fixed in
1.3.20.