Players timing out randomly
#21

This is the first good response I see, thanks Spmn.

I found an updated version of it made by the original author. It will be hard to ask few players to put it and analyse all that data (maybe I could change the settings of it to something better), in case that mass timeout happens again. Also, I see that it has memory leaks (my game got up to ~1.4gb when everything got bugged) and few other stability problems.

Quote:

[06/07/2016 16:34:51] [part] niconiocni has left the server (2:0)
[06/07/2016 16:34:52] [part] Johni_Sopran has left the server (23:0)
[06/07/2016 16:34:52] [part] HellGirl__ has left the server (43:0)
[06/07/2016 16:34:52] [part] MTT_Mc_Fams has left the server (10:0)
[06/07/2016 16:34:52] [part] MTT_Mr_Fams has left the server (14:0)
[06/07/2016 16:34:52] [part] Owl12 has left the server (39:0)
[06/07/2016 16:34:52] [part] GGWPEZ has left the server (1:0)
[06/07/2016 16:34:52] [part] Vinnie has left the server (19:0)
[06/07/2016 16:34:52] [part] skrawch8 has left the server (27:0)
[06/07/2016 16:34:52] [part] spo has left the server (35:0)
[06/07/2016 16:34:53] [part] [TH]Mateka has left the server (28:0)
[06/07/2016 16:34:53] [part] AancAleXx has left the server (3:0)
[06/07/2016 16:34:53] [part] SUITSIID. has left the server (36:0)
[06/07/2016 16:34:53] [part] LVARTURS has left the server (6:0)
[06/07/2016 16:34:53] [part] [SG]Scrin has left the server (9:0)
[06/07/2016 16:34:53] [part] Lollo_Bra has left the server (11:0)
[06/07/2016 16:34:53] [part] xXGhoStWoLFXx has left the server (17:0)
[06/07/2016 16:34:53] [part] edi48gamer has left the server (21:0)
[06/07/2016 16:34:53] [part] Igor_Mashinin has left the server (24:0)
[06/07/2016 16:34:53] [part] Pauto_Raugas has left the server (26:0)
[06/07/2016 16:34:53] [part] [SG]KingFisher. has left the server (37:0)
[06/07/2016 16:34:53] [part] [SG]Probux. has left the server (41:0)

A timeout for 22 players, we were ~25 players left.

The weird thing is that ~3 of those players were in the same vehicle with me (a bus), so 3 players timeouted and 3 didn't. It's like the one who is doing the exploit can choose who timeouts, because I didn't received one of those timeouts for a few months already.

By the way, that RakLogger is crashing the game after a short play time (~1 hour), probably because it uses way too much memory or it has memory leaks. I can't give it to my players and I also can't detect where the timeouts come from because I don't receive any timeout.

