View Issue Details

IDProjectCategoryView StatusLast Update
0001658unrealircdpublic2004-03-16 16:03
Reporternemoswitch Assigned To 
PrioritynormalSeveritycrashReproducibilityalways
Status closedResolutionopen 
Product Version3.2-RC2 
Summary0001658: wird stops responding to client connects
Description[12:29] * Send error ([10053] Software caused connection abort)
-
[12:29] * Disconnected
Steps To Reproduceif a client connects too fast to the wircd. Unreal3.2RC2Fix stops responding. and A person has to shut down the server and restart it. I have tested to see how fast. and I have been able to make Unreal stop responding within 3 fast reconnects in between 5 - 10 seconds. this happens on regular client connects and ssl client connects. I run a different brand of ircd compiled on cygwin that does not do this. Server connects don't seem to do this. but server connects have that delay to connect so I have not tried to reproduce it there. it may just be my windows. but. Someone else may be able to reproduce this too.
Additional InformationThere is no error in any logs about this error.
3rd party modules

Activities

syzop

2004-03-16 15:41

administrator   ~0005509

if you mean that if 1 particular client reconnects too fast he can no longer connect (gets "throttled: blabla" error, or that thing you pasted above if you are very close with the server [eg: localhost]) for some time, then yes... that's called throttling :P.. This is done on per-IP basis, see set::throttle to tweak (or except throttle { } if you want to allow certain ips to bypass throttle).

If you mean all the connected clients get stalled/disconnected or any other persons with a different IP cannot connect either blabla etc.. then it's something else :P.

nemoswitch

2004-03-16 15:52

reporter   ~0005510

yes. sorry. I haven't used unreal for quite awhile. I was used to seeing the error message of.

[12:51] ERROR Trying to reconnect too fast..

but. I now noticed that unreal does not have that error message when throttling.

sorry again. please scratch my bug if you can.

syzop

2004-03-16 16:03

administrator   ~0005511

ok.

it only seems to happen sometimes with mIRC... when sniffing you can see that the 'Throttled: reconnecting too fast' message IS received, but before a 'NICK' msg is sent... when sending the 'NICK' msg the connection is already closed (thus the send error) and mirc did not display the ERROR: msg from the server itself, it's fun!

Issue History

Date Modified Username Field Change
2004-03-16 15:36 nemoswitch New Issue
2004-03-16 15:41 syzop Note Added: 0005509
2004-03-16 15:52 nemoswitch Note Added: 0005510
2004-03-16 16:03 syzop Status new => closed
2004-03-16 16:03 syzop Note Added: 0005511