Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 27 Nov 2008 09:42:50 -0500
From:      Lowell Gilbert <freebsd-questions-local@be-well.ilk.org>
To:        "Davenport\, Steve M" <SDavenpo@mc.utmck.edu>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: SNMPD Consuming Swap Space
Message-ID:  <44zljl9qmt.fsf@lowell-desk.lan>
In-Reply-To: <FB6C2216EEAFF24E888793716DC3FB5C042B6CC4@msexch2.utmck.edu> (Steve M. Davenport's message of "Tue\, 25 Nov 2008 12\:01\:26 -0500")
References:  <FB6C2216EEAFF24E888793716DC3FB5C042B6CC4@msexch2.utmck.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
"Davenport, Steve M" <SDavenpo@mc.utmck.edu> writes:

> Hello,
>  
> I am running snmpd 5.4.1.2 built from a port on 7-Release, hardware is
> Sun V100, 512Mb total memory, 381Mb free. The daemon starts fine. When a
> snmpwalk is done from another system all is well until the interface
> table and then I see:
>  
> interfaces.ifTable.ifEntry.ifSpeed.1 : Gauge32: 10000000
> interfaces.ifTable.ifEntry.ifSpeed.2 : Gauge32: 0
> interfaces.ifTable.ifEntry.ifSpeed.3 : Gauge32: 0
> snmpwalk: No response arrived before timeout.
>
> After the timeout happens, looking at "swapinfo -k" shows that swap
> space is continually consumed until empty at which point the snmpd
> daemon is stopped:
>  
> fbsdh# swap_pager: out of swap space
> swap_pager_getswapspace(16): failed
> Nov 25 11:44:08 fbsdh kernel: pid 84674 (snmpd), uid 0, was killed: out
> of swap space
>  
> Now the swap space is freeded:
> fbsdh# swapinfo -k
> Device          1K-blocks     Used    Avail Capacity
> /dev/ad0b         2099160    26456  2072704     1%
>  
> Has anyone seen this issue or know of a solution. 

Since you're running the SNMP daemon from a port, not the one from the
base system, you may need developers' assistance for this sort of bug.
Problems like this are often caused by wraparound bugs or infinite loops
in my experience, although there are lots of other possibilities.  If
you can get a stack traceback when it crashes, that will is quite likely
to give a solid clue.

-- 
Lowell Gilbert, embedded/networking software engineer, Boston area
		http://be-well.ilk.org/~lowell/



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44zljl9qmt.fsf>