JTS3ServerMod Hosting Edition - Connection Problem

Started by Alligatoras, April 27, 2016, 04:27:10 PM

Previous topic - Next topic

Alligatoras

Hello everyone,

I have added the whole "JTS3ServerMod_HostingEdition" folder on my vps in this location: "/home/teamspeak/JTS3ServerMod_HostingEdition". I took the "webinterface folder out from there and put it in this location: "/var/www/html/webinterface". i set everything up but when i try to start the bot i get this problem: . Maybe i have done something wrong. If anyone is able to help me i would appreciate it.

Thank you in response! :)

Stefan1200

Please attach the JTS3ServerMod_InstanceManager.log file.

Alligatoras

# JTS3ServerMod Instance Manager config file
#
# Each bot instance need:
# X.instance_enable
# X.instance_name
# X.instance_config_path
#
# Optional:
# X.instance_logfile_path
# X.instance_csvloginlog_path
# X.instance_debug = 1
#
# For X use a number starting from 1. Make sure that you have not more than 10 missing numbers between the instances.
# At least one enabled instance is needed or the bot process will stop after starting.
#
# 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 = (I have here my teamspeak uid)
# 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 = (i have here my own key from the website)
# 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 = (I have here my desired password)
# 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 = 185.25.22.9
# 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 =
# 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 = 3306
mysql_user = (desired name)
mysql_password = (desired password)
mysql_database = ts3bot

# Optional MySQL settings, more information on https://dev.mysql.com/doc/connector-j/en/connector-j-reference-configuration-properties.html
# 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 = 0
# Connection log entries older than X days will be deleted from MySQL jts3servermod_log table. 0 = disable auto delete!
mysql_connection_log_delete = 0

Stefan1200

Not the JTS3ServerMod_InstanceManager.cfg file, I mean the JTS3ServerMod_InstanceManager.log file.

Alligatoras

2016-04-27 15:13:50 START_MANAGER JTS3ServerMod 6.1.2 Hosting Edition (11.04.2016) Instance Manager started...
2016-04-27 15:13:50 CONFIG Loading InstanceManager config file from: /home/teamspeak/JTS3ServerMod_HostingEdition/config/JTS3ServerMod_InstanceManager.cfg
2016-04-27 15:13:50 CONFIG Bot chat command !exec is disabled!
2016-04-27 15:13:50 CONFIG Multi IP Mode disabled!
2016-04-27 15:13:51 LOGGER_SQL_ERROR Critical: Cannot connect to MySQL server for logging!
2016-04-27 15:13:51 JTS3ServerMod 6.1.2 Hosting Edition (11.04.2016): EXCEPTION
com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:404)
at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:981)
at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:339)
at com.mysql.jdbc.ConnectionImpl.coreConnect(ConnectionImpl.java:2253)
at com.mysql.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:2286)
at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2085)
at com.mysql.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:795)
at com.mysql.jdbc.JDBC4Connection.<init>(JDBC4Connection.java:44)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:404)
at com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:400)
at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:327)
at java.sql.DriverManager.getConnection(DriverManager.java:571)
at java.sql.DriverManager.getConnection(DriverManager.java:215)
at de.stefan1200.util.MySQLConnect.connect(Unknown Source)
at de.stefan1200.jts3servermod.u.a(Unknown Source)
at de.stefan1200.jts3servermod.u.<init>(Unknown Source)
at de.stefan1200.jts3servermod.f.c(Unknown Source)
at de.stefan1200.jts3servermod.f.<init>(Unknown Source)
at de.stefan1200.jts3servermod.JTS3ServerMod.main(Unknown Source)
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:579)
at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:211)
at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:298)
... 20 more
2016-04-27 15:13:51 CONFIG MySQL mode enabled!
2016-04-27 15:13:51 MYSQL_ERROR Error while connecting to database: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
2016-04-27 15:13:51 JTS3ServerMod 6.1.2 Hosting Edition (11.04.2016): EXCEPTION
com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:404)
at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:981)
at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:339)
at com.mysql.jdbc.ConnectionImpl.coreConnect(ConnectionImpl.java:2253)
at com.mysql.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:2286)
at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2085)
at com.mysql.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:795)
at com.mysql.jdbc.JDBC4Connection.<init>(JDBC4Connection.java:44)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:404)
at com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:400)
at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:327)
at java.sql.DriverManager.getConnection(DriverManager.java:571)
at java.sql.DriverManager.getConnection(DriverManager.java:215)
at de.stefan1200.util.MySQLConnect.connect(Unknown Source)
at de.stefan1200.jts3servermod.f.e(Unknown Source)
at de.stefan1200.jts3servermod.f.c(Unknown Source)
at de.stefan1200.jts3servermod.f.<init>(Unknown Source)
at de.stefan1200.jts3servermod.JTS3ServerMod.main(Unknown Source)
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:579)
at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:211)
at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:298)
... 19 more
2016-04-27 15:13:51 QUIT_MANAGER InstanceManager config file at "/home/teamspeak/JTS3ServerMod_HostingEdition/config/JTS3ServerMod_InstanceManager.cfg" does not exists, is not valid or an error while connecting to the database occurred, quitting now...

Stefan1200

QuoteConnection refused

Make sure, that the MySQL server is reachable on 127.0.0.1:3306 and no firewall is blocking this.

Alligatoras

I regranted the permissions. Now i just restart the "jts3servermod_startscript.sh" ?

Stefan1200

Yes, start the JTS3ServerMod and check out the JTS3ServerMod_InstanceManager.log file again.

Alligatoras

I still get the same error!
I have the port open so no filewall blocks

Stefan1200

Are you sure that the MySQL server is bound to 127.0.0.1? Did you tried the normal IP address of the MySQL server? You can also try to test the connection with the MySQL client.

Alligatoras

In the sql file where it says: bind-address do i have to type both IP and localhost?
Cause i have only my ip there.

Stefan1200

Just try to set your ip address as MySQL host in the JTS3ServerMod_InstanceManager.cfg file.

Alligatoras

I set in the SQL the bind address to all: 0.0.0.0
Works fine. Thank you for all you help Stefan. :)