Upgrade from RHES3 to RHES4 and authentication failures with apache

[Richard DeWath]

I planned on upgrading to a better host system and
since I am on RHES3 and can upgrade to RHES4, I went
ahead with a standard install.  Apache was upgraded
from  release 2.0.48 to 2.0.52 on the new system. 
Everything went well and I copied over the cfg files
and other plugins.  Nagios starts up and works - the
problem is with authentication for the website.  The
first problem I found when trying to authenticate with
.htaccess/.htpasswd showed up in the httpd error_log
indicating a MySQL authentication failure.  I did not
request that during the rpm based install, so I am not
sure why that has been added.  I fixed that so that
authentication will use .htaccess/.htpasswd.  That
seemed to work and I was allowed to the main page. 
When I went to look at the hosts on the new system I
was denied access.  After looking around I saw that
the env was missing all the authentication env
variables like REMOTE_USER=mysignon

I rebuilt and re-installed nagios to be sure it was
correct.  The problem persists.  

I know this is more an apache http issue, but I cannot
find any answers about this and why the upgrade has
caused this problem.  

If anyone has had this problem or can point me to a
solution, I would appreciate any help.

Richard

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null