aMule Forum
English => en_Bugs => Topic started by: newbeewan on July 28, 2004, 11:22:17 AM
-
Hi,
It was a bug report I post to xMule teem before aMule creation ! 8o
It was killed and it reappeared for me since I install the rc5
The result is it saturate my gateway ip_conntrack with some established connection never ended by aMule.
Please, Please, Please, solve it with hight priority.... :baby:
Thanks a lot
-
I'm bringing up an old post, and asking sort of a stupid question, as I'm compiling and about to try out rc7. But I just want to check whether this problem has been fixed in rc7.
I believe this fix in the changelog:
Fixed a bug in sockets where disconnected sockets wouldn't be removed immediatly, but left to timeout instead.
fixes this problem? Is that correct?
-
AFAIK, yes ;)
-
Wow, fast reply. I just finished hitting Post, updating aMule, started it up and hit refresh :baby:
That's good to know. I'll post if I notice any problems.
-
I'm a refresh freak.
-
It seem to be solved... let's run 3 or 4 days more to see if the number of open connection increase or not in the conntrack of my gateway...
Thanks for your fix :)
-
Please let us know the result. ;)
-
Well, unless there is something else I should've done after updating, it doesn't seem to have worked here.
After updating, I let it run all day, and used "cat /proc/net/ip_conntrack | grep -c ESTABLISHED" to watch it fill up. By last night, it had filled up enough that it interrupted my net connection. Closing amule did free up about 200-300 conntrack slots. I'm not sure that it's always done that.
But there's still ~3800 ESTABLISHED amule connections this morning (out of 4096 by default on a machine with 64MB RAM ['cat /proc/sys/net/ipv4/ip_conntrack_max' to find that]). From what I've read, ESTABLISHED connections don't timeout for 5 days by default. Possibly removing the ip_conntrack module and reloading it would clear them out, but it's being used by 8 other modules, so I've just been rebooting.
Also, yesterday after a clean reboot, I opened amule and let it fill up about 200 slots or so, and then closed it and they properly went to TIME_WAIT and then closed. I'll try to see if I can figure out at what point it's not able to close all the connections anymore.
Also, I've had my max connections at 25 for awhile now. My max new connections/5 second was at 20. I also turned down the max queue size to 500 yesterday.
I'm not sure if any of this helps, but it took me awhile to figure out what was happening, so maybe this will be helpful to someone.
I'll also check back to see what newbeewan finds after running the update for awhile. I'll try rebooting too, in case something from the old version was somehow being used.
-
I'll look into it.
-
Just an update. I rebooted both the router and the computer running amule. I let ip_conntrack get up to ~320 and then shutdown amule and it's sitting at ~280 stuck connections now.
Let me know if you need any info or for me to try anything.
-
Could you try recompiling with the configure flag --disable-gsocket ?
-
I recompiled with that configure flag but I'm still getting the same thing.
-
Ok, thanks.
-
Just thought I'd mention that I've used rc8 a couple times now and it looks to be closing the connections now. I'll have to test it a bit more, but so far, so good.
-
Marking it as fixed.