I've noticed something similar: Had a config with multiple snmp and external script configs.
If one of the external script configs didn't work (ie host down) none of the external script configs would work. I did have forks configured but didn't think to remove it I just put them each in their own config instead. Not sure which version of MRTG either 2.9.25 or 2.9.7 -----Original Message----- From: Chris Robb [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 15, 2003 5:32 PM To: [EMAIL PROTECTED] Subject: [mrtg] Re: [rrd-users] MRTG RRD collector failing on one host [changing lists because this looks to be an MRTG issue that might affect others] I did some further troubleshooting on the problem I detail below. It appears to be related to the way RRD forks, somehow. I did a really scaled down config that monitored only three interfaces with traditional MRTG logfile format (no RRD) When giving the first interface in the config a bogus IP address to match against, it would fail (as expected), but it would also cause the next interface to fail, with the 3rd interface successfully monitored. I started pulling things out of the config and it looks like getting rid of the Forks directive took care of it. Anyone else noticed this? -Chris Chris Robb Indiana University Global NOC Abilene/TransPAC Network Engineer [EMAIL PROTECTED] Desk: 812-855-8604 Cell: 812-325-8199 On Tue, 14 Jan 2003, Chris Robb wrote: > > I've got one barrier to rolling out our network's new RRD-based collection > and turning down the backup MRTG logfile-based collectors: when using MRTG > to collect the data into the RRDs, failure to collect on one host in the > config file stops processing for the entire config. This is a problem > when, say, and interface moves or an IP address changes. With traditional > MRTG, if that interface can't be collected against, it's values aren't > written, but the other configured collections are populated. Not so with > MRTG, using RRD as the backend. If one collection fails, all subsequently > configured collections also fail. > > Is there any way around this or is this a bug? > > -Chris > > Chris Robb > Indiana University Global NOC > Abilene/TransPAC Network Engineer > [EMAIL PROTECTED] Desk: 812-855-8604 Cell: 812-325-8199 > > ---------- Forwarded message ---------- > Date: Tue, 14 Jan 2003 17:09:09 -0500 > From: Cron Daemon <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Cron <[EMAIL PROTECTED]> /usr/local/mrtg/bin/mrtg > /home/monitoring/rrd-monitors/abilene/etc/abilene-mrtg.cfg > > WARNING: Could not match host:'[EMAIL PROTECTED]:::::2' ref:'Ip' key:'205.171.4.130' > WARNING: no data for ifHCInOctets&ifHCOutOctets:[EMAIL PROTECTED] Skipping further queries for Host 198.32.8.251 in this round. > ERROR: Target[dnvr-qwest-bits][_IN_] ' $$target[224]{$mode} ' did not eval into defined data > ERROR: Target[dnvr-qwest-bits][_OUT_] ' $$target[224]{$mode} ' did not eval into defined data > ERROR: Target[dnvr-qwest-pkts][_IN_] ' $$target[225]{$mode} ' did not eval into defined data > ERROR: Target[dnvr-qwest-pkts][_OUT_] ' $$target[225]{$mode} ' did not eval into defined data > ERROR: Target[dnvr-qwest-errors][_IN_] ' $$target[226]{$mode} ' did not eval into defined data > ERROR: Target[dnvr-qwest-errors][_OUT_] ' $$target[226]{$mode} ' did not eval into defined data > ERROR: Target[dnvr-arizonastate-int-bits][_IN_] ' $$target[227]{$mode} ' did not eval into defined data > ERROR: Target[dnvr-arizonastate-int-bits][_OUT_] ' $$target[227]{$mode} ' did not eval into defined data > ERROR: Target[dnvr-arizonastate-int-pkts][_IN_] ' $$target[228]{$mode} ' did not eval into defined data > ERROR: Target[dnvr-arizonastate-int-pkts][_OUT_] ' $$target[228]{$mode} ' did not eval into defined data > ERROR: Target[dnvr-arizonastate-int-errors][_IN_] ' $$target[229]{$mode} ' did not eval into defined data > ERROR: Target[dnvr-arizonastate-int-errors][_OUT_] ' $$target[229]{$mode} ' did not eval into defined data > ERROR: Target[dnvr-arizonastate-bits][_IN_] ' $$target[230]{$mode} ' did not eval into defined data > ERROR: Target[dnvr-arizonastate-bits][_OUT_] ' $$target[230]{$mode} ' did not eval into defined data > ERROR: Target[dnvr-unm-bits][_IN_] ' $$target[231]{$mode} ' did not eval into defined data > ERROR: Target[dnvr-unm-bits][_OUT_] ' $$target[231]{$mode} ' did not eval into defined data > ERROR: Target[dnvr-unm-pkts][_IN_] ' $$target[232]{$mode} ' did not eval into defined data > ERROR: Target[dnvr-unm-pkts][_OUT_] ' $$target[232]{$mode} ' did not eval into defined data > ERROR: Target[dnvr-unm-errors][_IN_] ' $$target[233]{$mode} ' did not eval into defined data > ERROR: Target[dnvr-unm-errors][_OUT_] ' $$target[233]{$mode} ' did not eval into defined data > > > > > -- > Unsubscribe mailto:[EMAIL PROTECTED] > Help mailto:[EMAIL PROTECTED] > Archive http://www.ee.ethz.ch/~slist/rrd-users > WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi > > > -- Unsubscribe mailto:[EMAIL PROTECTED] Archive http://www.ee.ethz.ch/~slist/mrtg FAQ http://faq.mrtg.org Homepage http://www.mrtg.org WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi -- Unsubscribe mailto:[EMAIL PROTECTED] Archive http://www.ee.ethz.ch/~slist/mrtg FAQ http://faq.mrtg.org Homepage http://www.mrtg.org WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi
