Logged in as ?

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Nigel kendrick
> Sent: Thursday, November 24, 2005 8:43 AM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Logged in as ?
> 
> I am having a similar problem to Lori:
> 
> I have had Nagios 1.2 running for nearly two years on a CentOS 3.x
> installation but I have just downloaded 1.3, installed it on a new
server
> running CentoS 4.2 (RHEL4) and copied over the .cfg files.
> 
> All .htaccess and htpasswd files are in place and working properly,
the
> ScriptAlias and Alias text is in place in /etc/httpd/conf.d/nk.conf
> (copied
> from the other server), yet I am always shown as 'logged in as ?'
> 
> The nagios directory and all below are owned by apache:nagios
> 
> The only way I can run Nagios is if I turn off authentication - in
which
> case everything works fine.
> 
> Any ideas?

Look in your apache error logs. Almost certainly the .htaccess file in
your sbin directory isn't being processed properly. Nagios simply looks
at the value of the environment variable REMOTE_USER, set by Apache, to
determine who is logged in. Apache is not setting it for scripts
accessed in the sbin directory.

A less likely problem may be your SELinux restrictions if you have it
enabled. Look in /var/log/messages for 'avc denied' messages related to
the nagios directories.

--
Marc


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&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