Author Topic: Probleme mit den QueryBots  (Read 4426 times)

Jan Brockmann

  • JTS3ServerMod Internal
  • *****
  • Posts: 44
    • View Profile
Probleme mit den QueryBots
« on: November 26, 2019, 06:19:55 PM »
Hallo,

in der letzten Zeit werden manche Bots einfach nicht geladen, bzw. „Bot nicht erreichbar"
wenn ich z. B. die Instanzen mal manuell neu lade dann kommt auch immer ein Fehler, dass ein Fehler aufgetreten ist.

Stefan1200

  • Administrator
  • *****
  • Posts: 2244
    • View Profile
Re: Probleme mit den QueryBots
« Reply #1 on: November 26, 2019, 06:22:14 PM »
Was steht in der JTS3ServerMod_InstanceManager.log? Aber ab und zu funktioniert das Starten und Beenden über das Web Interface einwandfrei?

Jan Brockmann

  • JTS3ServerMod Internal
  • *****
  • Posts: 44
    • View Profile
Re: Probleme mit den QueryBots
« Reply #2 on: November 27, 2019, 02:50:21 PM »
Hey,

das Stoppen funktioniert einwandfrei (also falls der Bot auch erreichbar ist) nur ab und zu passiert auch das hier siehe Anhang.

Stefan1200

  • Administrator
  • *****
  • Posts: 2244
    • View Profile
Re: Probleme mit den QueryBots
« Reply #3 on: November 27, 2019, 05:39:46 PM »
Vermutlich blockst du Javascript im Browser, denn der Status wird immer per Javascript nachgeladen.

Fehler im Browser Protokoll?

Jan Brockmann

  • JTS3ServerMod Internal
  • *****
  • Posts: 44
    • View Profile
Re: Probleme mit den QueryBots
« Reply #4 on: November 28, 2019, 08:53:06 AM »
Wo kann ich den Browser Protokoll sehen?

Stefan1200

  • Administrator
  • *****
  • Posts: 2244
    • View Profile
Re: Probleme mit den QueryBots
« Reply #5 on: November 30, 2019, 10:40:36 AM »
Teste einfach mal mit einem anderen Browser ohne Addons / Erweiterungen.

Jan Brockmann

  • JTS3ServerMod Internal
  • *****
  • Posts: 44
    • View Profile
Re: Probleme mit den QueryBots
« Reply #6 on: November 30, 2019, 01:11:01 PM »
Jo, werde ich nacher testen!

Jan Brockmann

  • JTS3ServerMod Internal
  • *****
  • Posts: 44
    • View Profile
Re: Probleme mit den QueryBots
« Reply #7 on: November 30, 2019, 02:49:10 PM »
Ich habe es gerade mit einem anderen Browser getestet aber jetzt kommt nur noch der Fehler

Keinen Service auf der IP-Adresse / Port erreicht! Stelle sicher, dass der JTS3ServerMod Prozess läuft und die telnet_enable und telnet_run_forever Einstellungen in der JTS3ServerMod_InstanceManager.cfg aktiviert sind!

Stefan1200

  • Administrator
  • *****
  • Posts: 2244
    • View Profile
Re: Probleme mit den QueryBots
« Reply #8 on: November 30, 2019, 03:06:32 PM »
Und was steht in der JTS3ServerMod_InstanceManager.log Datei?

Jan Brockmann

  • JTS3ServerMod Internal
  • *****
  • Posts: 44
    • View Profile
Re: Probleme mit den QueryBots
« Reply #9 on: December 04, 2019, 04:04:52 PM »
Und was steht in der JTS3ServerMod_InstanceManager.log Datei?

 :o

