Messages

Updated JTS3ServerMod Hosting Edition to version 6.2.0. Web Interface was updated to build 3022. See changelog from the first post for a list of changes.

New Version 6.2.0 (03.09.2016)

Check first post for the changes (Changelog).

Neue Version 6.2.0 (03.09.2016)

Lese den ersten Beitrag für die Änderungen (Entwicklungsgeschichte).

[-= Sichtbarkeit vom Bot im Teamspeak =-]

wenn ich neue Channel im TS erstelle, werden diese mir nicht in den Auswahl Fenstern der Funktionen angezeigt, es sind immer nur die drin, als der Server erstellt wurde. Wo dran kann es liegen?

Das Webinterface hat einen Cache, der nach 2 Stunden automatisch aktualisiert wird. Wenn du den Channel Namen innerhalb von 2 Stunden nach dem Erstellen im Web Interface sehen musst, kannst du auf der Bot Einstellungen Seite (da wo alle Funktionen aufgelistet sind) den Cache neu laden lassen, dann ist auch der neue Channel zu sehen.

Desweiteren suche ich, das der bot auf dem TS angezeigt wird. Habe es schon mal gesehen, finde es einfach nicht wieder.

Bitte die Anleitung lesen, die beim Bot dabei liegt, Abschnitt: -= Sichtbarkeit vom Bot im Teamspeak =-

New release:

Version 1.3 Final (28.08.2016)
+ Added optional MySQL Connector settings to the config file (settings about compression and encryption of the MySQL connections).
- Bugfix: JTSDNS is now compatible with the new Teamspeak version 3.1. (thx to BigBear)
o JTSDNS version will be printed to log file after starting JTSDNS.
o Updated MySQL Connector/J to version 5.1.39.

Neue Version 1.3, welche jetzt auch mit dem Teamspeak 3.1 Beta Client kompatibel ist und weitere kleinere Neuerungen bringt.

[-= Needed Permissions for the bot =-]

JTS3ServerMod   EXCEPTION   de.stefan1200.jts3serverquery.TS3ServerQueryException: ServerQuery Error 2568: insufficient client permissions - Permission ID: 43
JTS3ServerMod   EXCEPTION   de.stefan1200.jts3serverquery.TS3ServerQueryException: ServerQuery Error 2568: insufficient client permissions - Permission ID: 29

Permission ID 29 = b_virtualserver_client_dblist
Permission ID 43 = b_virtualserver_notify_register

Please read the section -= Needed Permissions for the bot =-
https://www.stefan1200.de/documentation/jts3servermod_mysql/readme.html

After a Teamviewer session this problem was identified and solved: The JTS3ServerMod used a different database than the web interface. After changing the MySQL settings at the JTS3ServerMod, everything was working fine.

Sure, your are not present today?

I think not, maybe later this day for a short time, but I can't promise this currently. If I have time, I will connect to your TS3 server and check if you are online. Which name do you have on your TS3 server?

Can we meet at the weekend, so I can check your configuration using Teamviewer?

]
How to know if it is the same database

Well, if you used the same MySQL Server IP and database name at the web interface and in the JTS3ServerMod_InstanceManager.cfg file, than you should be fine.

What happens, if you restart the JTS3ServerMod?

Do the web interface and JTS3ServerMod really use the same database?

I have reload no work, delete and create bot no work, I have: Bot unknown!

What will be displayed on the Query Interface settings?

You created the bot before you made the query interface working. But that is easy to fix.

Go to the bot list page and click on manual instance list reload. Wait 15 seconds and the status should change.

Some of you may now, that the Licence Check of the JTS3ServerMod Hosting Edition has a grace time of 12 hours, if the licence server is offline. Last night the database was not working, but the web server itself did. The server side script was not prepared for this and was sending the wrong answer to the JTS3ServerMod. That is the reason, why this grace time was not working and all your bots was stopping.

After doing a server side change, I simulated a database downtime and tested it with the JTS3ServerMod. The grace time is working now, in future a downtime with up to 12 hours of the database and/or web server will not affect a running JTS3ServerMod. Only starting a stopped JTS3ServerMod will not work while the website or database is offline.

This will give my hoster more time to fix the problems in future. No update of the JTS3ServerMod is necessary, because it was a server side fix at the licence server script.

If the licence server is not reachable, you get a message in the JTS3ServerMod_InstanceManager.log file:
LICENCE_CHECK   Error while validating heartbeat token! Reason: Licence Server answer: 500 Internal Server Error