Views

Difference between revisions of "Nagios XI:FAQs"

From Nagios Support Wiki

(Installation and Upgrade Problems)
(Problems Using Nagios XI With Proxies)
Line 30: Line 30:
 
In /etc/yum.conf :
 
In /etc/yum.conf :
  
<nowiki>proxy=http://someproxyserver:port/</nowiki>  
+
  proxy=<nowiki>http://someproxyserver:port/</nowiki> <nowiki>#</nowiki> Shouldn't need to be quoted, remember the trailing slash
+
  proxy_username=myname  <nowiki>#</nowiki> The username you authenticate to your proxy with, if applicable
<nowiki>#</nowiki> Shouldn't need to be quoted, remember the trailing slash
+
  proxy_password=mypass  <nowiki>#</nowiki> The password you provide to your proxy, if applicable
 
+
proxy_username=myname   
+
 
+
<nowiki>#</nowiki> The username you authenticate to your proxy with, if applicable
+
 
+
proxy_password=mypass   
+
 
+
<nowiki>#</nowiki> The password you provide to your proxy, if applicable
+
  
 
In /etc/wgetrc :
 
In /etc/wgetrc :
  
<nowiki>http_proxy=http://myname:mypass@someproxyserver:port/</nowiki>  
+
  http_proxy=<nowiki>http://myname:mypass@someproxyserver:port/</nowiki> <nowiki># A</nowiki>ll in one string this time
 
+
  no_proxy=localhost,127.0.0.0/8,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16 <nowiki>#</nowiki> Hosts to exclude from proxying
<nowiki># A</nowiki>ll in one string this time
+
 
+
<nowiki>no_proxy=localhost,127.0.0.0/8,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16</nowiki> 
+
 
+
<nowiki>#</nowiki> Hosts to exclude from proxying
+
  
 
Quoting is not needed (or helpful) in any of these, but if you have special characters in passwords (especially : or @) and are having problems you probably need to escape them with backslashes.
 
Quoting is not needed (or helpful) in any of these, but if you have special characters in passwords (especially : or @) and are having problems you probably need to escape them with backslashes.

Revision as of 16:02, 29 September 2010

Back To Nagios XI Overview

Answers to Frequently Asked Questions (FAQs) regarding Nagios XI can be found here.


FAQs

What Are FAQs? Frequently Asked Questions, or "FAQs", are answers to questions that are frequently asked in some context.


Common Problems - Try These Solutions First

