Capacity Planning Graphs - values not JSON compliant

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
User avatar
lmiltchev
Bugs find me
Posts: 13589
Joined: Mon May 23, 2011 12:15 pm

Re: Capacity Planning Graphs - values not JSON compliant

Post by lmiltchev »

You can revert the changes you made - that's what devs wanted us to try.

Is there a change that you modified your command and the number of data sources changed? Can you run the following command and show us the output?

Code: Select all

rrdtool info /usr/local/nagios/share/perfdata/hp.core.fcu/Ping.rrd
Be sure to check out our Knowledgebase for helpful articles and solutions!
User avatar
tgriep
Madmin
Posts: 9190
Joined: Thu Oct 30, 2014 9:02 am

Re: Capacity Planning Graphs - values not JSON compliant

Post by tgriep »

I think I found a fix for the graphing issue. One question I have is did you change the service check from check_ping to check_icmp?
Go to the link below and follow the section called
ICMP and Ping Checks Stopped Graphing After XI 2014 Upgrade
http://support.nagios.com/wiki/index.ph ... _Displayed

After it is done, the graphs will have to capture data for many hours before they populate.
Be sure to check out our Knowledgebase for helpful articles and solutions!
FLCUISIT
Posts: 93
Joined: Mon Feb 01, 2010 12:09 pm

Re: Capacity Planning Graphs - values not JSON compliant

Post by FLCUISIT »

What should the Ping Alert look like - We use the wizard to create these and I now notice that there is no command on any of these Ping Service alerts. see attached

Shouldn't a check_ping or check_icmp be in the command fro each of these ping service alerts?

Also ,I do not have this folder mentioned in the support link: /var/lib/mrtg/ so I cannot test the check command it references
You do not have the required permissions to view the files attached to this post.
jolson
Attack Rabbit
Posts: 2560
Joined: Thu Feb 12, 2015 12:40 pm

Re: Capacity Planning Graphs - values not JSON compliant

Post by jolson »

Please check the template that the host is attached to. The template will very likely define the ping command in question.
Twits Blog
Show me a man who lives alone and has a perpetually clean kitchen, and 8 times out of 9 I'll show you a man with detestable spiritual qualities.
FLCUISIT
Posts: 93
Joined: Mon Feb 01, 2010 12:09 pm

Re: Capacity Planning Graphs - values not JSON compliant

Post by FLCUISIT »

Host template is check_ICMP command see attached
You do not have the required permissions to view the files attached to this post.
FLCUISIT
Posts: 93
Joined: Mon Feb 01, 2010 12:09 pm

Re: Capacity Planning Graphs - values not JSON compliant

Post by FLCUISIT »

Service Template for ping is attached
You do not have the required permissions to view the files attached to this post.
User avatar
tgriep
Madmin
Posts: 9190
Joined: Thu Oct 30, 2014 9:02 am

Re: Capacity Planning Graphs - values not JSON compliant

Post by tgriep »

If you are missing the folder /var/lib/mrtg that is a problem.

Lets create it by running the following.

Code: Select all

mkdir /var/lib/mrtg
chmod 755 /var/lib/mrtg/
Then run this command as root and post back any errors.

Code: Select all

LANG=C LC_ALL=C /usr/bin/mrtg /etc/mrtg/mrtg.cfg
Be sure to check out our Knowledgebase for helpful articles and solutions!
FLCUISIT
Posts: 93
Joined: Mon Feb 01, 2010 12:09 pm

Re: Capacity Planning Graphs - values not JSON compliant

Post by FLCUISIT »

Yesterday it would not allow me to navigate to the directory - Today when I tried to create it it says already exists: See results below:

