When you reboot, the interfaces are being reenumerated – so they get a different number.
When MRTG probes the device, it finds them but under a different number to the one given in the cache file, and then does not know which to use (hence the ‘dup’). So, delete the mrtg.ok file, then run MRTG again. It will recreate the .ok file (this is the interface identifier cache file) using the current enumeration, and all should work. Steve Steve Shipway <mailto:[email protected]> [email protected] (GNU Terry Pratchett) From: Aizad Fauzi [mailto:[email protected]] Sent: Friday, 5 June 2015 2:38 p.m. To: Steve Shipway Cc: [email protected] Subject: Re: [FORGED] [mrtg] Won't work after reboot Hi Steve, The /usr/sbin/mrtg is run by crontab. Even I run it manually after reboot, it will always shows the error. This is my mrtg.ok file. This is setup from scratch [email protected]_ Name br-lan 6 [email protected]_ Name eth0 2 [email protected]_ Name eth1 3 [email protected]_ Name lo 1 [email protected]_ Name pppoe-wan 8 [email protected]_ Name wlan0 15 [email protected]_ Name wlan1 16 after reboot and run "mrtg mrtg.conf" the OK file with show wlan0 and wlan1 as Dup Thanks.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ mrtg mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/mrtg
