Re: nagios

[caio ferreira <idic@terra.com.br>]

On 15 Jun 2003 13:35:44 -0300
Srinath Mantripragada <srinathm@terra.com.br> wrote:

> e verifique no apache as configuracoes para execussao de scripts
> CGI algo do tipo:
>  ScriptAlias /cgi-bin/nagios /usr/lib/cgi-bin/nagios/
>  ScriptAlias /nagios/cgi-bin /usr/lib/cgi-bin/nagios/
> no seu caso deve estar dentro do dir /usr/local/nagios/

	Fiz a alteração que você sugeriu acima e mesmo assim estou tendo
problemas para executar o nagios.

## /etc/apache/httpd.conf

ScriptAlias /cgi-bin/nagios /usr/local/nagios/sbin/
ScriptAlias /nagios/cgi-bin /usr/local/nagios/sbin/
                                                                      
ScriptAlias /nagios/cgi-bin/ /usr/local/nagios/sbin/
<Directory "/usr/local/nagios/sbin/">
  AllowOverride AuthConfig
  Options ExecCGI
  Order allow,deny
  Allow from all
</Directory>

Alias /nagios/ /usr/local/nagios/share/
<Directory "/usr/local/nagios/share">
  Options None
  AllowOverride AuthConfig
  Order allow,deny
  Allow from all
</Directory>

	Quando eu tento acessar alguns dos serviços do nágios aparece a
seguinte mensagem de erro :

Whoops!

Error: Could not read host and service status information!

The most common cause of this error message (especially for new
users), is the fact that Nagios is not actually running. If Nagios is
indeed not running, this is a normal error message. It simply
indicates that the CGIs could not obtain the current status of hosts
and services that are being monitored. If you've just installed
things, make sure you read the documentation on starting Nagios.

Some other things you should check in order to resolve this error
include:

	1. Check the Nagios log file for messages relating to startup or
status data errors.   
	2. Always verify configuration options using the
-v command-line option before starting or restarting Nagios!   
	3. Make sure you've compiled the main program and the CGIs to use the
same status data storage options (i.e. text file or database). If the
main program is storing status data in a text file and the CGIs are
trying to read status data from a database, you'll have problems.

	No arquivo de log do nagios não aparece nenhuma mensagem de erro
quando ele foi parado e reinicializado.

[1055699308] Caught SIGTERM, shutting down...
[1055699308] Successfully shutdown... (PID=6146)
[1055699330] Nagios 1.1 starting... (PID=6284)
[1055699330] Finished daemonizing... (New PID=6285)
 
	Na segunda opção, a de que durante a parada e reinicialização do
nagios tenha aparecido alguma mensagem de erro isso não aconteceu.

muon:/usr/local/nagios# /etc/init.d/nagios stop
Stopping network monitor: nagios

muon:/usr/local/nagios# /etc/init.d/nagios start
Starting network monitor: nagios
  PID TTY          TIME CMD
 6285 ?        00:00:00 nagios

-- 

[ ]'s
 
  *******************    .''`.
* idic@terra.com.br  *  : :'  :
* GNU/Linux Debian   *  `. `'`
  *******************     `-
Gnupg ID 0x01186BE1
Key fingerprint =3D F17E 75C6 CE00 0E09 F63B  71B0 A0D2 FAD9 0118 6BE1

	Nunca deixo de ter em mente que o simples fato de existir ja 
	e divertido.
		--  Katherine Hepburn