Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
Allgemeine Diskussionen / Re: JTS3 kann Clientlist nicht Lesen / TS3 Krasch
« Last post by LFS96 on August 26, 2022, 10:09:04 PM »
Hi, danke für die Information, wo findet man den Debug-Log oder wie schalte ich ihn ein?
22
Allgemeine Diskussionen / Re: JTS3 kann Clientlist nicht Lesen / TS3 Krasch
« Last post by Stefan1200 on August 26, 2022, 09:45:35 PM »
Der TS3 Server hat doch auch ein Debug Log. Da müsste doch irgendwas drin stehen. Ansonsten ist vermutlich das offizielle TS3 Forum der passendere Ort.
23
Allgemeine Diskussionen / JTS3 kann Clientlist nicht Lesen / TS3 Krasch
« Last post by LFS96 on August 26, 2022, 08:49:06 PM »
Hi,

ich suche einen Fehler, ich weiß nicht, aus welchem System dieser kommt.
Glücklicherweise sehen es die Nutzer nicht bzw. hören nur zwei Sekunden nichts.
Ich glaube eigentlich nicht, dass der JTS3 Bot damit in Zusammenhang steht.

Folgendes passiert:
- an zufälligen Zeitpunkten geht die Verbindung zwischen TS3 und MariaDB verloren.
- der TS3 stürzt ab.
- Docker startet alles neu und in (15min - 72Std) gehts wieder los.

Die Systemkonfiuration:

Code: [Select]
version: '3.1'
services:
  teamspeak:
    image: teamspeak:latest
    container_name: teamspeak
    restart: always
    volumes:
      - "./data/teamspeak:/var/ts3server/"
      - "./licensekey.dat:/var/ts3server/licensekey.dat"
    ports:
      - 9987:9987/udp
      - 10011:10011
      - 30033:30033
    environment:
      TS3SERVER_DB_PLUGIN: ts3db_mariadb
      TS3SERVER_DB_SQLCREATEPATH: create_mariadb
      TS3SERVER_DB_HOST: db
      TS3SERVER_DB_USER: root
      TS3SERVER_DB_PASSWORD: XXXXXXXXXXXXXXXXXX
      TS3SERVER_DB_NAME: teamspeak
      TS3SERVER_DB_WAITUNTILREADY: 30
      TS3SERVER_LICENSE: accept
      TS3SERVER_DB_CONNECTIONS: 20
    depends_on:
      - db
  db:
    image: mariadb
    container_name: teamspeak-db
    restart: always
    volumes:
      - "./data/teamspeak-db:/var/lib/mysql"
    environment:
      MYSQL_ROOT_PASSWORD: XXXXXXXXXXXXXXX
      MYSQL_DATABASE: teamspeak

Ich versuche Mal die Logs sinnvoll darzustellen:

JTS3:
Code: [Select]
2022-08-26 15:16:48     Function CleanDefaultChannel    INFO    Client "Max Mustermann" (db id: 123) was idle, client was moved and got a message!
2022-08-26 17:23:15     JTS3ServerMod   CRITICAL        Error while getting client list!
2022-08-26 17:23:15     JTS3ServerMod   EXCEPTION       Bot Version: 6.5.7 (31.01.2020)
java.lang.IllegalStateException: null object, maybe connection to TS3 server interrupted.
        at de.stefan1200.jts3serverquery.JTS3ServerQuery.readIncoming(Unknown Source)
        at de.stefan1200.jts3serverquery.JTS3ServerQuery.doInternalCommand(Unknown Source)
        at de.stefan1200.jts3serverquery.JTS3ServerQuery.getList(Unknown Source)
        at de.stefan1200.jts3serverquery.JTS3ServerQuery.getList(Unknown Source)
        at de.stefan1200.jts3servermod.JTS3ServerMod.d(Unknown Source)
        at de.stefan1200.jts3servermod.l.run(Unknown Source)
        at java.base/java.util.TimerThread.mainLoop(Timer.java:556)
        at java.base/java.util.TimerThread.run(Timer.java:506)
2022-08-26 17:23:15     JTS3ServerMod   INFO    Unloaded all functions!
2022-08-26 17:23:15     JTS3ServerMod   INFO    Reconnecting in 65 seconds...
2022-08-26 17:24:20     JTS3ServerMod   STATUS  Virtual bot instance "bot1" starts now (build 6508)

