[mrtg] Re: MRTG/spikes after router reboot with fix/patch for 2.9.29

Michael Markstaller mm at elabnet.de
Mon Apr 19 10:23:24 MEST 2004


Jeremy,

I'm also replying to the list in case there're some others interested..
Unfortunately I never received any feedback, besides few "thanks"-mails from some users also fed up with spikes. 
I've made me a local DEB with my patched 2.9.29 running happy with it, without ever seeing spikes again.
As the rest of the MRTG-world doesn't seem to care about these spikes, I haven't created any patch for newer 2.10 versions. Although I'm curious why other users don't get mad with these spikes..

What I already wrote: The problem is, that MRTG/RRDTool simply "guesses" a counter-wrap occured when an snmp-agent is rebooted between two polls. Seems simple to me looking on the uptime, because if at least one poll fails (agent unreachable) you also won't get spikes and that is what my patch enforces, I even made it configurable and not-default in case anybody is missing the spikes in their graphs ;) 
The intention in creating a configurable option for this patch was indeed to have it included in the official mrtg. All other "workarounds" discussed the last years with maxbytes etc. are reducing the problem somehow but do not eliminate it.
All the details should've been in my inital post:
http://www.ee.ethz.ch/~slist/mrtg/msg25867.html

Anyway, if there's some interest I'll look into 2.10 and create a new patch the next days. If there isn't changed too much it should be quite simple to adjust for 2.10.13

Michael

-----Original Message-----
From: Jeremy Chadwick [mailto:freebsd at jdc.parodius.com]
Sent: Sunday, April 18, 2004 9:08 PM
To: Michael Markstaller
Subject: Re: MRTG/spikes after router reboot with fix/patch for 2.9.29


Michael,

I was curious -- did your patch ever get officially committed?

This issue (re: spikes) has continued to haunt all administrators
across the world since as early as 1999.  
...

If your patch didn't get committed: we're now up to mrtg 2.10.13, and
still no fix for this problem.  This angers me immensely.

Let me know if you have a patch for 2.10.13, as I'd love to submit it
to the FreeBSD ports tree so that people could at least solve this
problem in that branch.

Thanks!

-- 
| Jeremy Chadwick                                 jdc at parodius.com |
| Parodius Networking                        http://www.parodius.com/ |
| UNIX Systems Administrator                   Mountain View, CA, USA |
| Making life hard for others since 1977.                             |

--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
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



More information about the mrtg mailing list