Messages in this thread |  | | Date | Sat, 06 Jan 2001 10:51:22 -0500 | From | safemode <> | Subject | Re: ip_conntrack locks up hard on 2.4.0 after about 10 hours |
| |
<!doctype html public "-//w3c//dtd html 4.0 transitional//en"> <html> <br>Setiathome 3.03 and 3.x most likely causes the ip_conntrack errors which quickly brings the system to a screetching network halt. I suggest nobody run setiathome on their firewall/gateway/router if they're using iptables with 2.4.x. Not sure how it causes this error nor would it matter to me since i wouldn't be able to recode the client anyway. I'm sure there are setiathome developers (at least one) paying attention to this list. The client is broken. <br> <br> <br> <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. All i found were <br>these messages in my dmesg output <br>Jan 6 06:18:10 icebox kernel: reset_xmit_timer sk=c17fd040 1 <br>when=0x5d9e, caller=c01a6bf1 <br>Jan 6 06:18:10 icebox kernel: reset_xmit_timer sk=c17fd040 1 <br>when=0x5b2f, caller=c01a6bf1 <br>Jan 6 06:18:10 icebox kernel: reset_xmit_timer sk=c17fd040 1 <br>when=0x56bb, caller=c01a6bf1 <br>Jan 6 06:40:10 icebox kernel: reset_xmit_timer sk=c17fd040 1 <br>when=0x217db, caller=c01a6bf1 <br>Jan 6 06:40:10 icebox kernel: reset_xmit_timer sk=c17fd040 1 <br>when=0x2363e, caller=c01a6bf1 <br>Jan 6 06:40:10 icebox kernel: reset_xmit_timer sk=c17fd040 1 <br>when=0x21b64, caller=c01a6bf1 <br>Jan 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. 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. 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. :) i have been <br>using iptables since it came out though and ip_conntrack has only been <br>bad once before, 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> </blockquote>
<br> <br> </html>
|  |