From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-user+bounces-167903-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
by finch.gentoo.org (Postfix) with ESMTP id 267CC13888F
for <garchives@archives.gentoo.org>; Wed, 7 Oct 2015 22:26:13 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 94EA521C01F;
Wed, 7 Oct 2015 22:26:05 +0000 (UTC)
Received: from mail-wi0-f181.google.com (mail-wi0-f181.google.com [209.85.212.181])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id 5E01AE084D
for <gentoo-user@lists.gentoo.org>; Wed, 7 Oct 2015 22:26:04 +0000 (UTC)
Received: by wicfx3 with SMTP id fx3so3704598wic.1
for <gentoo-user@lists.gentoo.org>; Wed, 07 Oct 2015 15:26:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=subject:to:references:from:message-id:date:user-agent:mime-version
:in-reply-to:content-type:content-transfer-encoding;
bh=JiDmLOqR/Aj8XhM+kL5W1m+eCJxatAn3egZQR6W8768=;
b=p4rr/agJrZydrE/RfhLBueBD38ooCuunFvvRLoJV6r7cwREu+LmoO5GQNfdsNrexF0
wBULAdDS3f1i8lhifROIPa7F7omEAOCdKiP8+WOu7n0ARhmd8xuf1bHJoPYZ+iGqpIrA
+pOLfze/K4ESyIUN1XySU9QeLFyXdkL4m0via2bYZUjcycJd6lnUtBCo9s1I8BBie1R+
1xCggec18SNLQoqFl5MQW/8vYDSrJOdxL9TVQ2Ksig0AyG0CI8ebNlee5nj3sia847Ha
EbLg97WIAWSStFlE8oocW1Vyoj/d/DzgpTtbxa3lUF5NuDkDH9hh1wXwuXyHroj6su4Q
FCWw==
X-Received: by 10.180.103.2 with SMTP id fs2mr82091wib.9.1444256763097;
Wed, 07 Oct 2015 15:26:03 -0700 (PDT)
Received: from [172.20.0.41] ([105.210.54.110])
by smtp.googlemail.com with ESMTPSA id r4sm4425389wia.19.2015.10.07.15.26.01
for <gentoo-user@lists.gentoo.org>
(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Wed, 07 Oct 2015 15:26:02 -0700 (PDT)
Subject: Re: [gentoo-user] strange TCP timeout errors
To: gentoo-user@lists.gentoo.org
References: <CAN0CFw36pf6rHuqo-88-t6PnrO=9S5ySizERaVF7CzZqREDYsA@mail.gmail.com>
<5613003F.5020303@iinet.net.au> <5613073B.5090600@gmail.com>
<CAN0CFw25m1FtbeJ_5jp1Dsy-0k01-WNjOFp0GoQe9VZBEBsJTQ@mail.gmail.com>
<56152AAD.5030003@gmail.com>
<CAN0CFw1gK87M_c18uht0yv1aohjjs51q=0Pc6J2DhPT3ii+RLg@mail.gmail.com>
<561566EE.9000507@gmail.com>
<588564942-1444246926-cardhu_decombobulator_blackberry.rim.net-2145807130-@b25.c2.bise6.blackberry>
From: Alan McKinnon <alan.mckinnon@gmail.com>
Message-ID: <56159BD6.5000500@gmail.com>
Date: Thu, 8 Oct 2015 00:25:26 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
Thunderbird/38.3.0
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
In-Reply-To: <588564942-1444246926-cardhu_decombobulator_blackberry.rim.net-2145807130-@b25.c2.bise6.blackberry>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Archives-Salt: 8cc7242e-4454-4901-8dce-a962fd282f7e
X-Archives-Hash: 8f18a95408f553efc877ea6d9338545c
On 07/10/2015 21:42, brettrsears@gmail.com wrote:
> YyyyYYuIIIIIU
> Sent from my Verizon Wireless BlackBerry
Hmmmmmmmmmmmmmm, interesting reply. I'm wondering if it has something to
do with:
1. verizon
2. dodgy 3g
3. crapberry. oops, sorry: blackberry
Or maybe it's because y, u and i are in a row on the keyboard, shift and
enter are adjacent, and you have a over-friendly cat?
:-)
>
> -----Original Message-----
> From: Alan McKinnon <alan.mckinnon@gmail.com>
> Date: Wed, 7 Oct 2015 20:39:42
> To: <gentoo-user@lists.gentoo.org>
> Reply-to: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] strange TCP timeout errors
>
> On 07/10/2015 17:55, Grant wrote:
>>>>>>> I've attached a PNG from Munin showing the TCP timeout errors on my
>>>>>>> Gentoo server over the past month. The data is expressed in timeouts
>>>>>>> per second and that rate is shown to be steadily increasing over the
>>>>>>> past month. That seems strange to me. Munin doesn't show any other
>>>>>>> data point increasing like this over the time period. Any ideas?
>>>>>>>
>>>>>>> - Grant
>>>>>>>
>>>>>>
>>>>>> weird - does it reset on an interface restart or reboot?
>>>>>
>>>>> this would be my test #1
>>>>
>>>>
>>>> I rebooted and the rate of errors has dropped off to almost nothing.
>>>>
>>>>
>>>>>> Can you verify its not an artefact within munin (how?)
>>>>>
>>>>> In theory, a misconfigured graph can do this. Munin can draw many
>>>>> different types of graph, including cumulative values. Even for a data
>>>>> type like this which is X events per unit time, if you tell munin to add
>>>>> them all up, it will do so and graph it.
>>>>>
>>>>> Qucik test is to look at the graph config.
>>>>
>>>>
>>>> This graph lives in the "network" section of the munin web interface.
>>>> There is no matching section in /etc/munin/plugin-conf.d/munin-node so
>>>> it should be be using the default config.
>>>>
>>>> Any ideas based on this new info?
>>>
>>> A few :-)
>>>
>>>
>>> I can't find the plugin that delivers that graph though. Maybe I just
>>> don't have it, maybe it comes from contrib/
>>>
>>> What's your USE for munin?
>>
>>
>> USE="apache cgi http mysql ssl syslog -asterisk -dhcpd -doc -ipmi
>> -ipv6 -irc -java -memcached -minimal -postgres (-selinux) {-test}"
>>
>>
>>> What do you have in "ls -al /etc/munin/plugins/" ?
>
>
> It's as I thought - your data is accurate but rrd has been given a
> completely wrong method to derive the graphs.
>
> Munin graphs for section "Network" do not have to be in a file called
> "network" - it's just a category and the plugin defines what web-page
> section it must be in. In your case, the relevant plugin is
> netstat_multi which doesn't often get installed. It's data source is
> "netstat -s" so grep that output for "timeout" to see it.
>
> Timeouts are cumulative counters, they do not get less till they wrap
> around. So to scale them, the plugin gets the rrd file to subtract
> previous reading from current reading and divide by the time interval to
> get the timeouts/sec. This is all done inside rrd when the data files
> are updated (it's quite a lot of magic)
>
> That plugin sets the graph type to DERIVE
> (/etc/munin/plugins/netstat_multi around line 190. I feel it should be
> GAUGE or COUNTER.
>
> The proper reference on rrd is
> http://oss.oetiker.ch/rrdtool/doc/rrdcreate.en.html
> and the munin docs are
> https://munin.readthedocs.org/en/latest/index.html
>
> You must edit the plugin file and IIRC recreate the rrd, you will lose
> all past info (can't be helped).
>
>
> [snip ls output]
>
>
>> P.S. Any other good plugins you'd recommend?
>
> http://gallery.munin-monitoring.org/
>
> Monitoring is highly site-specific so recommendations aren't usually
> worth much, but that gallery has LOTS of contributed plugins
>
--
Alan McKinnon
alan.mckinnon@gmail.com