[mrtg] Same config, differing results...
Christian Arnaut
n8tgc at msn.com
Wed Nov 19 20:30:54 CET 2014
Thank you Wrolf, regarding the 'gauge vs counter' configuration. I have modified the cfg as shown below. I left the gauge option enabled globally as I have other devices monitored on the device (disk space, CPU load, etc.), But 'counter' is enabled locally for that interface.
Previously, I had tried deleting the log file entirely for that interface. The same problem recurred. So, this time I took your advice and copied the log file from the 'working' test server to the 'faulty' production server. Sadly, I'm back to square one. From the moment the log file was copied, moving forward, the saw-tooth line began growing again.
Ug!
~Christian
EnableIPv6: no
Options[_]: gaugeWorkDir: /var/www/mrtg/user
Target[user-eth1]: 12:xxxxpublic at 192.168.0.77:
SetEnv[user-eth1]: MRTG_INT_IP="192.168.3.55" MRTG_INT_DESCR="Intel(R)-Centrino(R)-Advanced-N-6205"
MaxBytes[user-eth1]: 16250000
Options[_]: bits, counter
Title[user-eth1]: Traffic Analysis for user -- WiFi Connection
<snip>
From: Wrolf.Courtney at mtahq.org
To: mrtg at lists.oetiker.ch
Date: Wed, 19 Nov 2014 17:05:43 +0000
Subject: Re: [mrtg] Same config, differing results...
Are you sure you want it to be a guage value – I believe the default is counter.
You may want to copy over the .log or .rrd file from the working box.
Wrolf
From: mrtg [mailto:mrtg-bounces+wrolf.courtney=mtahq.org at lists.oetiker.ch]
On Behalf Of Christian Arnaut
Sent: Wednesday, November 19, 2014 11:46 AM
To: mrtg at lists.oetiker.ch
Subject: [mrtg] Same config, differing results...
I have a test (virtual) Debian server that I use for testing new applications, configs, etc. before they are deployed to my production Debian server. MRTG is amongst the apps that I use the virtual server for.
Currently I am using the identical cfg file to monitor bandwidth on a Windows 7 wireless network adaptor on my laptop. On the test server, the graphed results are exactly what I intended. However, the exact cfg file on the production server
produces dramatically different results. On the production environment, the graph is a continually growing saw-tooth graph that almost appears to be showing the uptime of the interface. If, after a few hours, I turn off the wireless interface and turn it back
on, the graph drops to zero and the saw-tooth begins again. Conversely, on the test server, the bandwidth logs continue to be logged and displayed exactly as intended.
Two servers, both running the same OS (Debian 7.7), both running the same version of MRTG (2.7.14) and both running the same config for the intended interface (below). What am I possibly missing?
Thanks, in advance, for any suggestions!
~Christian
(cfg file below)
EnableIPv6: no
Options[_]: gauge
WorkDir: /var/www/mrtg/user
Target[user-eth1]: 12:xxxxpublic at 192.168.0.77:
SetEnv[user-eth1]: MRTG_INT_IP="192.168.3.55" MRTG_INT_DESCR="Intel(R)-Centrino(R)-Advanced-N-6205"
MaxBytes[user-eth1]: 16250000
Options[_]: bits
Title[user-eth1]: Traffic Analysis for user -- WiFi Connection
PageTop[user-eth1]: <h1>Traffic Analysis for user -- WiFi Connection</h1>
<div id="sysdetails">
<table>
<tr>
<td>System:</td>
<td>user-2519.xxxx.local in </td>
</tr>
<tr>
<td>Maintainer:</td>
<td>user at xxxx.org</td>
</tr>
<tr>
<td>Description:</td>
<td>Intel(R)-Centrino(R)-Advanced-N-6205 </td>
</tr>
# <tr>
# <td>ifType:</td>
# <td>Radio Spread Spectrum (802.11) (71)</td>
# </tr>
<tr>
<td>ifName:</td>
<td>WiFi Connection</td>
</tr>
<tr>
<td>Max Speed:</td>
<td>104.0 Mbits/s</td>
</tr>
<tr>
<td>Ip:</td>
<td>192.168.3.55 (user-2519.xxxx.local)</td>
</tr>
</table>
</div>
_______________________________________________
mrtg mailing list
mrtg at lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/mrtg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.oetiker.ch/pipermail/mrtg/attachments/20141119/f11751ec/attachment.html>
More information about the mrtg
mailing list