2015-10-27 17:41:05: ERROR: Target[IP_369100078][_IN_] ' $target->[22]{$mode} ' did not eval into defined data
2015-10-27 17:41:05: ERROR: Target[IP_369100078][_OUT_] ' $target->[22]{$mode} ' did not eval into defined data
2015-10-27 17:41:05: ERROR: Target[IP2_805306369][_IN_] ' $target->[808]{$mode} ' did not eval into defined data
2015-10-27 17:41:05: ERROR: Target[IP2_805306369][_OUT_] ' $target->[808]{$mode} ' did not eval into defined data
2015-10-27 17:41:05: ERROR: Target[IP2_1073741825][_IN_] ' $target->[809]{$mode} ' did not eval into defined data
2015-10-27 17:41:05: ERROR: Target[IP2_1073741825][_OUT_] ' $target->[809]{$mode} ' did not eval into defined data
2015-10-27 17:41:05: ERROR: Target[IP2_1073741826][_IN_] ' $target->[810]{$mode} ' did not eval into defined data
2015-10-27 17:41:05: ERROR: Target[IP2_1073741826][_OUT_] ' $target->[810]{$mode} ' did not eval into defined data
2015-10-27 17:41:05: ERROR: Target[IP2_1073741828][_IN_] ' $target->[811]{$mode} ' did not eval into defined data
Most annoyingly comment out each port in the config file it is complaining about ... it's about 37 lines per port. Or simply delete the port from the config file.
The configuration files for MRTG are created with the program cfgmaker. While you may have selected to only monitor a handful of ports from your network device when using the wizard, MRTG will collect data from all the interfaces.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
This is annoying. So if there is a device with 4 ports that I want to check, but the wizard finds 400, it will commit all 400 to configuration for MRTG to check? This could add a lot of unnecessary load to the XI box checking all the ports that aren't in XI.
