[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Nagios 3



Seguinte:
vê aê qual é o DocumentRoot do teu apache e depois olha se o nagios está nesse document root que pelo que eu estou vendo no log não está

2009/2/10 Moksha Tux <govatux@gmail.com>
Esse é o Log de erro


[Tue Feb 10 13:32:35 2009] [notice] Apache/2.2.9 (Debian) configured -- resuming normal operations

  2 [Tue Feb 10 13:44:54 2009] [notice] SIGUSR1 received.  Doing graceful restart
  3 [Tue Feb 10 13:44:54 2009] [notice] Apache/2.2.9 (Debian) configured -- resuming normal operations
  4 [Tue Feb 10 13:45:39 2009] [error] [client 10.202.0.150] File does not exist: /var/www/nagios
  5 [Tue Feb 10 13:45:39 2009] [error] [client 10.202.0.150] File does not exist: /var/www/favicon.ico
  6 [Tue Feb 10 13:56:27 2009] [error] [client 10.202.0.150] (2)No such file or directory: Could not open password file: /etc/nagios3/htpasswd.users
  7 [Tue Feb 10 13:56:34 2009] [error] [client 10.202.0.150] (2)No such file or directory: Could not open password file: /etc/nagios3/htpasswd.users
  8 [Tue Feb 10 13:56:58 2009] [error] [client 10.202.0.150] (2)No such file or directory: Could not open password file: /etc/nagios3/htpasswd.users
  9 [Tue Feb 10 13:58:35 2009] [notice] caught SIGTERM, shutting down
 10 [Tue Feb 10 13:58:36 2009] [notice] Apache/2.2.9 (Debian) configured -- resuming normal operations
 11 [Tue Feb 10 13:58:59 2009] [error] [client 10.202.0.150] (2)No such file or directory: Could not open password file: /etc/nagios3/htpasswd.users
 12 [Tue Feb 10 13:59:09 2009] [error] [client 10.202.0.150] (2)No such file or directory: Could not open password file: /etc/nagios3/htpasswd.users
 13 [Tue Feb 10 13:59:10 2009] [error] [client 10.202.0.150] (2)No such file or directory: Could not open password file: /etc/nagios3/htpasswd.users
 14 [Tue Feb 10 13:59:10 2009] [error] [client 10.202.0.150] (2)No such file or directory: Could not open password file: /etc/nagios3/htpasswd.users
 15 [Tue Feb 10 15:03:10 2009] [notice] caught SIGTERM, shutting down
 16 [Tue Feb 10 15:03:11 2009] [notice] Apache/2.2.9 (Debian) configured -- resuming normal operations
 17 [Tue Feb 10 15:03:39 2009] [error] [client 10.202.0.150] (2)No such file or directory: Could not open password file: /etc/nagios3/htpasswd.users
 18 [Tue Feb 10 15:06:15 2009] [error] [client 10.202.0.150] File does not exist: /var/www/nagios
 19 [Tue Feb 10 15:09:50 2009] [error] [client 10.202.0.150] (2)No such file or directory: Could not open password file: /etc/nagios3/htpasswd.users
 20 [Tue Feb 10 15:09:50 2009] [error] [client 10.202.0.150] File does not exist: /var/www/favicon.ico
 21 [Tue Feb 10 15:09:53 2009] [error] [client 10.202.0.150] File does not exist: /var/www/favicon.ico
 22 [Tue Feb 10 16:04:43 2009] [error] [client 10.202.0.150] (2)No such file or directory: Could not open password file: /etc/nagios3/htpasswd.users
 23 [Tue Feb 10 16:04:45 2009] [error] [client 10.202.0.150] (2)No such file or directory: Could not open password file: /etc/nagios3/htpasswd.users
 24 [Tue Feb 10 16:40:21 2009] [error] [client 10.202.0.150] File does not exist: /var/www/nagios
 25 [Tue Feb 10 16:40:24 2009] [error] [client 10.202.0.150] (2)No such file or directory: Could not open password file: /etc/nagios3/htpasswd.users


2009/2/10 Thiago Silveira Alexandre <thsalex@gmail.com>

abre os logs do apache com o tail -f e tenta acessar e cola aqui a saida de erro que da

2009/2/10 Moksha Tux <govatux@gmail.com>
Ainda não sei se é problema, instalei tudo (Apache2, Nagios3, Mysql-server) e quando tentei acessar o serviço através da web, me retornou uma tela de login, fiquei contentão pois estava parecendo que estava tudo ok, então quando eu informava o usuário (nagiosadmin) e a senha que eu especifiquei ele me retornava a seguinte página de erro:


Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, webmaster@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.





--
Thiago Silveira Alexandre




--
Thiago Silveira Alexandre

Reply to: