Page 2 of 2

Re: Errors when running LANG=C LC_ALL=C /usr/bin/mrtg /etc/m

Posted: Wed Jul 09, 2014 4:19 am
by vijilants
This problem appear to be a moving target. I ran the command today and see output below:

Code: Select all

[root@londnms1]# LANG=C LC_ALL=C /usr/bin/mrtg /etc/mrtg/mrtg.cfg –check
2014-07-09 10:16:18: ERROR: Target[10.40.1.249_13][_IN_] ' $target->[77]{$mode} ' did not eval into defined data
2014-07-09 10:16:18: ERROR: Target[10.40.1.249_13][_OUT_] ' $target->[77]{$mode} ' did not eval into defined data
2014-07-09 10:16:18: ERROR: Target[10.40.1.249_17][_IN_] ' $target->[80]{$mode} ' did not eval into defined data
2014-07-09 10:16:18: ERROR: Target[10.40.1.249_17][_OUT_] ' $target->[80]{$mode} ' did not eval into defined data
2014-07-09 10:16:18: ERROR: Target[10.40.1.249_18][_IN_] ' $target->[81]{$mode} ' did not eval into defined data
2014-07-09 10:16:18: ERROR: Target[10.40.1.249_18][_OUT_] ' $target->[81]{$mode} ' did not eval into defined data
2014-07-09 10:16:18: ERROR: Target[10.40.1.249_19][_IN_] ' $target->[82]{$mode} ' did not eval into defined data
2014-07-09 10:16:18: ERROR: Target[10.40.1.249_19][_OUT_] ' $target->[82]{$mode} ' did not eval into defined data
2014-07-09 10:16:18: ERROR: Target[10.40.1.249_20][_IN_] ' $target->[83]{$mode} ' did not eval into defined data
2014-07-09 10:16:18: ERROR: Target[10.40.1.249_20][_OUT_] ' $target->[83]{$mode} ' did not eval into defined data
2014-07-09 10:16:18: ERROR: Target[10.40.1.249_21][_IN_] ' $target->[84]{$mode} ' did not eval into defined data
2014-07-09 10:16:18: ERROR: Target[10.40.1.249_21][_OUT_] ' $target->[84]{$mode} ' did not eval into defined data
[root@londnms1 # 
I have emailed you the service file as requested.

Thanks

Re: Errors when running LANG=C LC_ALL=C /usr/bin/mrtg /etc/m

Posted: Wed Jul 09, 2014 4:50 pm
by slansing
Well, it is likely occurring on multiple sets of devices, especially if it is the same hardware. Can you get us a copy of those flat files? At least of the one you just showed? You would not happen to be able to correlate if those switches/firewalls were down during the time you ran the check? Or if those ports were administratively down if they actually exist and are not vlans, etc?