Mod cluster Troubleshooting: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
=External= | |||
* Apache fails to proxy saying "No protocol handler was valid for the URL" https://access.redhat.com/solutions/277193 | |||
=Internal= | =Internal= | ||
* [[mod_cluster#Subjects|mod_cluster]] | * [[mod_cluster#Subjects|mod_cluster]] | ||
=Figure Out mod_cluster Version= | |||
It should be reported in httpd logs: | |||
<pre> | |||
[Thu Jun 16 00:47:50 2016] [notice] Apache/2.2.26 (Unix) DAV/2 mod_ssl/2.2.26 OpenSSL/1.0.1e-fips mod_cluster/1.2.9.Final CovalentSNMP/2.3.0 configured -- resuming normal operations | |||
</pre> | |||
=Increase Logging Verbosity= | =Increase Logging Verbosity= | ||
Latest revision as of 20:42, 8 February 2017
External
- Apache fails to proxy saying "No protocol handler was valid for the URL" https://access.redhat.com/solutions/277193
Internal
Figure Out mod_cluster Version
It should be reported in httpd logs:
[Thu Jun 16 00:47:50 2016] [notice] Apache/2.2.26 (Unix) DAV/2 mod_ssl/2.2.26 OpenSSL/1.0.1e-fips mod_cluster/1.2.9.Final CovalentSNMP/2.3.0 configured -- resuming normal operations
Increase Logging Verbosity
Set
LogLevel debug
in the mod_cluster virtual host.