Last login: Mon Mar 16 11:09:25 2015 from hpz220-01.core.fcu
[root@localhost ~]# mkdir /var/lib/mrtg
mkdir: cannot create directory `/var/lib/mrtg': File exists
[root@localhost ~]# chmod 755 /var/lib/mrtg/
[root@localhost ~]# LANG=C LC_ALL=C /usr/bin/mrtg /etc/mrtg/mrtg.cfg
SNMP Error:
no response received
SNMPv1_Session (remote host: "192.168.6.6" [192.168.6.6].161)
community: "flcu"
request ID: 1895712320
PDU bufsize: 8000 bytes
timeout: 2s
retries: 5
backoff: 1)
at /usr/bin/../lib/mrtg2/SNMP_util.pm line 497
SNMPGET Problem for ifInOctets.1 ifOutOctets.1 on [email protected]::::::v4only
at /usr/bin/mrtg line 2330
2015-03-17 11:15:14: WARNING: skipping because at least the query for ifInOctets.1 on 192.168.6.6 did not succeed
2015-03-17 11:15:14: WARNING: no data for ifInOctets&ifOutOctets:[email protected]. Skipping further queries for Host 192.168.6.6 in this round.
SNMP Error:
no response received
SNMPv1_Session (remote host: "192.168.21.37" [192.168.21.37].161)
community: "flcu"
request ID: 444261664
PDU bufsize: 8000 bytes
timeout: 2s
retries: 5
backoff: 1)
at /usr/bin/../lib/mrtg2/SNMP_util.pm line 497
SNMPGET Problem for ifInOctets.2 ifOutOctets.2 on [email protected]::::::v4only
at /usr/bin/mrtg line 2330
2015-03-17 11:15:14: WARNING: skipping because at least the query for ifInOctets.2 on 192.168.21.37 did not succeed
2015-03-17 11:15:14: WARNING: no data for ifInOctets&ifOutOctets:[email protected]. Skipping further queries for Host 192.168.21.37 in this round.
SNMP Error:
no response received
SNMPv1_Session (remote host: "192.168.5.7" [192.168.5.7].161)
community: "flcu"
request ID: 2074887979
PDU bufsize: 8000 bytes
timeout: 2s
retries: 5
backoff: 1)
at /usr/bin/../lib/mrtg2/SNMP_util.pm line 497
SNMPGET Problem for ifInOctets.2 ifOutOctets.2 on [email protected]::::::v4only
at /usr/bin/mrtg line 2330
2015-03-17 11:15:14: WARNING: skipping because at least the query for ifInOctets.2 on 192.168.5.7 did not succeed
2015-03-17 11:15:14: WARNING: no data for ifInOctets&ifOutOctets:[email protected]. Skipping further queries for Host 192.168.5.7 in this round.
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_1][_IN_] ' $target->[39]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_1][_OUT_] ' $target->[39]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_2][_IN_] ' $target->[40]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_2][_OUT_] ' $target->[40]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_3][_IN_] ' $target->[41]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_3][_OUT_] ' $target->[41]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_4][_IN_] ' $target->[42]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_4][_OUT_] ' $target->[42]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_5][_IN_] ' $target->[43]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_5][_OUT_] ' $target->[43]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_6][_IN_] ' $target->[44]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_6][_OUT_] ' $target->[44]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_7][_IN_] ' $target->[45]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_7][_OUT_] ' $target->[45]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_8][_IN_] ' $target->[46]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_8][_OUT_] ' $target->[46]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_9][_IN_] ' $target->[47]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_9][_OUT_] ' $target->[47]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_10][_IN_] ' $target->[48]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_10][_OUT_] ' $target->[48]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_11][_IN_] ' $target->[49]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_11][_OUT_] ' $target->[49]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_12][_IN_] ' $target->[50]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_12][_OUT_] ' $target->[50]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_13][_IN_] ' $target->[51]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_13][_OUT_] ' $target->[51]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_14][_IN_] ' $target->[52]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_14][_OUT_] ' $target->[52]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_15][_IN_] ' $target->[53]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_15][_OUT_] ' $target->[53]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_16][_IN_] ' $target->[54]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_16][_OUT_] ' $target->[54]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_17][_IN_] ' $target->[55]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_17][_OUT_] ' $target->[55]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_18][_IN_] ' $target->[56]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_18][_OUT_] ' $target->[56]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_19][_IN_] ' $target->[57]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_19][_OUT_] ' $target->[57]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_20][_IN_] ' $target->[58]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_20][_OUT_] ' $target->[58]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_21][_IN_] ' $target->[59]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_21][_OUT_] ' $target->[59]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_22][_IN_] ' $target->[60]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_22][_OUT_] ' $target->[60]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_23][_IN_] ' $target->[61]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_23][_OUT_] ' $target->[61]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_24][_IN_] ' $target->[62]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_24][_OUT_] ' $target->[62]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_26][_IN_] ' $target->[63]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_26][_OUT_] ' $target->[63]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_27][_IN_] ' $target->[64]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.6.6_27][_OUT_] ' $target->[64]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.5.7_2][_IN_] ' $target->[84]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.5.7_2][_OUT_] ' $target->[84]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.5.7_11][_IN_] ' $target->[85]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.5.7_11][_OUT_] ' $target->[85]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.5.7_23][_IN_] ' $target->[86]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.5.7_23][_OUT_] ' $target->[86]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.5.7_25][_IN_] ' $target->[87]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.5.7_25][_OUT_] ' $target->[87]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.5.7_26][_IN_] ' $target->[88]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.5.7_26][_OUT_] ' $target->[88]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.5.7_27][_IN_] ' $target->[89]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.5.7_27][_OUT_] ' $target->[89]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.21.37_2][_IN_] ' $target->[516]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.21.37_2][_OUT_] ' $target->[516]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.21.37_3][_IN_] ' $target->[517]{$mode} ' did not eval into defined data
2015-03-17 11:15:39: ERROR: Target[192.168.21.37_3][_OUT_] ' $target->[517]{$mode} ' did not eval into defined data
You have new mail in /var/spool/mail/root
FLCUISIT
Posts: 93
Joined: Mon Feb 01, 2010 12:09 pm

Re: Capacity Planning Graphs - values not JSON compliant

Post by FLCUISIT »

FYI. The IP address errors listed above do not exists on our subnets: 192.168.6.6, 192.168.21.37, 192.168.5.7
User avatar
tgriep
Madmin
Posts: 9190
Joined: Thu Oct 30, 2014 9:02 am

Re: Capacity Planning Graphs - values not JSON compliant

Post by tgriep »

Go to this folder

Code: Select all

cd /etc/mrtg/conf.d
Remote the files with the invalid IP addresses then rerun the following command and continue to fix the errors.

Code: Select all

 LANG=C LC_ALL=C /usr/bin/mrtg /etc/mrtg/mrtg.cfg

Have you gone through this section if the WIKI?
ICMP and Ping Checks Stopped Graphing After XI 2014 Upgrade

Even though is says ICMP and Ping Checks... it could fix your errors.
http://support.nagios.com/wiki/index.ph ... _Displayed
Be sure to check out our Knowledgebase for helpful articles and solutions!
Locked