Date: Tue, 27 Oct 2009 10:54:35 -0300 From: Paul Halliday <paul.halliday@gmail.com> To: questions@freebsd.org Subject: Re: Looking for troubleshooting tips. Message-ID: <2dab70a30910270654j79c3627bp2f2af88894dce2f2@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
I shift deleted my inbox and lost all of the original replies :( anyway... I have another sensor that just started to exhibit this same behavior. This time though, I have some more info: swap_pager_getswapspace(4): failed swap_pager_getswapspace(16): failed swap_pager_getswapspace(16): failed swap_pager_getswapspace(2): failed pid 75157 (flow-report), uid 1001, was killed: out of swap space What made me notice this time was the zabbix (http://www.zabbix.com/) agent on this host kept bumping online/offline. So it looks like we are loaded enough to affect other processes as well. Is this just a matter of adding more ram? Or do I increase the swap space? Or is there another issue here; I have never ran out of swap space before? Thanks. On Wed, Oct 21, 2009 at 9:58 AM, Paul Halliday <paul.halli...@gmail.com>wrote: > I use Freebsd as the base for my network monitoring sensors. These > machines run a netflow probe, act as a netflow collector and spool > full content data from a snort process FIFO that is bound to a span > port. During peak hours this can be 100MB saturated, its connected to > a GB intel NIC on the box (there is a separate uplink). > > In the background numerous little scripts run to produce summary data. > The basic template for these systems has been the same for the past 4 > years and things have worked great. Recently, one of these machines > started to become a little laggy and I can't seem to identify the > issue. > > This system has always seen a lot of packet loss, I expect this though > as it is a busy site but this has never affected its performance. Can > an overloaded NIC cause serious performance issues like those I am > seeing? > > This is a recent top: > > last pid: 98870; load averages: 1.54, 1.41, 1.31 up 1+01:57:10 > 11:50:24 > 142 processes: 2 running, 139 sleeping, 1 zombie > CPU states: 30.9% user, 0.0% nice, 15.0% system, 1.7% interrupt, 52.4% > idle > Mem: 450M Active, 328M Inact, 168M Wired, 33M Cache, 110M Buf, 3700K Free > Swap: 2048M Total, 5112K Used, 2043M Free > > 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 > > To be honest, I don't know which counters are important. Is there > anything specific I should be concentrating on to determine the cause? > > Thanks. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2dab70a30910270654j79c3627bp2f2af88894dce2f2>