Follow these steps if you are encountering problems with Nagios XI. These actions solve many commonly asked questions.

  • Clear your browser's cache to get the newest XI javascript code.
    Instructions on how to do it.
  • How To Reset Security Credentials (if performance graphs aren't displayed)
    Select the Reset Security Credentials option in the Admin section and click Update.
  • How To Reset File Permissions (if configuration changes are not taking effect)
    Instructions how.
  • Debugging Configuration Change Problems (if configuration changes are not taking effect)
    Write configuration file tool.


Capabilities

Is Nagios XI capable of Distributed Monitoring?

Yes it is! Nagios Core (the underlying monitoring engine) can be configured for distributed monitoring. For more information, read the Nagios Core documentation on distributed monitoring.


System Configuration Problems

Problems Using Nagios XI With Proxies

We do not officially support Nagios XI when you install and use proxy software that restricts traffic to or from the Nagios XI server. There are several reasons for this. First, Nagios XI requires external access for package installation and updates. Package installation and updates may not work when proxies are used. Additionally, the Nagios XI code makes several internal HTTP calls to the local Nagios XI server to import configuration data, apply configuration changes, process AJAX requests, etc. These functions may not work properly when you deploy a proxy, which would result in a non-functional Nagios XI installation.

There are two things that need to be configured to make XI installation work with a proxy; the yum and wget configurations. Do both of these before starting anything about the installation process.

In /etc/yum.conf :

 proxy=http://someproxyserver:port/ # Shouldn't need to be quoted, remember the trailing slash
 proxy_username=myname  # The username you authenticate to your proxy with, if applicable
 proxy_password=mypass  # The password you provide to your proxy, if applicable

In /etc/wgetrc :

 http_proxy=http://myname:mypass@someproxyserver:port/ # All in one string this time
 no_proxy=localhost,127.0.0.0/8,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16 # Hosts to exclude from proxying

Quoting is not needed (or helpful) in any of these, but if you have special characters in passwords (especially : or @) and are having problems you probably need to escape them with backslashes.

Installation and Upgrade Problems

SourceGuardian Errors

After upgrading to 2009R1.2C, some users started getting an error about SourceGuardian. Add this line to your /etc/php.ini file:

 extension=ixed.5.1.lin

Once you make that change, restart Apache:

 service restart httpd
Resolving "NSP: Sorry Dave, I can't let you do that" Errors

Session protection was added to 2009R1.2C to prevent CSRF attacks. This code to do this caused some users to see this error. The problem was due to the user's browser caching older versions of the XI javascript code. In order to clear the cache and prevent this from happening, you need to clear your browser's cache. This is typically done (in Firefox) by holding down the shift key and clicking reload. See Other well documented procedures on clearing the browser cache.


"HTTP 500 Error"/"PHP Parse error - Unexpected $end"

For those doing manual installations, some of the tools embedded in Nagios XI use the PHP short tags feature, which is not necessarily enabled on all web servers by default. To fix this issue, locate your php.ini file (located at /etc/php.ini for CentOS installations), and verify that "short_open_tag" is set to "on." We intend to use full tags for future version, but some components and addons may still use them, so we recommend leaving this setting to "on."

Configuration Problems

Modifying The Contents Of /usr/local/nagios/etc
  • You can keep custom configuration files in the /usr/local/nagios/etc/static directory
  • Don't modify config files directly in /usr/local/nagios/etc, as they will be overwritten by the Core Config Manager
Unable To Delete Hosts

Hosts can only be deleted after all of their dependent services and associated relationships have been deleted. Make sure to delete any associated services or other objects before deleting the host.


Network status map parent/child relationship not updating(v1.3)

Underneath the Parents box in the CCM, make sure the "standard" radio button is selected. If "null" is selected your parent host selection doesn't get written to disk. We're working on a method of fixing the CCM so this doesn't happen with several fields.


Core Config Manager Problems
GUI Issues

Most of these are related to IE's implementation of JavaScript. If possible, use a browser that more closely implements the ECMAScript Language Specification.

Configuration Changes

If you make changes to your configuration and they are not reflected in XI, it may be due to file permissions. Here are two options to try:


Performance Graph Problems

Performance Graphs Are Missing Or Not Displayed

This can happen for a variety of reasons, but there are several simple solutions that resolve this issue for most people:

Notification Problems

Nagios Admin Account Notifications Not Controlled Through XI
  • The nagiosadmin user was set to use the generic_template contact template, which resulted in notifications not being controlled through the XI interface.
    This can be corrected by changing the user's contact template to be xi_generic_template is the Core Config Manager. This bug was corrected in 2009R1.2 and only effects systems that had/have previous versions installed.
Email Notifications Are Not Going Out

This can happen for a variety of reasons:

  • The nagiosadmin is set to use the generic_template contact template.
    This should be xi_generic_template, and can be modified by using the Core Config Manager. This bug was corrected in 2009R1.2 and only effects systems that had/have previous versions installed.
  • Outbound SMTP connections may be blocked by your border firewall
  • Unauthenticated SMTP relaying may be denied somewhere downstream - try switching email methods from Sendmail to SMTP in the admin section

Other Issues

Login Screen Keeps Redirecting To Itself

The web browser keeps redirecting to the login screen even after entering login credentials. This has been noticed in Internet Explorer.

Nagios XI uses cookies to save session state. These cookies are set to expire after 30 minutes. If the time on the Nagios XI server is incorrect, the cookies returned to the client's browser might appear to be expired due to the time difference between the client's computer and the Nagios XI server. Solution: Fix the time on the Nagios XI server to ensure it is correct.


Check Services Being Orphaned

Some users have encountered large numbers of warning messages that accumulate quickly that read as follows:

Warning: The check of service <Your Service> on host <Your Host> looks like it was orphaned (results never came back). I'm scheduling an immediate check of the service..

This is most likely caused by multiple instances of Nagios running. To fix this kill all instances of Nagios and then restart the process. Related forum post can be read here.


// ?>