Hello.
The server stops responding to any telnet/ts3 client connections after running for a couple hours.
This has happended every day so far. There is no crash logs created whatsoever unfortunately.
It takes around 12 hours of uptime, before the next connecting client crashes the server.
The logs just end in the middle of the connection process:
After that there is absolutely not response from the server anymore.
Journalctl has no reported errors either, so the process is still running.
The server stops responding to any telnet/ts3 client connections after running for a couple hours.
This has happended every day so far. There is no crash logs created whatsoever unfortunately.
It takes around 12 hours of uptime, before the next connecting client crashes the server.
The logs just end in the middle of the connection process:
Code:
[2018-08-25 18:27:55] [ERROR] Timer ConnectedClient::tick needs more than 3724 microseconds. Max allowed was 2000 microseconds.
[2018-08-25 18:27:55] [ERROR] 3 | Ticking of client XX.XX.X.XXX:56245 (Username) needs more that 2500 microseconds! (5345 microseconds)
END LOG
Code:
[2018-08-26 15:23:41] [DEBUG] 3 | [XX.XX.X.XXX:65297/undefined] Creating VoiceClient instance at 0x52733ae4
[2018-08-26 15:23:41] [DEBUG] 3 | Allocated new voice client connection at 0x393015a8
[2018-08-26 15:23:41] [DEBUG] 3 | Remote address (v4) 192.168.178.41 destination address 192.168.178.41
[2018-08-26 15:23:41] [DEBUG] 3 | Having new voice client. Remote address: XX.XX.X.XXX:65297
[2018-08-26 15:23:41] [ERROR] 3 | [XX.XX.X.XXX:65297/undefined] Handling of packet Init1 needs more than 10ms (11ms)
[2018-08-26 15:23:41] [DEBUG] 3 | [XX.XX.X.XXX:65297/undefined] Got client 3.1 protocol with build timestamp 177256836
[2018-08-26 15:23:41] [ERROR] 3 | [XX.XX.X.XXX:65297/undefined] Handling of packet Init1 needs more than 10ms (164ms)
[2018-08-26 15:23:42] [DEBUG] 3 | [XX.XX.X.XXX:65297/undefined] Got client ek!
[2018-08-26 15:23:42] [ERROR] 3 | [XX.XX.X.XXX:65297/undefined] Handling of packet Command needs more than 10ms (17ms)
[2018-08-26 15:23:42] [DEBUG] 3 | [Property] Changing client property 'client_totalconnections' for 6 (New value: 12, SQL: UPDATE clients SET connections = :value WHERE serverId = :serverId AND cldbid = :cldbid)
[2018-08-26 15:23:42] [DEBUG] GEN | Query permission manager
[2018-08-26 15:23:42] [DEBUG] 3 | Loaded client from database. Database id: 6 Unique id: XXXX
[2018-08-26 15:23:42] [DEBUG] 3 | [XX.XX.X.XXX:65297/Username] Got client init. (HWID: XXXX,XXXX)
[2018-08-26 15:23:42] [DEBUG] 3 | [Permission] Value test result for test type 0.
[2018-08-26 15:23:42] [DEBUG] 3 | [Permission] Permission: b_client_ignore_bans Required value: 1 Gained value: 1 Force required: 1 Channel: none Result: 1
[2018-08-26 15:23:42] [DEBUG] 3 | [Property] Changing client property 'client_lastconnected' for 6 (New value: 1535289822, SQL: UPDATE clients SET lastConnect = :value WHERE serverId = :serverId AND cldbid = :cldbid)
[2018-08-26 15:23:42] [DEBUG] 3 | [Property] Changing client property 'client_totalconnections' for 6 (New value: 13, SQL: UPDATE clients SET connections = :value WHERE serverId = :serverId AND cldbid = :cldbid)
[2018-08-26 15:23:42] [ERROR] 3 | Command handling of command clientinit needs 47ms
[2018-08-26 15:23:42] [DEBUG] 3 | Updating server property: virtualserver_last_client_connect. New value: 1535289822. Query: UPDATE properties SET value = :value WHERE serverId = :sid AND type = :type AND id = :id AND key = :key
[2018-08-26 15:23:42] [ERROR] 3 | [XX.XX.X.XXX:65297/Username] Handling of packet Command needs more than 10ms (49ms)
[2018-08-26 15:23:42] [DEBUG] 3 | Updating server property: virtualserver_client_connections. New value: 30. Query: UPDATE properties SET value = :value WHERE serverId = :sid AND type = :type AND id = :id AND key = :key
[2018-08-26 15:23:42] [DEBUG] GEN | Client Username|XX.XX.X.XXX comes from XXXXX
[2018-08-26 15:23:42] [DEBUG] 3 | [XX.XX.X.XXX:65297/Username] Got a channel talk power of 75 Talk power set is 0
[2018-08-26 15:23:42] [DEBUG] 3 | Client id: 1
END LOG
Journalctl has no reported errors either, so the process is still running.