Hi Team,
We have noticed one issue, for one of the Switch on daily basis we have scheduled report in nagios and will triggered. When we analyzed the report from 12:00 pm to 3:00 pm there is no utilization, so we checked with Network Team they had confirmed that on that particular time frame they can able to see traffic on the switch but nagios showing 0% utilization.
We checked in DR server for same interface and able to the utilization in that time frame. So, please help to resolve this issue at the earliest it's impacting our production environment. I have attached the Profile and Graph for reference
Let me know any further details required.
Graph Issue
Graph Issue
You do not have the required permissions to view the files attached to this post.
Re: Graph Issue
A ticket was re-opened with me about the same issue that you opened this post for. I'll answer here the same as what I put in the ticket.
The max_connection setting for the MYSQL database is not large enough and the max connections settings is maxed out on the server. When that happens, it will cause database corruptions and possible loss of data.
To increase it, edit the /etc/my.cnf file and under the following section
put the following
Save the change and run the following as root to restart the processes, truncate temporary data and repair the database.
For the Bandwidth graph issue, go in to the /etc/mrtg/conf.d folder and remove any configuration files for any equipment that are no longer active in the network.
Edit the /etc/mrtg/mrtg.cfg file and increase the forks from 16 to 24
Forks: 24
Save the file and that will allow more MRTG processes to run and gather data and should help out on the graph issue.
The max_connection setting for the MYSQL database is not large enough and the max connections settings is maxed out on the server. When that happens, it will cause database corruptions and possible loss of data.
To increase it, edit the /etc/my.cnf file and under the following section
Code: Select all
[mysqld]Code: Select all
max_connections = 1000
open_files_limit = 4096Code: Select all
systemctl stop npcd
systemctl stop nagios
systemctl stop ndo2db
systemctl stop crond
pkill -9 -u nagios
echo "truncate table xi_events; truncate table xi_meta; truncate table xi_eventqueue;" | mysql -u root -pnagiosxi nagiosxi
mysqlcheck -f -r -u root -pnagiosxi --all-databases --use-frm
systemctl restart mysqld
rm -f /usr/local/nagios/var/rw/nagios.cmd
rm -f /usr/local/nagios/var/nagios.lock
rm -f /var/run/nagios.lock
rm -f /usr/local/nagios/var/ndo.sock
rm -f /usr/local/nagios/var/ndo2db.lock
rm -f /var/lib/mrtg/mrtg_l
rm -f /usr/local/nagiosxi/var/*.lock
for i in `ipcs -q | grep nagios |awk '{print $2}'`; do ipcrm -q $i; done
pkill python
systemctl restart apache2
systemctl start ndo2db
systemctl start nagios
systemctl start npcd
systemctl start crondEdit the /etc/mrtg/mrtg.cfg file and increase the forks from 16 to 24
Forks: 24
Save the file and that will allow more MRTG processes to run and gather data and should help out on the graph issue.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Graph Issue
In a lot of cases, you can just open up a plugin with a text editor to read what it is trying to do.
It is not usually advisable to revoke sudo permissions for a plugin; as I have seen many issues related to it. You would probably disable your ability to check if the init service on that system is running.
additional resources =
NRPE DOCUMENT
NRPE on GitHub
Code: Select all
vi /usr/local/nagios/libexec/check_init_serviceadditional resources =
NRPE DOCUMENT
NRPE on GitHub
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Be sure to check out our Knowledgebase for helpful articles and solutions!