Bug 81092 - httpd won't start when adding multiple listening ports using the configurator.
httpd won't start when adding multiple listening ports using the configurator.
Status: CLOSED DUPLICATE of bug 75210
Product: Red Hat Linux
Classification: Retired
Component: httpd (Show other bugs)
8.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Joe Orton
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-01-03 23:56 EST by Lemster
Modified: 2007-04-18 12:49 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 13:50:55 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Lemster 2003-01-03 23:56:53 EST
Description of problem: Apache server configurator, when adding multiple
listening ports, the output string httpd.conf file -> Listen *.80 *.xxx where
xxx another port. Apache don't like it. Need to have Listen *.80 <newline>
Listen *.xxx


Version-Release number of selected component (if applicable): 8.0 patched all to
latest releases, clean install.


How reproducible: always


Steps to Reproduce:
1.goto "server settings" + "http server" from redhat start menu
2.add a new port, in additon to the standard port 80
3.save the file
4.bounce httpd -> go to /etc/init.d/httpd restart
    
Actual results:

http crashes

<snippit start>
Starting httpd: Syntax error on line 146 of /etc/httpd/conf/httpd.conf:
Listen takes one argument, A port number or a numeric IP address and a port number
                                                           [FAILED]

<snippit end>


Expected results:

Well I suppose it should say [OK] instead of [FAILED]



Additional info:

Happy New Year!
Comment 1 Joe Orton 2003-01-13 12:44:27 EST

*** This bug has been marked as a duplicate of 75210 ***
Comment 2 Red Hat Bugzilla 2006-02-21 13:50:55 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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