Code: [Select]
2019-11-30 13:44:39 START_MANAGER JTS3ServerMod 6.5.5 Hosting Edition (27.01.2019) Instance Manager started...
2019-11-30 13:44:39 SYSTEM_INFO Operating System : Linux (version: 4.19.0-6-amd64 / arch: amd64)
2019-11-30 13:44:39 SYSTEM_INFO Used Java Version: 11.0.5 (path: /usr/lib/jvm/java-11-openjdk-amd64)
2019-11-30 13:44:39 SYSTEM_INFO Current directory: /home/JTS3ServerMod_HostingEdition
2019-11-30 13:44:39 CONFIG Loading InstanceManager config file from: /home/JTS3ServerMod_HostingEdition/config/JTS3ServerMod_InstanceManager.cfg
2019-11-30 13:44:39 CONFIG Bot chat command !exec is disabled!
2019-11-30 13:44:39 CONFIG Multi IP Mode disabled!
2019-11-30 13:44:40 LOGGER_SQL_CONNECT Successfully connected to MySQL server for logging!
2019-11-30 13:44:40 CONFIG MySQL mode enabled!
2019-11-30 13:44:41 LICENCE_CHECK Licence key is valid! Thank you very much for your support, Jan!
2019-11-30 13:44:41 START_INSTANCE Start virtual bot instance bot1_1...
2019-11-30 13:44:41 START_INSTANCE Start virtual bot instance bot3_2...
2019-11-30 13:44:41 TELNET_START Query Interface started on port 5873!
2019-12-04 11:45:47 LOGGER_SQL_ERROR Critical: Cannot write log entry to MySQL server!
2019-12-04 11:45:47 JTS3ServerMod 6.5.5 Hosting Edition (27.01.2019): EXCEPTION
com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 337.453.274 milliseconds ago.  The last packet sent successfully to the server was 337.453.278 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:425)
at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:990)
at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3751)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2512)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2683)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2495)
at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1903)
at com.mysql.jdbc.PreparedStatement.executeUpdateInternal(PreparedStatement.java:2124)
at com.mysql.jdbc.PreparedStatement.executeUpdateInternal(PreparedStatement.java:2058)
at com.mysql.jdbc.PreparedStatement.executeLargeUpdate(PreparedStatement.java:5158)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2043)
at de.stefan1200.jts3servermod.t.a(Unknown Source)
at de.stefan1200.jts3servermod.t.a(Unknown Source)
at de.stefan1200.jts3servermod.JTS3ServerMod.addLogEntry(Unknown Source)
at de.stefan1200.jts3servermod.JTS3ServerMod.a(Unknown Source)
at de.stefan1200.jts3servermod.JTS3ServerMod.d(Unknown Source)
at de.stefan1200.jts3servermod.s.run(Unknown Source)
at java.base/java.util.TimerThread.mainLoop(Timer.java:556)
at java.base/java.util.TimerThread.run(Timer.java:506)
Caused by: java.net.SocketException: Die Verbindung wurde vom Kommunikationspartner zurückgesetzt (Write failed)
at java.base/java.net.SocketOutputStream.socketWrite0(Native Method)
at java.base/java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:110)
at java.base/java.net.SocketOutputStream.write(SocketOutputStream.java:150)
at java.base/java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:81)
at java.base/java.io.BufferedOutputStream.flush(BufferedOutputStream.java:142)
at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3733)
... 16 more
2019-12-04 11:45:47 LOGGER_SQL_ERROR Try to reconnect to MySQL server...
2019-12-04 11:45:47 LOGGER_SQL_CONNECT Successfully connected to MySQL server for logging!
2019-12-04 14:54:36 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 14:54:36 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 14:54:46 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 14:54:46 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 14:54:56 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 14:54:56 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 14:55:17 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 14:55:17 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 14:55:48 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 14:55:48 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 14:55:58 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 14:55:58 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 14:56:19 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 14:56:19 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 14:57:21 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 14:57:21 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 14:57:31 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 14:57:31 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 14:57:41 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 14:57:41 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 14:57:51 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 14:57:51 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 14:58:02 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 14:58:02 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 14:58:12 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 14:58:12 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 14:58:22 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 14:58:22 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 14:58:33 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 14:58:33 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 14:58:43 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 14:58:43 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 14:58:53 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 14:58:53 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 14:59:03 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 14:59:03 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 14:59:14 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 14:59:14 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 14:59:24 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 14:59:24 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 14:59:35 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 14:59:35 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 14:59:45 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 14:59:45 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 14:59:55 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 14:59:55 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 15:00:06 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 15:00:07 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 15:00:16 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 15:00:16 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 15:00:26 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 15:00:26 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 15:00:36 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 15:00:36 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 15:00:47 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 15:00:47 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 15:00:57 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 15:00:57 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 15:01:07 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 15:01:07 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 15:01:18 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 15:01:18 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 15:01:28 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 15:01:28 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 15:01:38 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 15:01:38 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 15:01:48 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 15:01:48 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 15:01:59 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 15:01:59 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 15:02:09 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 15:02:09 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 15:02:19 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 15:02:19 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 15:02:30 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 15:02:30 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 15:02:40 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 15:02:40 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 15:02:50 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 15:02:50 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 15:03:01 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 15:03:01 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 15:03:11 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 15:03:11 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 15:03:21 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 15:03:21 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 15:03:32 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 15:03:32 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 15:03:42 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 15:03:42 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 15:03:52 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 15:03:52 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
2019-12-04 15:04:03 TELNET_CONNECTION Accepted telnet connection from 116.203.132.69...
2019-12-04 15:04:03 TELNET_CONNECTION Closed telnet connection to 116.203.132.69...
« Last Edit: December 04, 2019, 04:10:25 PM by Jan »

