Problem mit Aktualisierung auf 6.4.2

[Sandviper]

Hallo Stefan,
habe die neuste Version grade bei meinem Bot das Update eingespielt, danach steht im WI immer das der Bot nicht erreichbar ist. In der CFG stehen genau die Daten wie vorher. Ersetzte ich die dateien wieder gegen die alten läuft alles normal. Wenn ich den Ordner offen habe in dem die ganzen Bot Datein liegen, springen die Datein immer hin und her.

Log Datei:
2017-11-21 10:01:53   JTS3ServerMod   STATUS   Virtual bot instance "bot1" starts now (build 6402)
2017-11-21 10:01:53   JTS3ServerMod   STATUS   Activate log level: INFO
2017-11-21 10:01:53   JTS3ServerMod   ERROR   
2017-11-21 10:01:53   JTS3ServerMod   ERROR   **********************************************************************************
2017-11-21 10:01:53   JTS3ServerMod   ERROR   It seems you never touched the config, check file config/server1/JTS3ServerMod_server.cfg
2017-11-21 10:01:53   JTS3ServerMod   ERROR   **********************************************************************************
2017-11-21 10:01:53   JTS3ServerMod   ERROR   
2017-11-21 10:01:53   JTS3ServerMod   CRITICAL   Unable to connect to Teamspeak 3 server at ts3.server.net!
2017-11-21 10:01:53   JTS3ServerMod   EXCEPTION   java.net.UnknownHostException: ts3.server.net
2017-11-21 10:01:53   JTS3ServerMod   INFO   Unloaded all functions!
2017-11-21 10:01:53   JTS3ServerMod   STATUS   Virtual bot instance "bot1" stopped

Gruß VIP

[Stefan1200]

Diese Logdatei sollte es gar nicht geben, wenn du den MySQL Modus aktiviert hast. Sieht so aus, als wäre die JTS3ServerMod_InstanceManager.cfg falsch eingerichtet. Was steht in der JTS3ServerMod_InstanceManager.log Datei?

[Sandviper]

Hier der Inhalt der Instance Log:

2017-11-21 11:05:23   START_MANAGER   JTS3ServerMod 6.4.2 (07.10.2017) Instance Manager started...
2017-11-21 11:05:23   SYSTEM_INFO   Operating System : Windows Server 2008 R2 (version: 6.1 / arch: x86)
2017-11-21 11:05:23   SYSTEM_INFO   Used Java Version: 1.8.0_151 (path: C:\Program Files (x86)\Java\jre1.8.0_151)
2017-11-21 11:05:23   SYSTEM_INFO   Current directory: C:\TS3\bot
2017-11-21 11:05:23   LOCK_FILE   
2017-11-21 11:05:23   LOCK_FILE   ************************************************************************************************
2017-11-21 11:05:23   LOCK_FILE   Lock file still exists, it seems this JTS3ServerMod process is running twice! Please check this!
2017-11-21 11:05:23   LOCK_FILE   If you are sure, that the JTS3ServerMod process is not running twice, delete the file:
2017-11-21 11:05:23   LOCK_FILE   C:\TS3\bot\config\JTS3ServerMod_InstanceManager.cfg.lock
2017-11-21 11:05:23   LOCK_FILE   ************************************************************************************************
2017-11-21 11:05:23   LOCK_FILE   
2017-11-21 11:05:23   CONFIG   Loading InstanceManager config file from: C:\TS3\bot\config\JTS3ServerMod_InstanceManager.cfg
2017-11-21 11:05:23   CONFIG   Bot chat command !exec is disabled!
2017-11-21 11:05:23   QUIT_MANAGER   No instances enabled or needed entries missing in InstanceManager config file, quitting now...

Es wird nur ein JTS3ServerMod-Prozess ausgeführt. Wie ich schon geschrieben habe, mit der alten Version läuft es.

Habe nun mal diese JTS3ServerMod_InstanceManager.cfg.lock gelöscht, nun steht das in der Instance cfg:

2017-11-21 11:23:21   START_MANAGER   JTS3ServerMod 6.4.2 (07.10.2017) Instance Manager started...
2017-11-21 11:23:21   SYSTEM_INFO   Operating System : Windows Server 2008 R2 (version: 6.1 / arch: x86)
2017-11-21 11:23:21   SYSTEM_INFO   Used Java Version: 1.8.0_151 (path: C:\Program Files (x86)\Java\jre1.8.0_151)
2017-11-21 11:23:21   SYSTEM_INFO   Current directory: C:\TS3\bot
2017-11-21 11:23:21   CONFIG   Loading InstanceManager config file from: C:\TS3\bot\config\JTS3ServerMod_InstanceManager.cfg
2017-11-21 11:23:21   CONFIG   Bot chat command !exec is disabled!
2017-11-21 11:23:21   QUIT_MANAGER   No instances enabled or needed entries missing in InstanceManager config file, quitting now...

Die Instance Manager.cfg ist aber vorhanden.

Sieht so aus, als wäre die JTS3ServerMod_InstanceManager.cfg falsch eingerichtet.

Kann nicht sein, da ich diese einfach kopiert und eingefügt, also nichts verändert habe.

Hier die JTS3ServerMod_InstanceManager.cfg(passwörter/lizenzkey entfernt) :

# JTS3ServerMod Instance Manager config file
#
# This file must be saved with the encoding ISO-8859-1!

