Bug 616436 - system-config-httpd cannot configure IP and port addresses properly
Summary: system-config-httpd cannot configure IP and port addresses properly
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-httpd   
(Show other bugs)
Version: 13
Hardware: All Linux
Target Milestone: ---
Assignee: Phil Knirsch
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-20 13:11 UTC by Jesse Pollard
Modified: 2015-03-05 01:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-06-29 13:13:52 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Jesse Pollard 2010-07-20 13:11:55 UTC
Description of problem:

When configuring the httpd listen addresses system-config-httpd runs the
IP address and the port number together. Converting what should be: into The only way to get proper addressing is
to delete all entries.

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

How reproducible:
Just use it.

Steps to Reproduce:
1.Attempt to start apache (service httpd start)
2.Add extensive debugging output (-E file)
3.Attempt to start apache - fails as it exits immediately
  reported error is:
  (98)Address already in use: make_sock: could not bind to address [::]:80

4.delete all entries in system-config-httpd (main)
5.Attempt to start apache - succeeds 
Actual results:

Expected results:

Additional info:
The problem makes it impossible to use system-config-httpd as designed.

Comment 1 Bug Zapper 2011-06-01 13:21:49 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 2 Jesse Pollard 2011-06-01 16:17:02 UTC
The workaround of deleting all entries has been sufficient.

Since no one else has reported this bug (it is over a year old), it may have been fixed due to other updates.

Comment 3 Bug Zapper 2011-06-29 13:13:52 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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