Is your Nagios bandwidth graph showing 0 MB? We can help you with it.

Here at Bobcares, we have seen several such Nagios-related errors as part of our Server Management Services for web hosts and online service providers.

Today we’ll take a look at how to fix this Nagios error.

Know more about ‘Nagios bandwidth graph showing 0 MB’

Nagios is an open source monitoring system that monitors devices. Actually, it runs periodic checks on critical parameters of application, network, and server resources.

Generally, Nagios XI running on a system uses certain non-English languages, bandwidth services. However, their associated graphs may incorrectly report 0 MB/s even though there is traffic actively flowing through the given port.

How we resolve ‘Nagios bandwidth graph showing 0 MB’ problem

Here are the steps our Support Engineers provide to our customers to resolve this error message.

The easiest fix our Engineers suggest is to edit the resource.cfg file. In this file add LC_ALL=C before the $USER1$ macro as a prefix to be run before all commands Nagios runs. It forces applications to use the default language for output. LC_ALL is the environment variable that overrides all the other localization settings.

Different aspects of localisations can be set using a few environment variables.

1. First, open the /usr/local/nagios/etc/resource.cfg file in any preferred text editor.

2. Next, edit the $USER1$ macro (typically the second line of the file) as follows:

$USER1$=LC_ALL=C /usr/local/nagios/libexec

3. Then save and close the file. Now, restart the Nagios service using one of the commands below depending on the OS:

RHEL 6|CentOS 6|Oracle Linux 6|Ubuntu 14

# service nagios restart

RHEL 7|CentOS 7|Oracle Linux 7|Debian|Ubuntu 16/18

# systemctl restart nagios.service

4. Finally, graphs must start showing proper information. It may take up to 15 minutes for the changes to take effect, possibly longer for large environments.

[Need any further assistance in fixing Nagios errors? – We are here to help you]

Conclusion

Today, we saw how our Support Engineers resolve this Nagios error and provide a solution to our customers.