From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 699A813888F for ; Wed, 7 Oct 2015 12:58:20 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7F0AD21C00E; Wed, 7 Oct 2015 12:58:10 +0000 (UTC) Received: from mail-qk0-f172.google.com (mail-qk0-f172.google.com [209.85.220.172]) (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 57CBCE07FA for ; Wed, 7 Oct 2015 12:58:09 +0000 (UTC) Received: by qkas79 with SMTP id s79so5176331qka.0 for ; Wed, 07 Oct 2015 05:58:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=1XYT09zyq7hIL9Yw4KDh8QQaUiVaAxwCD1mfGl52pYQ=; b=dmDHqMbZzwpKEm1f7dyDzhp+92oJ0pVpeZnWjrLRYAY0IiCPDg4VHFpfHDsvYVSiMi S2FsYc+s9RgpzOvDSmpoSiWUABPqf0c2SOx0Aa6go5o5MfCJxzGIE58KV4L3AM2IAYy3 P92VPRAZj/vEyWXQgfTA8Gy8wVqR6M1UyGP0gHSmhQZPT3TMNLgjM0DrVk3ymi9eOByc NrQdMxO9ppC8Uzpf4/vQosaRtmJ1w1KLecn0B4G2HYYrH2GZAUIuc57xR9uqJMlX+wu6 QSIzLGh0z1TKhm1iI4Qk8zIkkIKhB6+YAPmlpByhmbISy8rEhILZ8DJPZw6dlRitN2so DwEQ== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.55.198.20 with SMTP id b20mr1157152qkj.35.1444222688310; Wed, 07 Oct 2015 05:58:08 -0700 (PDT) Received: by 10.140.100.241 with HTTP; Wed, 7 Oct 2015 05:58:08 -0700 (PDT) In-Reply-To: <5613073B.5090600@gmail.com> References: <5613003F.5020303@iinet.net.au> <5613073B.5090600@gmail.com> Date: Wed, 7 Oct 2015 05:58:08 -0700 Message-ID: Subject: Re: [gentoo-user] strange TCP timeout errors From: Grant To: Gentoo mailing list Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: d32cf9b8-b859-4a27-a19b-3ad9a0d766a9 X-Archives-Hash: eb2c6b2da52b618e9e0994231a7e94b3 >>> 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? - Grant