ports/141910: sysutils/munin-node bug with reset stat for 'netstat' plugin

Ben Jackson ben at ben.com
Wed Dec 23 01:20:01 UTC 2009


>Number:         141910
>Category:       ports
>Synopsis:       sysutils/munin-node bug with reset stat for 'netstat' plugin
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Dec 23 01:20:00 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Ben Jackson
>Release:        FreeBSD 7.2-STABLE amd64
>Organization:
>Environment:
System: FreeBSD kronos.home.ben.com 7.2-STABLE FreeBSD 7.2-STABLE #2: Tue Sep 15 22:53:16 PDT 2009 bjj at kronos.home.ben.com:/usr/obj/usr/src/sys/GENERIC amd64


In the 'netstat' plugin there's an awk script to extract the 'reset'
count from netstat -s.  Unfortunately there are two lines with 'reset'
and when both of those are reported it confuses some other part of the
stats gathering and produces an ever growing graph line:

kronos /usr/local/share/munin/plugins # /usr/bin/netstat -s | grep reset
                6645 reset
                0 stream reset timers fired

I just threw in a '$' so the pattern is 'reset$':

kronos /usr/local/share/munin/plugins # tail -2 netstat
/usr/bin/netstat -s | awk '/connection requests/ { print "active.value " $1 } /connection accepts/ { print "passive.value " $1 } /bad connection/ { print "failed.value " $1 } /reset$/ { print "resets.value " $1 } /connections established/ { print "established.value " $1 }'

>Description:
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the freebsd-ports-bugs mailing list