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.
Quote from: Stefan1200 on February 14, 2022, 09:33:47 PM
Okay, this two lines are related together:
2022-02-13 16:26:34 JTS3ServerMod ERROR Error while getting server info!
2022-02-13 16:26:34 JTS3ServerMod EXCEPTION de.stefan1200.jts3serverquery.TS3ServerQueryException: ServerQuery Error 1280: database error
Every some minutes the JTS3ServerMod sends the command serverinfo to the TS3 server, if I remember correctly. And if that fails, the bot quits.
In fact, I have no idea, why the TS3 server answers with "database error" on that command. Maybe the TS3 server really has an database error? Maybe it helps if you check the TS3 server logs.
Quote from: Stefan1200 on February 14, 2022, 06:58:41 PM
I guess the client Gramse used the chat command !botversion
Thats the reason for the first two lines. If course the id changes, because that is different with every connect to the TS3 server.
Maybe the HTTPS request is getting blocked by a firewall or something.
The EXCEPTION line "database error" is from the TS3 server. A server query command got the error message "database error" from the TS3 server. Maybe a full log would be more helpfull.
Page created in 0.010 seconds with 12 queries.