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 6B14413888F for ; Mon, 5 Oct 2015 23:27:38 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9402C21C020; Mon, 5 Oct 2015 23:27:29 +0000 (UTC) Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) (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 6B33DE079D for ; Mon, 5 Oct 2015 23:27:28 +0000 (UTC) Received: by wicge5 with SMTP id ge5so142477943wic.0 for ; Mon, 05 Oct 2015 16:27:27 -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=9a0cPG5Dbj0ykrnv6EDqD72/2AWwe9y1i0LFQHImuZI=; b=KnqgfVqb/I1axvOPWDU8Cqy9CvvmvWwXkMlVlZ07eqaiFk5O/WQH723VglFJ5sj6J2 N4XmBEj+WUatKHEtYAFubVKTjfdvJQ3XOQVTPC36+CmGW2J5AtUfufU/1T1tSS/TZg9k G/7Iaykd99ZNmzspTgKbSAyEMw5K5e+RGzFsAtBoqtmv8f2W/p9IYYYWoGMPhs7Zl0Fe 7U6R7j6FedagqxqtvbfwVbYmrBdhtVrgKynGBHrUFATiaDD6I2E53KiG7Nl0ACBvgdpl Dtq3eu9M3iyGsG60gkn48Fo1E+GKZQrXpsGV90N4xllT53jgPnASjhpWDMI7PkXjjK9u 83Tw== X-Received: by 10.194.92.166 with SMTP id cn6mr32995425wjb.6.1444087647148; Mon, 05 Oct 2015 16:27:27 -0700 (PDT) Received: from [172.20.0.41] ([105.210.210.164]) by smtp.googlemail.com with ESMTPSA id ew2sm17035069wic.20.2015.10.05.16.27.25 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 05 Oct 2015 16:27:26 -0700 (PDT) Subject: Re: [gentoo-user] strange TCP timeout errors To: gentoo-user@lists.gentoo.org References: <5613003F.5020303@iinet.net.au> From: Alan McKinnon Message-ID: <5613073B.5090600@gmail.com> Date: Tue, 6 Oct 2015 01:26:51 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 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 In-Reply-To: <5613003F.5020303@iinet.net.au> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 3245be8f-9701-43d6-972f-63603b19583d X-Archives-Hash: 68521ddeace8ccfc7268bda5259c43df On 06/10/2015 00:57, Bill Kenworthy wrote: > On 06/10/15 01:35, 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 > 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. -- Alan McKinnon alan.mckinnon@gmail.com