On Friday 11 December 2009 12:56:53 Chris Blake wrote: > On Fri, Dec 11, 2009 at 12:18 PM, Martin Melin <mme...@gmail.com> wrote: > [Fri Dec 11 13:20:09 2009] [error] [client 192.168.2.102] (2)No such > file or directory: Could not open password file: > /usr/local/nagios/etc/htpasswd.users > [Fri Dec 11 13:20:09 2009] [error] [client 192.168.2.102] access to > /nagios/ failed, reason: verification of user id 'nagiosadmin' not > configured > > I have the following permissions set up : > > [r...@zabbix etc]# pwd > /usr/local/nagios/etc > [r...@zabbix etc]# ls -l > total 88 > -rw-rw-r-- 1 nagios nagios 11408 Dec 11 13:16 cgi.cfg > -rwxrwxrwx 1 nagios nagios 26 Dec 11 12:52 htpassword.users > -rw-rw-r-- 1 nagios nagios 43776 Dec 11 10:36 nagios.cfg > drwxrwxr-x 2 nagios nagios 4096 Dec 11 10:36 objects > -rw-rw---- 1 nagios nagios 1340 Dec 11 10:36 resource.cfg > [r...@zabbix etc]# > > Can someone please help me, I have gone through a few articles and I > am obviously missing something as to why I cannot log in
Hi, your webserver looks for /usr/local/nagios/etc/htpasswd.users, but your file is named htpassword.users. Just rename your htpassword.users to htpasswd.users and everything should be fine. Greetings, Christian > > Thank you. > -- Christian Schneemann Geschaeftsfuehrer: Ralph Dehner Technical Tester & Writer Unternehmenssitz: Vohburg B1 Systems GmbH Amtsgericht: Ingolstadt Handelsregister: HRB 3537 EMail: schneem...@b1-systems.de http://www.b1-systems.de Adresse: B1 Systems GmbH, Osterfeldstraße 7, 85088 Vohburg GPG: http://pgpkeys.pca.dfn.de/pks/lookup?op=get&search=0x2FA8643A41BDAB81 ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Nagios-users mailing list Nagios-users@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