Advertisement
Guest User

Untitled

a guest
May 27th, 2017
517
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 8.58 KB | None | 0 0
  1. 28.05 00:34:02 [Server] INFO [LiteBans] Enabling LiteBans v2.2.3
  2. 28.05 00:34:02 [Server] INFO [LiteBans] Loading SQL driver: mysql (com.mysql.jdbc.Driver)
  3. 28.05 00:34:02 [Server] INFO [LiteBans] Connecting to database...
  4. 28.05 00:34:02 [Server] WARN Sun May 28 00:34:02 CEST 2017 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
  5. 28.05 00:34:03 [Server] WARN Sun May 28 00:34:03 CEST 2017 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
  6. 28.05 00:34:04 [Server] WARN Sun May 28 00:34:04 CEST 2017 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
  7. 28.05 00:34:04 [Server] WARN Sun May 28 00:34:04 CEST 2017 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
  8. 28.05 00:34:05 [Server] WARN Sun May 28 00:34:05 CEST 2017 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
  9. 28.05 00:34:06 [Server] WARN Sun May 28 00:34:06 CEST 2017 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
  10. 28.05 00:34:07 [Server] WARN Sun May 28 00:34:07 CEST 2017 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
  11. 28.05 00:34:09 [Server] WARN Sun May 28 00:34:09 CEST 2017 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
  12. 28.05 00:34:11 [Server] WARN Sun May 28 00:34:11 CEST 2017 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
  13. 28.05 00:34:14 [Server] WARN Sun May 28 00:34:14 CEST 2017 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
  14. 28.05 00:34:17 [Server] WARN Sun May 28 00:34:17 CEST 2017 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
  15. 28.05 00:34:22 [Server] WARN Sun May 28 00:34:22 CEST 2017 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
  16. 28.05 00:34:28 [Server] WARN Sun May 28 00:34:28 CEST 2017 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
  17. 28.05 00:34:36 [Server] WARN Sun May 28 00:34:36 CEST 2017 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
  18. 28.05 00:34:37 [Server] ERROR [LiteBans] Failed to connect to [jdbc:mysql://149.56.147.175:3306/mc1357] using mysql driver.
  19. 28.05 00:34:37 [Server] ERROR [LiteBans] Error: Exception during pool initialization: litebans-pool - Connection is not available, request timed out after 30000ms.
  20. 28.05 00:34:37 [Server] ERROR [LiteBans] Cause: Access denied for user 'mc1357@149.56.147.175'@'ip175.ip-149-56-147.net' (using password: YES)
  21. 28.05 00:34:37 [Server] ERROR [LiteBans] [!] Access to the database "mc1357" was denied.
  22. 28.05 00:34:37 [Server] ERROR [LiteBans] [!] Ensure that the database "mc1357" has been created and that you have permissions to access this database.
  23. 28.05 00:34:37 [Server] ERROR [LiteBans] Please configure: plugins/LiteBans/config.yml
  24. 28.05 00:34:37 [Server] ERROR [LiteBans] Connection failed.
  25. 28.05 00:34:37 [Server] INFO [LiteBans] v2.2.3 enabled. Startup took 35247 ms.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement