There are a lot of Nagios errors 
out there. Way too many, right?

You as sysadmin know that for sure – return code errors,
specify direct recipients, hosts unreachable.

Here you'll find quick solutions for the most common Nagios errors:

  1. Nagios error "Return code of x is out of bounds"
  2. Nagios error "mail: Null names are not allowed" or Nagios Error "You must specify
    direct recipients with -s, -c, or -b."
  3. Nagios error "Error in configuration file 'xxxxxxx.cfg' - Line 34 (Unknown variable)"
  4. Nagios error "Could not open command file <filename> for update"
  5. Nagios error "Hosts UNREACHABLE"
  6. Nagios error "IndexError: list index out of range"

 

And you'll find the solution to get rid of ALL Nagios errors – forever: Test PRTG as your new monitoring tool and get startet in minutes!

 

 1. Nagios error:

"Return code of x is out of bounds"

 

Quick fix

If the output of a plugin for a host or service check returns a "(Return code of x is out of bounds)" error, this usually means two things:

  • The plugin you use to check the service or host does not return a correct return value when it terminates
  • The path to the plugin is invalid (e.g. the program or script does not exist). This is usually the case if there is an error with the return value 127. If you get this error, you need to check your command definition and make sure that the path to the plugins is correct (and that you really are installed on your system at this point).

 Proper fix

Switch to PRTG: PRTG automatically discovers and monitors all your network devices, bandwidth and traffic. Test now for free and get rid of all your Nagios errors like this most common one – forever.

See why monitoring with PRTG is like working in paradise.

 

 2. Nagios error: 

"mail: Null names are not allowed"

"You must specify direct recipients with -s, -c, or -b."

 

Quick fix

Error in the definition of the notification command.

Make sure that the syntax you use to call /bin/mail (or where/how your mail program should be) is correct in the definition of the notification command for your system.

 Proper fix

Switch to PRTG as your new file monitoring tool. Monitor all your files and applications – agentless. Get started with PRTG in parallel to Nagios in minutes and get rid of all your Nagios errors – forever.

See why monitoring with PRTG is like working in paradise.

 

 3. Nagios error: 

"Error in configuration file 'xxx.cfg' - Line 34 (Unknown variable)"

 

 

Quick fix

Make sure that you pass the path to your main configuration file on the command line.

The correct syntax should look like the following command (possibly changed something for your system, of course):

/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg

 Proper fix

Switch to PRTG. No need for configuration files anymore. PRTG monitors all your network devices, bandwidth and traffic at a glance. Get PRTG started in minutes and get rid of all your Nagios errors – forever.

More information about monitoring with PRTG – without buggy config files!

 

 4. Nagios error: 

"Could not open command file for update"

 

 

Quick fix

Usually a problem with directory and/or file permissions.

  • Make sure that you have created a directory for the command file.
  • Make sure that you have restarted your web server so that it recognizes the new group permissions you have assigned.

 Proper fix

No need for command files anymore. PRTG monitors all your network devices, bandwidth and traffic at a glance. Get PRTG started in minutes and get rid of all your Nagios errors – forever.

Take a look how PRTG makes monitoring that easy – without command files.

 

 5. Nagios error: 

"Hosts UNREACHABLE"

 

 

Quick fix

You have activated the notify_unreachable option in the host definition(s).

If you do not want to be notified when a host is unreachable, you only need to deactivate this option in the host definition.

 

 Proper fix

Switch to PRTG as your new network monitoring tool. Monitor all your hosts – agentless. Get started witrh PRTG in parralel to Nagios in minutes and get rid of all your Nagios errors – forever.

Take a look how PRTG makes monitoring that easy

 

6. Nagios error: 

"IndexError: list index out of range"

 

 

Quick fix

Perform a file check one at a time.

Details can be found in your log file - "Check log for details"

 Proper fix

Switch to PRTG: PRTG automatically discovers and monitors all your network devices, bandwidth and traffic. Test now for free and get rid of all your Nagios errors like this most common one – forever.

Take a look how PRTG makes monitoring that easy

 

Choose your solution: Bugfix or replacement

 

With PRTG you'll never have to deal with
Nagios errors again. Ever.

 


  • Monitor all the systems, devices, traffic, and applications in your IT infrastructure.

  • Everything is included with PRTG; there is no need for additional plugins or downloads.


  • PRTG is a powerful and easy-to-use solution, which is suitable for businesses of all sizes.

 

Free Download

Unlimited version of PRTG for 30 days. After 30 days, PRTG reverts to a free version.
Or, you can upgrade to a paid license anytime.

 
 

Trusted by 300,000 users
and recognized by industry analysts as a leader

“Fantastic network and infrastructure monitoring solution that is easy to deploy and easier still to use. Simply the best available.”

Read more reviews

“Software is absolutely perfect, Support is superior. Meets all needs and requirements, This is a must have solution if you are needing any form of monitoring.”

Read more reviews

“The tool excels at its primary focus of being a unified infrastructure management and network monitoring service.”

Read more reviews



This third party content uses Performance cookies. Change your Cookie Settings or

load anyways

*This will leave your Cookie Settings unchanged.