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 98BDE13888F for ; Fri, 9 Oct 2015 14:16:16 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B4ABD21C012; Fri, 9 Oct 2015 14:15:58 +0000 (UTC) Received: from mail-qk0-f178.google.com (mail-qk0-f178.google.com [209.85.220.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 9F33321C003 for ; Fri, 9 Oct 2015 14:15:57 +0000 (UTC) Received: by qkht68 with SMTP id t68so32886558qkh.3 for ; Fri, 09 Oct 2015 07:15:56 -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=ljEZJ8ORJbvOtwj3RlLWwplptm3t2gLxo/mH+uNEU44=; b=PZrKfBk4AB3NlxCKdpk6OFz0NvOhx9w6+NLIxDmbutXnfrU+BjP8D2jsJp5RN4fBm5 vkpFCzszhRXw6WlMUZ9VHQrGOCvKgcMV4heIf4AUn2EDqXM6eGSxRKMUWn5TeqWLsX8K pn8y0rwlfgm3TmWRRksTMunL+W0QhIzz8hGkuN28kBSynffkfrm8syr8X65x3P4+pkuc f48Y4o/wANjwM/oug5F7J6oUw1xYk9RaL+DV3VPGG3JwvHNFtYFZa/oXM+FYw+qOCQpv WB8bl0I717IoUZiArFMhFqUB3KI3nXoX7BWRxBN1xqJ+hDagVfpqdI81ozTY/UduSD61 S8Aw== 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.214.80 with SMTP id t77mr15237203qki.101.1444400156614; Fri, 09 Oct 2015 07:15:56 -0700 (PDT) Received: by 10.140.100.241 with HTTP; Fri, 9 Oct 2015 07:15:56 -0700 (PDT) In-Reply-To: <561566EE.9000507@gmail.com> References: <5613003F.5020303@iinet.net.au> <5613073B.5090600@gmail.com> <56152AAD.5030003@gmail.com> <561566EE.9000507@gmail.com> Date: Fri, 9 Oct 2015 07:15:56 -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: 5c8bdbcb-585b-4aee-8b25-9441b8db2d18 X-Archives-Hash: 75041367a453db8fd5428455efc1677b > 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 Many thanks Alan! - Grant