Quote3.|-- core31.hel1.hetzner.com 0.0% 10 0.6 0.8 0.4 2.4 0.5
4.|-- vswitchgw.juniper2.dc1.hel1.hetzner.com 0.0% 10 0.8 0.6 0.4 0.8 0.0
5.|-- web4.xxxxxx.de 60.0% 10 400.6 250.7 200.7 400.6 99.9
Quote3.|-- core32.hel1.hetzner.com 0.0% 10 1.2 0.7 0.4 1.5 0.0
4.|-- vswitchgw.juniper2.dc1.hel1.hetzner.com 0.0% 10 0.4 1.2 0.4 4.3 1.1
5.|-- web4.xxxxxx.de 80.0% 10 200.1 267.1 200.1 334.1 94.8
Quote2022-05-11 19:12:47 LICENCE_CHECK Error while validating heartbeat token! Reason: java.net.ConnectException: Connection timed out (Connection timed out)
2022-05-11 23:12:47 LICENCE_CHECK Error while validating heartbeat token! Reason: java.net.ConnectException: Connection timed out (Connection timed out)
2022-05-12 07:12:48 LICENCE_CHECK Error while validating heartbeat token! Reason: java.net.ConnectException: Connection timed out (Connection timed out)
QuoteMai Mi 11 14:54:41: JTS3Bot started
Error while validating licence key! Reason: java.net.ConnectException: Connection timed out (Connection timed out)
Mai Mi 11 14:54:41: JTS3Bot started
Error while validating licence key! Reason: java.net.ConnectException: Connection timed out (Connection timed out)
Mai Mi 11 14:58:11: JTS3Bot started
Error while validating licence key! Reason: java.net.ConnectException: Connection timed out (Connection timed out)
Mai Mi 11 15:00:51: JTS3Bot started
Error while validating licence key! Reason: java.net.ConnectException: Connection timed out (Connection timed out)
Quote from: Gramse on February 18, 2022, 06:31:16 PM
Me and a friend have checked logs high and low and come to the conclusion that JTS3 and TS3 did nothing wrong.
The culprit was actually the MYSQL Server it self that for some reason restarted it self. And thus JTS3 made an error
in the log file.
Page created in 0.034 seconds with 15 queries.