37 players:
pawn Code:
[08/07/2016 14:29:49] [part] PizzaBoy_QTV has left the server (10:0)
[08/07/2016 14:29:49] [part] T.S has left the server (15:0)
[08/07/2016 14:29:49] [part] Gta_Victor has left the server (27:0)
[08/07/2016 14:29:49] [part] Vinnie has left the server (23:0)
[08/07/2016 14:29:49] [part] Axer has left the server (53:0)
[08/07/2016 14:29:49] [part] T3rmin4t0r has left the server (25:0)
[08/07/2016 14:29:49] [part] Leorquiorra has left the server (32:0)
[08/07/2016 14:29:49] [part] MAXIMS has left the server (16:0)
[08/07/2016 14:29:49] [part] truong_G has left the server (34:0)
[08/07/2016 14:29:49] [part] [TH]Mare_69_Life has left the server (20:0)
[08/07/2016 14:29:49] [part] mikute123456789 has left the server (0:0)
[08/07/2016 14:29:49] [part] Vapor has left the server (2:0)
[08/07/2016 14:29:49] [part] Owl12 has left the server (7:0)
[08/07/2016 14:29:49] [part] IstI has left the server (26:0)
[08/07/2016 14:29:49] [part] gaga_gamer has left the server (1:0)
[08/07/2016 14:29:49] [part] @Petrut has left the server (29:0)
[08/07/2016 14:29:49] [part] gamebinner173 has left the server (31:0)
[08/07/2016 14:29:49] [part] ZapperRekter has left the server (52:0)
[08/07/2016 14:29:49] [part] Domis_Glock has left the server (58:0)
[08/07/2016 14:29:49] [part] Vanguard has left the server (60:0)
[08/07/2016 14:29:49] [part] Flavius0 has left the server (3:0)
[08/07/2016 14:29:49] [part] ApaMinerala has left the server (4:0)
[08/07/2016 14:29:49] [part] [69]BunnyPervert has left the server (5:0)
[08/07/2016 14:29:49] [part] [SG]Probux. has left the server (8:0)
[08/07/2016 14:29:49] [part] [SG]Scrin has left the server (9:0)
[08/07/2016 14:29:49] [part] stashkin1 has left the server (11:0)
[08/07/2016 14:29:49] [part] Vasya_Becker has left the server (19:0)
[08/07/2016 14:29:49] [part] RelaX. has left the server (21:0)
[08/07/2016 14:29:49] [part] DanielFernandes has left the server (28:0)
[08/07/2016 14:29:49] [part] VLADTik has left the server (33:0)
[08/07/2016 14:29:49] [part] MaSt3r has left the server (36:0)
[08/07/2016 14:29:49] [part] [SG]KingFisher. has left the server (37:0)
[08/07/2016 14:29:49] [part] KING has left the server (41:0)
[08/07/2016 14:29:49] [part] [SG]VerteX has left the server (44:0)
[08/07/2016 14:29:49] [part] FLACARA21 has left the server (47:0)
[08/07/2016 14:29:49] [part] Den4ik has left the server (54:0)
[08/07/2016 14:29:49] [part] ESCU has left the server (59:0)
Can't believe it. This is by far the biggest mass timeout I ever received. This sh*t is ruining everything. I see that the last ID who timeouted had ID 59. When I saw the server now it had only 30 players.

15 euro monthly for hosted tab, just for my players to receive mass timeouts, great ! Thanks SA:MP !
Reply
#22

The thing is that Romania's biggest servers are hosted at them, having a total of a few thousands players.

When I made a ticket they said that they checked everything and saw no problem. Also, they didn't receive a ticket about this problem from any other server hosted at them (well, others may not see the timeouts ?). I also checked everything in my server, there's no problem with it. They look professional. I'm hosted at them since 2012 and before 0.3.7 (or 0.3z, not sure when this problem first started to happen) mass timeouts never happened.

I ocasionally receive
Quote:

[warning] dropping a split packet from client

in console, but today I got only ~3 warns like that.

If it would be a flood I think that if I don't receive a timeout, I should have lag at least, but that's not the case, the game is fine for me.

