Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 2 Feb 2011 20:10:12 GMT
From:      Mark Boolootian <mark.boolootian@gmail.com>
To:        freebsd-net@FreeBSD.org
Subject:   Re: kern/146792: [flowtable] flowcleaner 100% cpu's core load
Message-ID:  <201102022010.p12KACV5039592@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/146792; it has been noted by GNATS.

From: Mark Boolootian <mark.boolootian@gmail.com>
To: bug-followup@FreeBSD.org, niko@gtelecom.ru
Cc:  
Subject: Re: kern/146792: [flowtable] flowcleaner 100% cpu's core load
Date: Wed, 2 Feb 2011 11:37:16 -0800

 --00163630f77dc34e0d049b51c661
 Content-Type: text/plain; charset=ISO-8859-1
 
 Hi folks,
 
 I hit this problem on a pair of anycast name servers.  What
 I'm running:
 
 FreeBSD ns1.example.com 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Mon Jul 19
 02:36:49
 UTC 2010     root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64
 
 Here's a peak at ps:
 
 ns1b# ps auxwww | head
 USER     PID %CPU %MEM   VSZ   RSS  TT  STAT STARTED      TIME COMMAND
 root      11 100.0  0.0     0    32  ??  RL   11Jan11 59960:15.43 [idle]
 root      21 100.0  0.0     0    16  ??  RL   11Jan11 1112:01.24
 [flowcleaner]
 root       0  0.0  0.0     0    96  ??  DLs  11Jan11   0:02.94 [kernel]
 root       1  0.0  0.0  3204   556  ??  ILs  11Jan11   0:00.01 /sbin/init --
 root       2  0.0  0.0     0    16  ??  DL   11Jan11   0:52.87 [g_event]
 root       3  0.0  0.0     0    16  ??  DL   11Jan11   0:10.10 [g_up]
 root       4  0.0  0.0     0    16  ??  DL   11Jan11   0:15.18 [g_down]
 root       5  0.0  0.0     0    16  ??  DL   11Jan11   0:00.00
 [mpt_recovery0]
 
 The box is running Quagga with a single OSPF adjacency.  It has about 500
 routes.
 Both anycast instances of ns1 hit this problem, but neither instance of ns2,
 which are
 configured identically, saw the trouble.  The ns1 name servers are much
 busier than ns2.
 
 It appears that one instance of ns1 died almost a week ago, which went
 unnoticed :-(  This
 morning, the second instance died.  At that point, it was hard not to notice
 :-)
 
 Traffic on the mailing list suggests that 'sysctl
 net.inet.flowtable.enable=0' is a work-around.
 We'll pursue that path and hope for a bug fix in the not-too-distant future.
 
 thanks,
 mark
 
 --00163630f77dc34e0d049b51c661
 Content-Type: text/html; charset=ISO-8859-1
 Content-Transfer-Encoding: quoted-printable
 
 <div>Hi folks,</div><div>=A0</div><div>I hit this problem on a pair of anyc=
 ast name servers. =A0What</div><div>I&#39;m running:</div><div>=A0</div><di=
 v>FreeBSD <a href=3D"http://ns1.example.com">ns1.example.com</a>; 8.1-RELEAS=
 E FreeBSD 8.1-RELEASE #0: Mon Jul 19 02:36:49</div>
 <div>UTC 2010 =A0 =A0 root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENER=
 IC =A0amd64</div><div><br></div><div>Here&#39;s a peak at ps:</div><div><br=
 ></div><div><div><div><font class=3D"Apple-style-span" face=3D"&#39;courier=
  new&#39;, monospace">ns1b# ps auxwww | head</font></div>
 <div><font class=3D"Apple-style-span" face=3D"&#39;courier new&#39;, monosp=
 ace">USER =A0 =A0 PID %CPU %MEM =A0 VSZ =A0 RSS =A0TT =A0STAT STARTED =A0 =
 =A0 =A0TIME COMMAND</font></div><div><font class=3D"Apple-style-span" face=
 =3D"&#39;courier new&#39;, monospace">root =A0 =A0 =A011 100.0 =A00.0 =A0 =
 =A0 0 =A0 =A032 =A0?? =A0RL =A0 11Jan11 59960:15.43 [idle]</font></div>
 <div><font class=3D"Apple-style-span" face=3D"&#39;courier new&#39;, monosp=
 ace">root =A0 =A0 =A021 100.0 =A00.0 =A0 =A0 0 =A0 =A016 =A0?? =A0RL =A0 11=
 Jan11 1112:01.24 [flowcleaner]</font></div><div><font class=3D"Apple-style-=
 span" face=3D"&#39;courier new&#39;, monospace">root =A0 =A0 =A0 0 =A00.0 =
 =A00.0 =A0 =A0 0 =A0 =A096 =A0?? =A0DLs =A011Jan11 =A0 0:02.94 [kernel]</fo=
 nt></div>
 <div><font class=3D"Apple-style-span" face=3D"&#39;courier new&#39;, monosp=
 ace">root =A0 =A0 =A0 1 =A00.0 =A00.0 =A03204 =A0 556 =A0?? =A0ILs =A011Jan=
 11 =A0 0:00.01 /sbin/init --</font></div><div><font class=3D"Apple-style-sp=
 an" face=3D"&#39;courier new&#39;, monospace">root =A0 =A0 =A0 2 =A00.0 =A0=
 0.0 =A0 =A0 0 =A0 =A016 =A0?? =A0DL =A0 11Jan11 =A0 0:52.87 [g_event]</font=
 ></div>
 <div><font class=3D"Apple-style-span" face=3D"&#39;courier new&#39;, monosp=
 ace">root =A0 =A0 =A0 3 =A00.0 =A00.0 =A0 =A0 0 =A0 =A016 =A0?? =A0DL =A0 1=
 1Jan11 =A0 0:10.10 [g_up]</font></div><div><font class=3D"Apple-style-span"=
  face=3D"&#39;courier new&#39;, monospace">root =A0 =A0 =A0 4 =A00.0 =A00.0=
  =A0 =A0 0 =A0 =A016 =A0?? =A0DL =A0 11Jan11 =A0 0:15.18 [g_down]</font></d=
 iv>
 <div><font class=3D"Apple-style-span" face=3D"&#39;courier new&#39;, monosp=
 ace">root =A0 =A0 =A0 5 =A00.0 =A00.0 =A0 =A0 0 =A0 =A016 =A0?? =A0DL =A0 1=
 1Jan11 =A0 0:00.00 [mpt_recovery0]</font></div></div></div><div><font class=
 =3D"Apple-style-span" face=3D"&#39;courier new&#39;, monospace"><br>
 </font></div><div><font class=3D"Apple-style-span" face=3D"arial, helvetica=
 , sans-serif">The box is running Quagga with a single OSPF adjacency. =A0It=
  has about 500 routes.</font></div><div><font class=3D"Apple-style-span" fa=
 ce=3D"arial, helvetica, sans-serif">Both anycast instances of ns1 hit this =
 problem, but neither instance of ns2, which are=A0</font></div>
 <div><font class=3D"Apple-style-span" face=3D"arial, helvetica, sans-serif"=
 >configured identically, saw the trouble. =A0The ns1 name servers are much =
 busier than ns2.</font></div><div><font class=3D"Apple-style-span" face=3D"=
 arial, helvetica, sans-serif"><br>
 </font></div><div><font class=3D"Apple-style-span" face=3D"arial, helvetica=
 , sans-serif">It appears that one instance of ns1 died almost a week ago, w=
 hich went unnoticed :-( =A0This</font></div><div><font class=3D"Apple-style=
 -span" face=3D"arial, helvetica, sans-serif">morning, the second instance d=
 ied. =A0At that point, it was hard not to notice :-)</font></div>
 <div><font class=3D"Apple-style-span" face=3D"arial, helvetica, sans-serif"=
 ><br></font></div><div><font class=3D"Apple-style-span" face=3D"arial, helv=
 etica, sans-serif">Traffic on the mailing list suggests that &#39;sysctl ne=
 t.inet.flowtable.enable=3D0&#39; is a work-around.</font></div>
 <div><font class=3D"Apple-style-span" face=3D"arial, helvetica, sans-serif"=
 >We&#39;ll pursue that path and hope for a bug fix in the not-too-distant f=
 uture.</font></div><div><font class=3D"Apple-style-span" face=3D"arial, hel=
 vetica, sans-serif"><br>
 </font></div><div><font class=3D"Apple-style-span" face=3D"arial, helvetica=
 , sans-serif">thanks,</font></div><div><font class=3D"Apple-style-span" fac=
 e=3D"arial, helvetica, sans-serif">mark</font></div>
 
 --00163630f77dc34e0d049b51c661--



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