Absent Member.. Absent Member..
Absent Member..
344 views

SA support tip: 10.0 install on RHEL 6.4 causes httpsProxy error

Installing SA on RHEL 6.4 causes httpsProxy to throw an error during the startup of this component. A minor workaround will permit httpsProxy to start up correctly.

 

 Here is an example of an attempted restart of httpsProxy which is exhibiting this issue:

 

 

httpsProxy: Starting httpsProxy on ports (80 81 82 4433)

[Fri Sep 27 22:02:39 2013] [warn] VirtualHost localhost:82 overlaps with VirtualHost localhost:82, the first has precedence, perhaps you need a NameVirtualHost directive

[Fri Sep 27 22:02:39 2013] [warn] VirtualHost localhost:81 overlaps with VirtualHost localhost:81, the first has precedence, perhaps you need a NameVirtualHost directive

(98)Address already in use: make_sock: could not bind to address 127.0.0.1:81

no listening sockets available, shutting down

Unable to open logs

Successfully performed "restart" operation on Opsware SAS components.

[root@usculhpsat01 httpsProxy]#

[root@usculhpsat01 httpsProxy]#

[root@usculhpsat01 httpsProxy]# /etc/init.d/opsware-sas status httpsProxy

Verify "httpsProxy" is running: FAILURE (process not running)

Verify local "httpsProxy" is listening on port 80: FAILURE (Connection refused)

Failed to perform "status" operation on Opsware SAS components.

 

 This issue has definitely been seen when doing a new install of SA 10.0 on RHEL 6.4; this is not to say that it could not happen with other versions of SA or RHEL. If the version of SA or the version of RHEL are not an exact match, feel free to try the workaround described below.

 

 

The simple workaround to this issue is to remove both the 'localhost' and 'localhost.localdomain' hostnames from resolving to ::1 (IPv6), and leave them unchanged on the line which resolves to 127.0.0.1 (IPv4).

 

 

Please view this KM for more details on how to do this:

 

 

http://support.openview.hp.com/selfsolve/document/KM00590811

 



Ed Molina
HP Cloud Solution Support Engineer

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution. Also, if you liked this post please consider providing Kudos on the left side.
Labels (1)
0 Replies
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.