MariaDB:
Code: [Select]
2022-08-25  7:28:35 0 [Note] InnoDB: Buffer pool(s) load completed at 220825  7:28:35
2022-08-26 17:23:15 23 [Warning] Aborted connection 23 to db: 'teamspeak' user: 'root' host: '172.31.0.3' (Got an error reading communication packets)
2022-08-26 17:23:15 22 [Warning] Aborted connection 22 to db: 'teamspeak' user: 'root' host: '172.31.0.3' (Got an error reading communication packets)
2022-08-26 17:23:15 20 [Warning] Aborted connection 20 to db: 'teamspeak' user: 'root' host: '172.31.0.3' (Got an error reading communication packets)
2022-08-26 17:23:15 19 [Warning] Aborted connection 19 to db: 'teamspeak' user: 'root' host: '172.31.0.3' (Got an error reading communication packets)
2022-08-26 17:23:15 21 [Warning] Aborted connection 21 to db: 'teamspeak' user: 'root' host: '172.31.0.3' (Got an error reading communication packets)
2022-08-26 17:23:15 17 [Warning] Aborted connection 17 to db: 'teamspeak' user: 'root' host: '172.31.0.3' (Got an error reading communication packets)
2022-08-26 17:23:15 16 [Warning] Aborted connection 16 to db: 'teamspeak' user: 'root' host: '172.31.0.3' (Got an error reading communication packets)
2022-08-26 17:23:15 15 [Warning] Aborted connection 15 to db: 'teamspeak' user: 'root' host: '172.31.0.3' (Got an error reading communication packets)
2022-08-26 17:23:15 14 [Warning] Aborted connection 14 to db: 'teamspeak' user: 'root' host: '172.31.0.3' (Got an error reading communication packets)
2022-08-26 17:23:15 18 [Warning] Aborted connection 18 to db: 'teamspeak' user: 'root' host: '172.31.0.3' (Got an error reading communication packets)
2022-08-26 17:23:15 13 [Warning] Aborted connection 13 to db: 'teamspeak' user: 'root' host: '172.31.0.3' (Got an error reading communication packets)
2022-08-26 17:23:15 12 [Warning] Aborted connection 12 to db: 'teamspeak' user: 'root' host: '172.31.0.3' (Got an error reading communication packets)
2022-08-26 17:23:15 11 [Warning] Aborted connection 11 to db: 'teamspeak' user: 'root' host: '172.31.0.3' (Got an error reading communication packets)
2022-08-26 17:23:15 10 [Warning] Aborted connection 10 to db: 'teamspeak' user: 'root' host: '172.31.0.3' (Got an error reading communication packets)
2022-08-26 17:23:15 8 [Warning] Aborted connection 8 to db: 'teamspeak' user: 'root' host: '172.31.0.3' (Got an error reading communication packets)
2022-08-26 17:23:15 9 [Warning] Aborted connection 9 to db: 'teamspeak' user: 'root' host: '172.31.0.3' (Got an error reading communication packets)
2022-08-26 17:23:15 7 [Warning] Aborted connection 7 to db: 'teamspeak' user: 'root' host: '172.31.0.3' (Got an error reading communication packets)
2022-08-26 17:23:15 4 [Warning] Aborted connection 4 to db: 'teamspeak' user: 'root' host: '172.31.0.3' (Got an error reading communication packets)
2022-08-26 17:23:15 5 [Warning] Aborted connection 5 to db: 'teamspeak' user: 'root' host: '172.31.0.3' (Got an error reading communication packets)
2022-08-26 17:23:15 6 [Warning] Aborted connection 6 to db: 'teamspeak' user: 'root' host: '172.31.0.3' (Got an error reading communication packets)

TS3:
Zeigt nur dass alle Joinen, es gibt kein

Bei Weitern Fragen immer raus damit.
Ich bin kurz davor, wieder  SQLite zu nutzen.

Grüße Fabian





24
Ja habe ich jetzt auch gemerkt, deshalb mit /8 weil ich beim neu starten des TS nie weiß ob die das selbe netzwerk wiederbekommen.
25
Falsche IP Adresse auf der query_ip_whitelist.txt vom TS3 Server. Durch Docker ändert sich ja die IP Adresse. Im TS3 log siehst du ja, welche IP Adresse vom JTS3ServerMod genutzt wird, die muss dann auf die query_ip_whitelist.txt
26
Hi,
auch wenn ich jetzt die Lösung gefunden habe, hier die Zusammenfassung:

Ich habe meinen Teamspeak in einen Dockercontainer gesteckt und hatte seit dem Update von Teamspeak auf 3.13.7 Problme, dass der JTS3 Bot sich nicht richtig verbunden hat. Es scheint was mit dem Anti-Flood zu tun zu haben.

Daraus ergebeben sich dann die Untenstehenden Logs.

Ich konnte mein Problem jetzt lösen, indem ich den JTS3-Bot auch in einen Docker gepackt habe.
Wenn man diesen Container dann noch in das Teamspeak-Netzwek packt, scheint der Antifload nicht mehr zu greifen.

Fragt mich nicht warum.

