lkml.org 
[lkml]   [2001]   [Jan]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: ip_conntrack locks up hard on 2.4.0 after about 10 hours
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>Setiathome 3.03 and 3.x most likely causes the ip_conntrack errors
which quickly brings the system to a screetching network halt.&nbsp;&nbsp;
I suggest nobody run setiathome on their firewall/gateway/router if they're
using iptables with 2.4.x.&nbsp;&nbsp; Not sure how it causes this error
nor would it matter to me since i wouldn't be able to recode the client
anyway.&nbsp; I'm sure there are setiathome developers (at least one) paying
attention to this list.&nbsp; The client is broken.
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<p>safemode wrote:
<blockquote TYPE=CITE>It seems that for one reason or another, ip_conntrack
totally locks (not
<br>removeable) after about 10 hours of continued use.&nbsp; All i found
were
<br>these messages in my dmesg output
<br>Jan&nbsp; 6 06:18:10 icebox kernel: reset_xmit_timer sk=c17fd040 1
<br>when=0x5d9e, caller=c01a6bf1
<br>Jan&nbsp; 6 06:18:10 icebox kernel: reset_xmit_timer sk=c17fd040 1
<br>when=0x5b2f, caller=c01a6bf1
<br>Jan&nbsp; 6 06:18:10 icebox kernel: reset_xmit_timer sk=c17fd040 1
<br>when=0x56bb, caller=c01a6bf1
<br>Jan&nbsp; 6 06:40:10 icebox kernel: reset_xmit_timer sk=c17fd040 1
<br>when=0x217db, caller=c01a6bf1
<br>Jan&nbsp; 6 06:40:10 icebox kernel: reset_xmit_timer sk=c17fd040 1
<br>when=0x2363e, caller=c01a6bf1
<br>Jan&nbsp; 6 06:40:10 icebox kernel: reset_xmit_timer sk=c17fd040 1
<br>when=0x21b64, caller=c01a6bf1
<br>Jan&nbsp; 6 06:40:10 icebox kernel: reset_xmit_timer sk=c17fd040 1
<br>when=0x1fa85, caller=c01a6bf1
<p>This makes it impossible to make any sort of network socket connection
<br>and all prior connections died.&nbsp; As i said you cannot remove the
module
<br>to reset ip_conntrack and i'm not sure what could have caused this
as it
<br>did work up until i woke up this morning, with a total running time
of
<br>about 10 hours or so.&nbsp; I'd consider this bug rather important,
if anyone
<br>thinks this is not an ip_conntrack bug and rather something that has
<br>changed that i havn't read about, help would be nice. :)&nbsp;&nbsp;&nbsp;
i have been
<br>using iptables since it came out though and ip_conntrack has only been
<br>bad once before,&nbsp;&nbsp; on test5 when it wouldn't kill old dead
socket
<br>connections and eventually starved itself of free sockets.
<br><a href="http://www.tux.org/lkml/"></a>&nbsp;</blockquote>

<br>&nbsp;
<br>&nbsp;</html>
\
 
 \ /
  Last update: 2005-03-22 12:52    [W:0.040 / U:0.884 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site