View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0004529unrealircdpublic2015-12-31 23:412016-03-04 14:25
ReportervNode1 Assigned Tosyzop  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionunable to duplicate 
Product Version4.0.0 
Summary0004529: Increased ping outs
DescriptionI have noticed after switching to Unreal 4 that I have problems staying linked to other Unreal 4's, even if they are hosted in the same company. I mean there is a chance that it's a coincidence that my provider has been having network issues since we switched, but I've never had this before.

[11:43] -irc.vnode.ovh- ERROR :from twisted.vnode.ovh[51.254.141.204] -- Closing Link: irc.vnode.ovh[ip-3.35.254.51.reverse.level3.vnode.ovh] (Ping timeout: 120 seconds)
-
3rd party modules

Activities

syzop

2016-01-01 17:57

administrator   ~0019003

I can only say that I'm not seeing this on my own network.

dboyz

2016-01-04 05:57

reporter   ~0019014

Additional information from kevin

[12:32:07] <+Kevin> We also get weird ping time outs
[12:32:10] <+Kevin> like example: theres this too
[12:32:14] <+Kevin> [09:24] * Quits: ~FknNode ([email protected]) (Read error)
[12:32:22] <+Kevin> That's hosted locally
[12:32:28] <@DBoyz> That has something to do with SSL
[12:32:28] <+Kevin> There's no need for it to Read error
[12:32:34] <+Kevin> It's not connected on SSL.
[12:33:00] <+Kevin> That's just a plain connection to the server
[12:33:01] <+Kevin> it's not SSL
[12:33:24] <+Kevin> But i get tons of ping outs
[12:33:37] <+Kevin> Shit, even a 127.0.0.1 ip (locally) pinged out

Time to reaudit our socket codes?

syzop

2016-01-04 10:31

administrator   ~0019016

A "Read error" is not a ping timeout, though, it's quite different.
Also, a ping timeout from a 127.0.0.1 client is possible... if the client doesn't pong back (or not in time, anyway).
Not saying there is no problem, it's a new I/O engine after all so it's not unreasonable to suspect something. Just saying it's not as clear-cut as is claimed.

Could you give us some additional information:
1) What IRC client software was getting ping timeout locally? And which one got the read error?
2) What is your class:pingfreq set to for these clients?
3) Which OS does the IRCd run on? (As this impacts which I/O engine is in use)

Thanks!

vNode1

2016-01-04 17:08

reporter   ~0019022

It runs on Debian, mIRC xChat, ZNC, irssi

All the above clients ping out at random, even if connected locally

- never have I had this problem in the unreal 3 branch

clients are alternative between ping time out: 180 seconds, etc to Read Error weather or not they're on SSL.

ping freq is:
class clients
{
    pingfreq 90;
    maxclients 1000;
    sendq 500k;
    recvq 8000;
};

vNode1

2016-01-05 05:22

reporter   ~0019026

[03:55] * [10053] Software caused connection abort
-
[03:55] * Disconnected
-
reconnected instantly.

vNode1

2016-01-05 05:29

reporter   ~0019027

[08:50] * Quits: FknNode ([email protected]) (Ping timeout: 180 seconds)

syzop

2016-01-05 20:57

administrator   ~0019028

Sounds like quite some clients that experience the issue. Just one question... when you say locally you mean the local network and not localhost? How else can mIRC run on Debian, unless you use wine? :)

Anyway, I've started monitoring all ping timeouts on my server. I'll post results here if I have anything.

blank

2016-01-05 21:47

reporter   ~0019029

Last edited: 2016-01-05 21:51

 @syzop some statistics we've collected on our network

17:00 - 19:00 (GMT)

1840 connects, 7 disconnects (Ping Timeout)

about usual

syzop

2016-01-05 22:16

administrator   ~0019030

Thanks :)

vNode1

2016-01-05 22:26

reporter   ~0019031

I suppose I'm not being clear:

I ping out, and i am znc'd via localhost

FknNode is the same same provider just a windows shell on the same host it's a split box, never pinged out on unreal, our ping time outs are abnormally high since the switch. I mean i can add an o:line on my server for you if you want. lol. I'm trying not to switch software I've always liekd Unreal. sorry this keyboard sucks at work currently.

syzop

2016-01-08 12:24

administrator   ~0019033

To debug the localhost connections you can run the following ngrep command on the IRC server as root. This requires 'ngrep' (so, 'apt-get install ngrep').

Command:
ngrep -d lo -q -t '(PING|PONG|Ping timeout)' 'port 6667' 1>/root/ping.log 2>&1&

Then after you have a few unexpected ping timeouts you can send the /root/ping.log over to me ([email protected]).

Issue History

Date Modified Username Field Change
2015-12-31 23:41 vNode1 New Issue
2016-01-01 17:57 syzop Note Added: 0019003
2016-01-01 17:57 syzop Priority high => normal
2016-01-04 05:57 dboyz Note Added: 0019014
2016-01-04 10:31 syzop Note Added: 0019016
2016-01-04 10:31 syzop Assigned To => syzop
2016-01-04 10:31 syzop Status new => feedback
2016-01-04 17:08 vNode1 Note Added: 0019022
2016-01-05 05:22 vNode1 Note Added: 0019026
2016-01-05 05:29 vNode1 Note Added: 0019027
2016-01-05 20:57 syzop Note Added: 0019028
2016-01-05 20:57 syzop Status feedback => new
2016-01-05 21:47 blank Note Added: 0019029
2016-01-05 21:48 blank Note Edited: 0019029
2016-01-05 21:51 blank Note Edited: 0019029
2016-01-05 22:16 syzop Note Added: 0019030
2016-01-05 22:26 vNode1 Note Added: 0019031
2016-01-08 12:24 syzop Note Added: 0019033
2016-03-04 14:24 syzop Status new => closed
2016-03-04 14:25 syzop Resolution open => unable to duplicate