# A comma seperated list (without spaces) of unique user ids,
# which should be able to use bot full admin commands on all bot instances.
# Bot full admin can also see the TS3 server password and is able to use the !exec command.
# The unique user ids looks like this: mBbHRXwDAG7R19Rv3PorhMwbZW4=
bot_fulladmin_list = iTBNCqONzmBD1m49lUN0fZrLTV8=
# Allow !exec and !execwait commands for bot full admins? 1 = Yes, 0 = No
# This allow you to execute system commands.
# Only use !execwait for commands which quits within some seconds,
# because the bot waits for the end of this command to send you the text output of the program.
# Use !exec for commands with a longer runtime instead,
# this command don't send you any text output, because the bot don't wait for it.
bot_command_exec = 0
# Every time a bot full admin connects to the TS3 server it will be checked if an update for the JTS3ServerMod is available.
# If an update is available, a chat message will be sent to the bot full admin.
# 0 = disable, 1 = final versions, 2 = final and test versions
bot_update_check = 0
# The own personal licence key.
# Read the instructions, to know how to get one, at the download page of the JTS3ServerMod Hosting Edition.
bot_licence_key = xxxxxxxx
# Add a small delay in milliseconds to the bot starting process.
# Only change this value if you have problems starting all bots at once, like hanging bot threads.
delay_bot_start = 100

# Enable the multi IP mode. 1 = Enable, 0 = Disable
# If slow mode is activated, this feature split bot connections to the Teamspeak 3 servers.
# Events (Chat and some functions) and the Client Database Cache gets an own connection which should solve the IP ban problem.
multiipmode_enable = 0
# Local IP Address of the main connection, make sure that this is not the same as for chat and cache!
multiipmode_ip_main = 123.123.123.123
# Local IP Address of the chat connection, make sure that this is not the same as for main and cache!
multiipmode_ip_chat = 124.124.124.124
# Local IP Address of the cache connection, make sure that this is not the same as for chat and main!
multiipmode_ip_cache = 125.125.125.125
# First local port
multiipmode_portrange_min = 50000
# Last local port
# Make sure, that you have at least 3 ports for every bot, which use the slow mode!
multiipmode_portrange_max = 51999

# Enable the Query Interface of the JTS3ServerMod. 1 = Enable, 0 = Disable
# You are able to start, stop or reload a virtual bot instance using this Query Interface.
telnet_enable = 1
# Choose a port for the Query Interface, default port is 5873.
telnet_port = 5873
# Choose a password for the Query Interface.
# If this password is shorter than 6 characters, the Query Interface will be disabled!
telnet_password =xxxxxx
# Choose a network interface for the Query Interface. Only set a single ip address of a local network interface here.
# Set nothing here to bound the Query Interface to all network interfaces (default).
# Example: Set to 127.0.0.1 (IPv4) or ::1 (IPv6) to allow connections only from localhost.
telnet_bindTo =
# A comma seperated list (without spaces) of IP addresses, which are allowed to connect to the Query Interface.
# Leave empty, if every IP address is allowed to connect.
telnet_whitelist = 127.0.0.1
# Log query connection attempts to logfile? 1 = Enable, 0 = Disable
telnet_connection_log = 1
# Enable this to prevent that the JTS3ServerMod process quits if no bot instances are running. 1 = Enable, 0 = Disable
# You can still quit the process with !botquit in TS3 client chat or with botquit on the Query Interface.
telnet_run_forever = 1

# Use a MySQL database to save bot instances and configurations. 1 = Enable, 0 = Disable
# There should be a structure sql file in the documents directory.
# Import this into your MySQL database to create the tables (the included web interface do this already for you).
# But you must fill this tables by yourself, the bot just reads the information out there.
mysql_enable = 1
mysql_host = 127.0.0.1
mysql_port = 3307
mysql_user = ts3bot
mysql_password = xxxxxx
mysql_database = ts3bot

# Optional MySQL settings, more information on https://dev.mysql.com/doc/connector-j/5.1/en/connector-j-reference-configuration-properties.html#connector-j-reference-set-config
# Possible values: -1 = default, 0 = disable, 1 = enable
mysql_verifyServerCertificate = -1
mysql_useSSL = -1
mysql_requireSSL = -1
mysql_useCompression = -1

# Normal log entries older than X days will be deleted from MySQL jts3servermod_log table. 0 = disable auto delete!
mysql_log_delete = 180
# Connection log entries older than X days will be deleted from MySQL jts3servermod_log table. 0 = disable auto delete!
mysql_connection_log_delete = 180

[Stefan1200]

Sieht so aus, als wäre die JTS3ServerMod_InstanceManager.cfg falsch eingerichtet.

Kann nicht sein, da ich diese einfach kopiert und eingefügt, also nichts verändert habe.

Ist aber so, die von dir gepostete JTS3ServerMod_InstanceManager.cfg Datei liegt nicht am Ort C:\TS3\bot\config\JTS3ServerMod_InstanceManager.cfg
Und das sagt die Logdatei so deutlich, das es hier keinen Zweifel gibt.

[Sandviper]

Wo liegt die denn sonst?

Hier ein Shoot von meinem Server:

[Stefan1200]

Sorry, ich habe übersehen, das in der Logdatei steht, das du die freie Version vom JTS3ServerMod gestartet hast. Die kann natürlich kein MySQL. Bitte die Hosting Edition installieren.

[Sandviper]

Die hatte ich aber aus deinem neuen Download Link, jezt nochmal geladen und es ist die Hosting. Nun läuft auch wieder alles...Danke.

[Stefan1200]

Die hatte ich aber aus deinem neuen Download Link, jezt nochmal geladen und es ist die Hosting. Nun läuft auch wieder alles...Danke.

Der Download Link hat sich noch nie geändert. Du bist im Forum einfach nur falsch abgebogen.