Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 444140 - apache.sh doesn't work with apache v2.2
apache.sh doesn't work with apache v2.2
Product: Red Hat Cluster Suite
Classification: Retired
Component: rgmanager (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Marek Grac
Cluster QE
Depends On:
  Show dependency treegraph
Reported: 2008-04-25 08:07 EDT by Pavel V Martynenko
Modified: 2009-04-16 16:36 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-09-23 07:22:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
ugly patch (1.01 KB, patch)
2008-04-25 08:07 EDT, Pavel V Martynenko
no flags Details | Diff

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Bugzilla 1822342 None None None Never

  None (edit)
Description Pavel V Martynenko 2008-04-25 08:07:04 EDT
Description of problem:
there is no Port directive in apache v2.2. But apache.sh tries to use Listen and
Port insted of "Listen ip:port proto".

Version-Release number of selected component (if applicable):
rgmanager-2.0.31-1.el5_1.1 & httpd-2.2.3-11.el5_1.3

How reproducible:
use /usr/share/cluster/apache.sh in cluster.conf

Steps to Reproduce:
Actual results:
httpd doesn't start

Expected results:
working httpd server

Additional info:
Service Request: 1822342 - bug in /usr/share/cluster/apache.sh
Comment 1 Pavel V Martynenko 2008-04-25 08:07:04 EDT
Created attachment 303777 [details]
ugly patch
Comment 2 Marek Grac 2008-09-23 07:22:46 EDT
Resource agent can use both Listen and Port directives but it will not generate lines other then with Listen. If we will met 'Port' then it will be commented out. This description (and proposed patch) tends me to believe that this is not a bug.

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