It happened again today, but it is weirder than before:
pawn Code:
[01/10/2016 19:44:26] [part] Zlatan_nostra has left the server (64:0)
[01/10/2016 19:44:26] [part] The_MagiC has left the server (46:0)
[01/10/2016 19:44:27] [part] Cheloo has left the server (48:0)
[01/10/2016 19:44:27] [part] [KraToF] has left the server (12:0)
[01/10/2016 19:44:27] [part] Mario_Well has left the server (22:0)
[01/10/2016 19:44:28] [part] Pedro_Souza has left the server (56:0)
[01/10/2016 19:44:28] [part] [TBK]raouly has left the server (77:0)
[01/10/2016 19:44:29] [part] dragonit has left the server (17:0)
[01/10/2016 19:44:30] [part] [TH.creW]mAngO_ has left the server (5:0)
[01/10/2016 19:44:30] [part] AlexandruXD has left the server (10:0)
[01/10/2016 19:44:31] [part] Wizz009 has left the server (7:0)
[01/10/2016 19:44:31] [part] SickKitten has left the server (78:0)
[01/10/2016 19:44:32] [part] Roni_Mago has left the server (76:0)
[01/10/2016 19:44:32] [part] Rocombole has left the server (72:0)
[01/10/2016 19:44:33] [part] megagamesbr has left the server (41:0)
[01/10/2016 19:44:33] [part] [TH.creW]NapsTR_ has left the server (40:0)
[01/10/2016 19:44:34] [part] [STF]Jezyl10 has left the server (0:0)
[01/10/2016 19:44:34] [part] TiowDosCrack has left the server (15:0)
[01/10/2016 19:44:36] [part] MangEdLuffy has left the server (1:0)
[01/10/2016 19:44:37] [part] Justin_Zockt has left the server (61:0)
[01/10/2016 19:44:39] [part] Kenpachi_Zaraki has left the server (8:0)
[01/10/2016 19:44:42] [part] Anonym_Danke has left the server (20:0)
[01/10/2016 19:44:43] [part] jefferson has left the server (3:0)
[01/10/2016 19:44:46] [part] Gaudytojas has left the server (54:0)
They were timeouting one by one (as you can see in the timestamp). Yes, the "restarting" kind of timeout. No helpful thing in the serverlog at all.
Reply
#23

Sure it's not ddos? correct me if i'm wrong or someone already said this
Reply
#24

Quote:
Originally Posted by CannonBolt
View Post
Sure it's not ddos? correct me if i'm wrong or someone already said this
They checked and they said that there wasn't any DDoS when those timeouts happened.
Reply
#25

Been happening on a server I play/admin at it. I pretty much timeout even on LSRP while my internet is working fine too.
Reply
#26

Happens on the server I play on too. I believe it's something from SA-MP server itself, the big difference is, all players timeout at once, and then connect again.
Reply
#27

Quote:
Originally Posted by Jayse
View Post
Happens on the server I play on too. I believe it's something from SA-MP server itself, the big difference is, all players timeout at once, and then connect again.
Yeah, that's what happens.

Again today (well, after my last post it still happened sometimes, but it happened rarely in the last months because I no longer have hosted tab):
Quote:

[28/12/2016 20:22:52] [part] SKTT1 has left the server (11:0)
[28/12/2016 20:22:52] [part] DKRAouly has left the server (32:0)
[28/12/2016 20:22:52] [part] gjekuthebest has left the server (3:0)
[28/12/2016 20:22:52] [part] smoke has left the server (8:0)
[28/12/2016 20:22:52] [part] Cristina_Kat has left the server (9:0)
[28/12/2016 20:22:52] [part] Dovla_Brat has left the server (28:0)
[28/12/2016 20:22:52] [part] Sedox_Drifter has left the server (0:0)

Yeah, not too many players this time, "luckily" enough.
Reply
#28

It's either a script related issue, or your host just isn't good for hosting gameservers.

It isn't a client issue, other servers would have the same issue otherwise.
Reply
#29

Quote:
Originally Posted by SickAttack
View Post
It's either a script related issue, or your host just isn't good for hosting gameservers
Nah, the hoster he uses is pretty popular here in Romania and several 1000 player servers are hosted there with no problem.

Have you checked what packets/RPCs are sent to players before they timeout as I've told you before?
Reply
#30

Quote:
Originally Posted by SickAttack
View Post
It's either a script related issue, or your host just isn't good for hosting gameservers.

It isn't a client issue, other servers would have the same issue otherwise.
Read all replies in this topic. It also happens to other servers. I analysed everything in my script. The guys from the host also checked everything they could. I'm hosted where few of Romania's biggest servers are hosted too.

Quote:
Originally Posted by Spmn
View Post
Have you checked what packets/RPCs are sent to players before they timeout as I've told you before?
Well, I just started using this:
https://github.com/urShadow/RakNetManager

