[mrtg] Won't work after reboot

Steve Shipway s.shipway at auckland.ac.nz
Fri Jun 5 04:43:07 CEST 2015

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 Shipway

 <mailto:s.shipway at auckland.ac.nz> s.shipway at auckland.ac.nz

(GNU Terry Pratchett)


From: Aizad Fauzi [mailto:redsan at gmail.com] 
Sent: Friday, 5 June 2015 2:38 p.m.
To: Steve Shipway
Cc: mrtg at lists.oetiker.ch
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

public at     Name    br-lan  6

public at     Name    eth0    2

public at     Name    eth1    3

public at     Name    lo      1

public at     Name    pppoe-wan       8

public at     Name    wlan0   15

public at     Name    wlan1   16


after reboot and run "mrtg mrtg.conf" the OK file with show wlan0 and wlan1 as Dup




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.oetiker.ch/pipermail/mrtg/attachments/20150605/6e98e523/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 10311 bytes
Desc: not available
URL: <http://lists.oetiker.ch/pipermail/mrtg/attachments/20150605/6e98e523/attachment.bin>

More information about the mrtg mailing list