Stefan1200

  • Administrator
  • *****
  • Posts: 2244
    • View Profile
Re: Probleme mit den QueryBots
« Reply #10 on: December 04, 2019, 09:28:19 PM »
Sieht doch gut aus. Also das Web Interface mit der IP 116.203.132.69 scheint keine Probleme zu haben.

Jan Brockmann

  • JTS3ServerMod Internal
  • *****
  • Posts: 44
    • View Profile
Re: Probleme mit den QueryBots
« Reply #11 on: December 05, 2019, 04:16:53 PM »
Sieht doch gut aus. Also das Web Interface mit der IP 116.203.132.69 scheint keine Probleme zu haben.

hmm und was jetzt?

Stefan1200

  • Administrator
  • *****
  • Posts: 2244
    • View Profile
Re: Probleme mit den QueryBots
« Reply #12 on: December 05, 2019, 06:31:14 PM »
hmm und was jetzt?

116.203.132.6 ist deine Webseite? Falls ja, funktioniert laut Log alles.

Jan Brockmann

  • JTS3ServerMod Internal
  • *****
  • Posts: 44
    • View Profile
Re: Probleme mit den QueryBots
« Reply #13 on: December 06, 2019, 10:32:26 AM »
hmm und was jetzt?

116.203.132.6 ist deine Webseite? Falls ja, funktioniert laut Log alles.
Das ist der Webspace worauf alles läuft!
ich kann im Interface die Bots nicht starten.. weil da steht Bot nicht erreichbar...

monster010

  • JTS3ServerMod Internal
  • *****
  • Posts: 75
    • View Profile
    • monster010 Blog
Re: Probleme mit den QueryBots
« Reply #14 on: December 06, 2019, 01:15:39 PM »
Das ist der Webspace worauf alles läuft!
ich kann im Interface die Bots nicht starten.. weil da steht Bot nicht erreichbar...
Tippe mal du meinst damit, dass der JTS3ServerMod und das Webspace auf einem Server laufen.
Wenn das so ist, läuft vllt eine Firewall auf dem Server? Wenn ja, dann wuerde mich interessieren, ob das
Interface per 127.0.0.1 oder per 116.203.132.69 auf den Bot zugreift.