Few minutes ago I was thinking about those packets/RPCs. I'm curious if they still call one of those callbacks if packets/RPCs are sent to a player after he actually lost connection to the server. I find this thing a bit difficult. :c If they are still called, there's no reason to actually track them, as there could be some legit packets/RPCs sent to the player after he loses connection from a bad packet/RPC.

Also, I can't really test this packet/RPC tracking as this mass timeout happens pretty rarely.
Reply
#31

That's my point, it's a script related issue then.
Reply
#32

Quote:
Originally Posted by SickAttack
Посмотреть сообщение
That's my point, it's a script related issue then.
There's no [warning] in server log like "dropping split packet", "client exceeded messages limit", "client exceeded messages hole limit" or similar thing. I also added debugs for all Kick/BlockIpAddress/Ban/BanEx in my scripts before, some mass timeouts happened while these debugs were enabled, but there was no function of those called. Everything is fine in my script. I even checked every plugin's source, everything is fine, no plugin has anything to do with kicks/IP blocks. I never had problems like this until 0.3.7. I started my server in 2009.

Also, other forum members also replied here that it happens to other servers too, with various configurations and locations. Just read everything I posted in this topic instead of claiming the same thing all over again. Also, I saw few other topics related to this exact same thing.

If I correctly remember, everything started after I bought hosted tab for the first time, after those internet lists exploits appeared and the list got closed, cloning the hosted tab.
Reply
#33

Quote:
Originally Posted by IstuntmanI
Посмотреть сообщение
There's no [warning] in server log like "dropping split packet", "client exceeded messages limit", "client exceeded messages hole limit" or similar thing. I also added debugs for all Kick/BlockIpAddress/Ban/BanEx in my scripts before, some mass timeouts happened while these debugs were enabled, but there was no function of those called. Everything is fine in my script. I even checked every plugin's source, everything is fine, no plugin has anything to do with kicks/IP blocks. I never had problems like this until 0.3.7. I started my server in 2009.

Also, other forum members also replied here that it happens to other servers too, with various configurations and locations. Just read everything I posted in this topic instead of claiming the same thing all over again. Also, I saw few other topics related to this exact same thing.

If I correctly remember, everything started after I bought hosted tab for the first time, after those internet lists exploits appeared and the list got closed, cloning the hosted tab.
You using VPS or slots? If VPS can I know which OS? I was facing the same issue. But somehow I fix it my own.
Reply
#34

I already said what I am using. Anyway, Ubuntu 10.04, AFAIK. Shared host.

I'll stop answering to future replies if the answers are in previous posts. I don't want to repeat everything everytime. Just read previous posts if you are curious.
Reply
#35

Well. I had the same issue I tried both Ubuntu 10.04 and 10.10. The solution I found is I move to Debian and it working fine. So I suggest you that.
Reply
#36

The fact this only happens on a few servers, means this is an issue on one of your ends. Not the client.

Massive timeouts happened way before 0.3.7, some servers managed to fix the issue after having everyone timeout and timeout.
Reply
#37

Quote:
Originally Posted by SickAttack
Посмотреть сообщение
The fact this only happens on a few servers, means this is an issue on one of your ends. Not the client.

Massive timeouts happened way before 0.3.7, some servers managed to fix the issue after having everyone timeout and timeout.
That's a Ubuntu issue since I found. As I waste 1 week on finding solution. Since I move to Debian 8. I faced not a single issue like this. I face the same issue as he mention and the solution I find is switching to Debian. As I suggest him same.
Reply
#38

I don't get how it could drop connections as they checked and said that it didn't drop any connection at that time. I don't think they are lying (they have no reason for that), they look alright. I don't think it could happen without them being able to see it. As I said, they host some of the biggest romanian servers and such problems would be detected really fast.

Also, I won't switch to something else, due to various reasons.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)