• Hey Guest, we're evolving the future of TeaSpeak.
    You're invited to join the discussion here!

Completed Failed to write datagram packet for connection

infernus

Active member
Hello,

when we're running a teaspeak server instance for more then a few days, it starts dropping connections on user join. The user is in a reconnect loop for around 5-100 tries until it starts working again.

When it occurs, it's happening globally on all virtual servers.

We currently have ~30 virtual servers running on that instance.

Until now, a simple reboot of the teaspeak server software helped solving the problem, but now it even occurs after restart and the reconnect loop won't stop at all.

The client is stuck in a channel, unable to chat, speak or change his channel.


This is from the error log of a server instance (the global log doesn't say anything strange):
Rich (BB code):
[2019-01-17 20:56:26] [INFO]     22 | Voice client CLIENT_ID_1 (CLIENT_NAME_1) from CLIENT_IP_1:45758 left.
[2019-01-17 20:56:26] [CRITICAL]    22 | Failed to write datagram packet for client CLIENT_IP_2:57773 (errno: 97 message: Address family not supported by protocol). Closing connection
[2019-01-17 20:56:26] [INFO]     22 | Voice client CLIENT_ID_2 (CLIENT_NAME_2) from CLIENT_IP_2:57773 joined.
[2019-01-17 20:56:26] [INFO]     22 | Voice client CLIENT_ID_2 (CLIENT_NAME_2) from CLIENT_IP_2:57773 left.
[2019-01-17 20:56:49] [INFO]     22 | [CLIENT_IP_1:45758/CLIENT_NAME_1 | 0] Client may cached a old permission list (Server is newer than the client's last join)
[2019-01-17 20:56:49] [ERROR]    22 | Command handling of command clientinit needs 19ms
[2019-01-17 20:56:49] [ERROR]    22 | [CLIENT_IP_1:45758/CLIENT_NAME_1 | 0] Handling of packet Command needs more than 10ms (20ms)
[2019-01-17 20:56:49] [INFO]     22 | Voice client CLIENT_ID_1 (CLIENT_NAME_1) from CLIENT_IP_1:45758 joined.
[2019-01-17 20:56:49] [ERROR]    22 | Command handling of command connectioninfoautoupdate needs 29ms
[2019-01-17 20:56:49] [ERROR]    22 | [CLIENT_IP_1:45758/CLIENT_NAME_1 | 5] Handling of packet Command needs more than 10ms (29ms)
[2019-01-17 20:56:51] [ERROR]    22 | Command handling of command clientmove needs 11ms
[2019-01-17 20:56:51] [ERROR]    22 | [CLIENT_IP_1:45758/CLIENT_NAME_1 | 5] Handling of packet Command needs more than 10ms (12ms)
[2019-01-17 20:56:54] [INFO]     22 | [CLIENT_IP_2:57773/CLIENT_NAME_2 | 0] Client may cached a old permission list (Server is newer than the client's last join)
[2019-01-17 20:56:54] [ERROR]    22 | Command handling of command clientinit needs 19ms
[2019-01-17 20:56:54] [ERROR]    22 | [CLIENT_IP_2:57773/CLIENT_NAME_2 | 6] Handling of packet Command needs more than 10ms (20ms)
[2019-01-17 20:56:54] [ERROR]    22 | Could not resolve country for ip CLIENT_IP_2|CLIENT_NAME_2
[2019-01-17 20:56:54] [INFO]     22 | Voice client CLIENT_ID_2 (CLIENT_NAME_2) from CLIENT_IP_2:57773 joined.
[2019-01-17 20:56:54] [CRITICAL]    22 | Failed to write datagram packet for client CLIENT_IP_1:45758 (errno: 101 message: Network is unreachable). Closing connection
[2019-01-17 20:56:54] [INFO]     22 | Voice client CLIENT_ID_1 (CLIENT_NAME_1) from CLIENT_IP_1:45758 left.
[2019-01-17 20:57:24] [INFO]     22 | [CLIENT_IP_1:45758/CLIENT_NAME_1 | 0] Client may cached a old permission list (Server is newer than the client's last join)
[2019-01-17 20:57:24] [ERROR]    22 | Command handling of command clientinit needs 24ms
[2019-01-17 20:57:24] [ERROR]    22 | [CLIENT_IP_1:45758/CLIENT_NAME_1 | 0] Handling of packet Command needs more than 10ms (25ms)
[2019-01-17 20:57:24] [INFO]     22 | Voice client CLIENT_ID_1 (CLIENT_NAME_1) from CLIENT_IP_1:45758 joined.
[2019-01-17 20:57:24] [CRITICAL]    22 | Failed to write datagram packet for client CLIENT_IP_1:45758 (errno: 101 message: Network is unreachable). Closing connection
[2019-01-17 20:57:24] [INFO]     22 | Voice client CLIENT_ID_1 (CLIENT_NAME_1) from CLIENT_IP_1:45758 left.
Also please note that CLIENT_1 is joining using a IPv4 and CLIENT_2 is joining using a IPv6 address.
 

infernus

Active member
Maybe it has something to do with IPv4 / IPv6?

I'm disabling IPv6 to find out.


Edit:
The problem seems to occur when a user joins over IPv4 and another one joins over IPv6 (also happens when you reverse it)