Server Packet resend failed (1.4.8 beta-9)

[Vafin]

Some of my users are thrown from the server with the error "Packet resendfailed". What could be the reason?

[17:14:37] [INFO ]   145 | [83.149.19.246:23301/Hev[Иван] | 3] Client initialized session reconnect, but last ping response is not older then 5 seconds (1505). Ignoring attempt
[17:14:37] [INFO ]   145 | [83.149.19.246:23301/Hev[Иван] | 3] Client initialized session reconnect, but last ping response is not older then 5 seconds (2055). Ignoring attempt
[17:14:38] [INFO ]   145 | [83.149.19.246:23301/Hev[Иван] | 3] Client initialized session reconnect, but last ping response is not older then 5 seconds (2755). Ignoring attempt
[17:14:39] [INFO ]   145 | [83.149.19.246:23301/Hev[Иван] | 3] Client initialized session reconnect, but last ping response is not older then 5 seconds (3795). Ignoring attempt
[17:14:40] [INFO ]   145 | [83.149.19.246:23301/Hev[Иван] | 3] Client initialized reconnect and last ping response is older then 5 seconds (5054). Allowing attempt
[17:14:40] [INFO ]   145 | Voice client 36554/F5LrReXPhBDVCj0b2oqrdKJAP6o= (Hev[Иван]) from 83.149.19.246:23301 left.

[16:06:17] [INFO ]   145 | [95.52.178.198:54528/Quick_Rediska | 3] Client initialized reconnect and last ping response is older then 5 seconds (19801). Allowing attempt
[16:06:17] [INFO ]   145 | Voice client 36582/Trr67sivYp3edC0Z25kRLNBN+RA= (Quick_Rediska) from 95.52.178.198:54528 left.
[16:06:18] [ERROR]   145 | [95.52.178.198:54528/undefined | 0] Handling of command packet needs more than 10ms (11ms)
[16:06:18] [INFO ]   145 | [95.52.178.198:54528/Quick_Rediska | 0] Client may cached a old permission list (Server is newer than the client's last join)
[16:06:18] [ERROR]   145 | Command handling of command clientinit needs 124ms. This could be an issue!
[16:06:18] [ERROR]   145 | [95.52.178.198:54528/Quick_Rediska | 0] Handling of command packet needs more than 10ms (124ms)
[16:06:18] [INFO ]   145 | Voice client 36582/Trr67sivYp3edC0Z25kRLNBN+RA= (Quick_Rediska) from 95.52.178.198:54528 joined.

[17:06:37] [WARNING ]   145 | Found varianzes within the server tick! (Supposed: 500ms Hold: 530ms)
[17:06:40] [INFO ]   145 | [176.215.136.13:4242/_SNAIPER_Region_45 ЯРОСЛАВ | 0] Client may cached a old permission list (Server is newer than the client's last join)
[17:06:40] [WARNING ]   145 | Command handling of command clientinit needs 61ms.
[17:06:40] [ERROR]   145 | [176.215.136.13:4242/_SNAIPER_Region_45 ЯРОСЛАВ | 0] Handling of command packet needs more than 10ms (61ms)
[17:06:40] [INFO ]   145 | Voice client 36555/rJ5nFuJXdwC4cbcPd/W8ETr4ZcQ= (_SNAIPER_Region_45 ЯРОСЛАВ) from 176.215.136.13:4242 joined.

 

[WolverinDEV]

"What could be the reason?", well a naive answer would be: Bad internet.
But they're not allowed to reconnect instantly because the server still has to disconnect them.

This is manly due to some deeply rooted architecture mistakes, made within the beginning of this project.
I'm close to allocate some time and rewrite the core of the whole server. But before I need a stable 1.4.10

 

[Vafin]

"What could be the reason?", well a naive answer would be: Bad internet.
But they're not allowed to reconnect instantly because the server still has to disconnect them.

This is manly due to some deeply rooted architecture mistakes, made within the beginning of this project.
I'm close to allocate some time and rewrite the core of the whole server. But before I need a stable 1.4.10

I look forward to fixing problems in the kernel.

 

[WolverinDEV]

HAHA yeahr but the best thing is that in total you as user will not (hopefully) notice anything at all

 

[Vafin]

"What could be the reason?", well a naive answer would be: Bad internet.
But they're not allowed to reconnect instantly because the server still has to disconnect them.

This is manly due to some deeply rooted architecture mistakes, made within the beginning of this project.
I'm close to allocate some time and rewrite the core of the whole server. But before I need a stable 1.4.10

Tomorrow morning, I'll put the server in trace mode and send you more detailed logs in the evening.

---- Automatically Merged Double Post ----

My client said that the ejection from the server was related to the server group that he was giving out to his users. After its removal, the ejection stopped

---- Automatically Merged Double Post ----

When he created a new server group only these permissions were assigned

http://imgur.com/gGYCpn1

---- Automatically Merged Double Post ----

For some reason, permissions from the server group template are incorrectly assigned to the new group.

---- Automatically Merged Double Post ----

I found a problem, when creating a server group, permissions are not assigned (unknown). If you assign this group to a user, it will crash from the server.

same on teaclient

---- Automatically Merged Double Post ----

The same is true in the server version 1.4.10
The group should be created using the Guest template, but this does not happen.

 

[REDOSS]

@Vafin You will not believe it, but not so long ago someone described similar steps problems to me, but i did not pay attention to it... need to check again)

according to my user's feedback), it created a clean group and assigned only an icon... and the users of this group started losing their connection to the server, but when it removed this group from them, the losses stopped... it's some kind of magic))

 

[eduardoroeder]

I've described the same situation (with the same gif reroduction) in another post couple days ago

---- Automatically Merged Double Post ----

https://forum.teaspeak.de/index.php?threads/server-kicking-client-and-keep-him-from-connecting-back-after-servergroup-add-remove.2492/

 

[WolverinDEV]

Hmm just check it and it seems I somehow manage to revert that change^^

 

[Vafin]

Hmm just check it and it seems I somehow manage to revert that change^^

When I said that there is an error in version 1.4.10, I meant that the group is created empty and it is not assigned permissions, although there should be more of them. But what is interesting, in the server version 1.4.10, even with an empty group, the user does not throw out from the server.

 

[REDOSS]

When I said that there is an error in version 1.4.10, I meant that the group is created empty and it is not assigned permissions, although there should be more of them. But what is interesting, in the server version 1.4.10, even with an empty group, the user does not throw out from the server.

Perhaps this was fixed in version 1.4.10?
If you decide to create a new group from a template, then it will be created empty, as in a normal template?
In theory, if you select a type from a template, the group should be created based on the "Guest" group template ID 3?

 

[Vafin]

If you decide to create a new group from a template, then it will be created empty, as in a normal template?

For a newly created group, only the b_group_is_permanent permission is given, although there should be more.

In theory, if you select a type from a template, the group should be created based on the "Guest" group template ID 3?

I suppose it must be so, maybe I'm wrong...

Perhaps this was fixed in version 1.4.10?

Most likely Yes.

 

[REDOSS]

I'm commenting on the topic title.
This seems to have been fixed in version 1.4.9-beta 1

 

[Vafin]

I'm commenting on the topic title.
This seems to have been fixed in version 1.4.9-beta 1

Tomorrow I will update the main servers to the latest version and report the results.

 

[WolverinDEV]

Top

 

[Vafin]

I checked, in version 1.4.10 there are no crashes of the user with the newly created server group. There are rare crashes, but they are not related to this problem. So, all is well, you can close the topic .

 

[WolverinDEV]

//Closed