Code: [Select]
JTS3ServerMod 6.5.7 (31.01.2020) Instance Manager started...
Operating System : Linux (version: 5.10.0-16-amd64 / arch: amd64)
Used Java Version: 11.0.15 (path: /usr/lib/jvm/java-11-openjdk)
Current directory: /app
Writing InstanceManager log file to: /app/JTS3ServerMod_InstanceManager.log
Loading InstanceManager config file from: /app/config/JTS3ServerMod_InstanceManager.cfg
bot1: Writing bot log file to: /app/JTS3ServerMod_server1.log
bot1: Virtual bot instance "bot1" starts now (build 6508)
bot1 / NeuerBesucherMsg: Slow Mode is activated, if the bot gets banned by the TS3 server, you should disable the Server Group Notify!
bot1 / OKPMsg: Slow Mode is activated, if the bot gets banned by the TS3 server, you should disable the Server Group Notify!
bot1 / JoinMove: Slow Mode is activated, if the bot gets banned by the TS3 server, you should disable Auto Move!
bot1: Slow mode activated (using less commands at once)
bot1: Unable to connect to Teamspeak 3 server at 127.0.0.1!
bot1: java.net.ConnectException: Connection refused (Connection refused)
bot1: Reconnecting in 65 seconds...

Code: [Select]
25.08.2022 07:28:50 VirtualServer Info query client connected 'Private'(id:###) from 172.31.0.1:43728
25.08.2022 07:28:50 VirtualServerBase Info query client disconnected 'Private'(id:###) reason 'reasonmsg=disconnecting'
27
Quote
Error while validating licence key! Reason: java.net.ConnectException: Connection timed out: connect

Maybe blocked by the Windows Firewall? Something is blocking the HTTPS connection of the java process.
28
I did not changed nothing, just updated windows.

I also notice that other error:

2022-06-01 02:44:22   START_MANAGER   JTS3ServerMod 6.5.7 Hosting Edition (31.01.2020) Instance Manager started...
2022-06-01 02:44:22   SYSTEM_INFO   Operating System : Windows Server 2019 (version: 10.0 / arch: amd64)
2022-06-01 02:44:23   SYSTEM_INFO   Used Java Version: 1.8.0_333 (path: C:\Program Files\Java\jre1.8.0_333)
2022-06-01 02:44:24   SYSTEM_INFO   Current directory: C:\Program Files\JTS3ServerMod_HostingEdition
2022-06-01 02:44:26   CONFIG   Loading InstanceManager config file from: C:\Program Files\JTS3ServerMod_HostingEdition\config\JTS3ServerMod_InstanceManager.cfg
2022-06-01 02:44:26   CONFIG   Bot chat command !exec is disabled!
2022-06-01 02:44:26   CONFIG   Multi IP Mode disabled!
2022-06-01 02:44:30   LOGGER_SQL_CONNECT   Successfully connected to MySQL server for logging!
2022-06-01 02:44:31   CONFIG   MySQL mode enabled!
2022-06-01 02:45:11   LICENCE_CHECK   Error while validating licence key! Reason: java.net.ConnectException: Connection timed out: connect
2022-06-01 02:45:11   JTS3ServerMod 6.5.7 Hosting Edition (31.01.2020): EXCEPTION
java.net.ConnectException: Connection timed out: connect
   at java.net.DualStackPlainSocketImpl.connect0(Native Method)
   at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
   at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
   at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
   at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
   at java.net.PlainSocketImpl.connect(Unknown Source)
   at java.net.SocksSocketImpl.connect(Unknown Source)
   at java.net.Socket.connect(Unknown Source)
   at sun.security.ssl.SSLSocketImpl.connect(Unknown Source)
   at sun.security.ssl.SSLSocketImpl.<init>(Unknown Source)
   at sun.security.ssl.SSLSocketFactoryImpl.createSocket(Unknown Source)
   at de.stefan1200.jts3servermod.f.f(Unknown Source)
   at de.stefan1200.jts3servermod.f.<init>(Unknown Source)
   at de.stefan1200.jts3servermod.JTS3ServerMod.main(Unknown Source)
2022-06-01 02:45:11   QUIT_MANAGER   JTS3ServerMod licence is not valid, quitting now...
29
Make sure, that the JTS3ServerMod can connect to https://www.stefan1200.de
Also change the log level to INFO oder DEBUG, maybe I can see more details.
30
General Discussions / Error Unable to request the current JTS3ServerMod version
« Last post by PzSniper on May 31, 2022, 09:22:35 PM »
I run the bot since 2 years but yesterday after windows and java updated on Windows Server 2019 i notice this log error:

31/May/22 09:12:55PM    JTS3ServerMod    Error    Unable to request the current JTS3ServerMod version from https://www.stefan1200.de for the client PzSniper (Alex) (id: 110)!
31/May/22 09:12:11PM    JTS3ServerMod    Status    Activate log level: ERROR
31/May/22 09:12:11PM    JTS3ServerMod    Status    Virtual bot instance "ciwbot_ts" starts now (build 6508)
31/May/22 09:12:04PM    JTS3ServerMod    Status    Virtual bot instance "ciwbot_ts" stopped

can you help me?
Pages: 1 2 [3] 4 5 ... 10