[
https://issues.apache.org/jira/browse/GUACAMOLE-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17692287#comment-17692287
]
Jonathan Kwan commented on GUACAMOLE-1738:
------------------------------------------
Hi Mike,
Thanks for the quick response, unfortunately no, there are zero errors, and the
output is the same as it was when I was running it with 1.4.0. The Log output
is below:
[0m [Entrypoint] MySQL Docker Image 8.0.32-1.2.11-server
[0m [Entrypoint] Starting MySQL 8.0.32-1.2.11-server
[0m 2023-02-22T03:53:13.639172Z 0 [Warning] [MY-011068] [Server] The syntax
'--skip-host-cache' is deprecated and will be removed in a future release.
Please use SET GLOBAL host_cache_size=0 instead.
[0m 2023-02-22T03:53:13.641369Z 0 [System] [MY-010116] [Server]
/usr/sbin/mysqld (mysqld 8.0.32) starting as process 1
[0m 2023-02-22T03:53:13.647503Z 1 [System] [MY-013576] [InnoDB] InnoDB
initialization has started.
[0m 2023-02-22T03:53:14.036401Z 1 [System] [MY-013577] [InnoDB] InnoDB
initialization has ended.
[0m 2023-02-22T03:53:14.333269Z 0 [Warning] [MY-010068] [Server] CA certificate
ca.pem is self signed.
[0m 2023-02-22T03:53:14.333298Z 0 [System] [MY-013602] [Server] Channel
mysql_main configured to support TLS. Encrypted connections are now supported
for this channel.
[0m 2023-02-22T03:53:14.366154Z 0 [System] [MY-011323] [Server] X Plugin ready
for connections. Bind-address: '::' port: 33060, socket:
/var/run/mysqld/mysqlx.sock
[0m 2023-02-22T03:53:14.366360Z 0 [System] [MY-010931] [Server]
/usr/sbin/mysqld: ready for connections. Version: '8.0.32' socket:
'/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server - GPL.
> Docker Guacamole 1.5.0 Mysql Connection Error
> ---------------------------------------------
>
> Key: GUACAMOLE-1738
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1738
> Project: Guacamole
> Issue Type: Bug
> Affects Versions: 1.5.0
> Reporter: Jonathan Kwan
> Priority: Major
>
> Ever since I upgraded my docker instance of Guacamole from 1.4.0 to 1.5.0,
> Guacamole is unable to connect to my mysql instance. Previously on 1.4.0 it
> was working flawlessly without issue.
>
> I've ensure the following are up to date at the moment:
> nginx - 1.22.1
> mysql - 8.0.32
> docker engine - 23.0.1 (i was previously on 20.x, and it was causing weird
> issues with the Java components in Docker to indicate "out of memory" which
> wasn't the case)
>
> Based on the error messages my hunch is it might be to do with
> guacamole-auth-jdbc-mysql-1.5.0.jar.
>
> Below is the error message from Guacamole:
>
> [0m 04:05:17.030 [localhost-startStop-1] INFO
> o.a.g.environment.LocalEnvironment - GUACAMOLE_HOME is
> "/home/guacamole/.guacamole".
> [0m 04:05:17.117 [localhost-startStop-1] INFO
> o.a.g.GuacamoleServletContextListener - Read configuration parameters from
> "/home/guacamole/.guacamole/guacamole.properties".
> [0m 04:05:17.118 [localhost-startStop-1] INFO
> o.a.g.rest.auth.HashTokenSessionMap - Sessions will expire after 60 minutes
> of inactivity.
> [0m 04:05:17.505 [localhost-startStop-1] INFO
> o.a.g.extension.ExtensionModule - Multiple extensions are installed and will
> be loaded in order of decreasing priority:
> [0m 04:05:17.506 [localhost-startStop-1] INFO
> o.a.g.extension.ExtensionModule - - [duo] "Duo TFA Authentication Backend"
> (/home/guacamole/.guacamole/extensions/guacamole-auth-duo-1.5.0.jar)
> [0m 04:05:17.506 [localhost-startStop-1] INFO
> o.a.g.extension.ExtensionModule - - [mysql] "MySQL Authentication"
> (/home/guacamole/.guacamole/extensions/guacamole-auth-jdbc-mysql-1.5.0.jar)
> [0m 04:05:17.506 [localhost-startStop-1] INFO
> o.a.g.extension.ExtensionModule - To change this order, set the
> "extension-priority" property or rename the extension files. The default
> priority of extensions is dictated by the sort order of their filenames.
> [0m 04:05:17.783 [localhost-startStop-1] INFO
> o.a.g.extension.ExtensionModule - Extension "Duo TFA Authentication Backend"
> (duo) loaded.
> [0m 04:05:17.797 [localhost-startStop-1] INFO
> o.a.g.a.mysql.conf.MySQLEnvironment - Installed JDBC driver for MySQL/MariaDB
> detected as "MySQL Connector/J".
> [0m 04:05:18.558 [localhost-startStop-1] INFO
> o.a.g.extension.ExtensionModule - Extension "MySQL Authentication" (mysql)
> loaded.
> [0m 04:05:18.644 [localhost-startStop-1] INFO
> o.a.g.t.w.WebSocketTunnelModule - Loading JSR-356 WebSocket support...
> [0m 22-Feb-2023 04:05:19.453 INFO [localhost-startStop-1]
> org.apache.catalina.startup.HostConfig.deployWAR Deployment of web
> application archive [/home/guacamole/tomcat/webapps/guacamole.war] has
> finished in [3,996] ms
> [0m 22-Feb-2023 04:05:19.454 INFO [main]
> org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler
> ["http-nio-8080"]
> [0m 22-Feb-2023 04:05:19.464 INFO [main]
> org.apache.catalina.startup.Catalina.start Server startup in 4047 ms
> [0m 04:05:44.963 [http-nio-8080-exec-4] WARN
> o.a.g.e.AuthenticationProviderFacade - The "mysql" authentication provider
> has encountered an internal error which will halt the authentication process.
> If this is unexpected or you are the developer of this authentication
> provider, you may wish to enable debug-level logging. If this is expected and
> you wish to ignore such failures in the future, please set
> "skip-if-unavailable: mysql" within your guacamole.properties.
> [0m 04:05:44.967 [http-nio-8080-exec-4] ERROR o.a.g.rest.RESTExceptionMapper
> - Unexpected internal error:
> [0m ### Error querying database. Cause:
> com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link
> failure
> [0m
> [0m The last packet successfully received from the server was 111
> milliseconds ago. The last packet sent successfully to the server was 105
> milliseconds ago.
> [0m ### The error may exist in
> org/apache/guacamole/auth/jdbc/user/UserMapper.xml
> [0m ### The error may involve
> org.apache.guacamole.auth.jdbc.user.UserMapper.selectOne
> [0m ### The error occurred while executing a query
> [0m ### Cause: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException:
> Communications link failure
> [0m
> [0m The last packet successfully received from the server was 111
> milliseconds ago. The last packet sent successfully to the server was 105
> milliseconds ago.
> [0m 04:05:54.434 [http-nio-8080-exec-1] WARN
> o.a.g.e.AuthenticationProviderFacade - The "mysql" authentication provider
> has encountered an internal error which will halt the authentication process.
> If this is unexpected or you are the developer of this authentication
> provider, you may wish to enable debug-level logging. If this is expected and
> you wish to ignore such failures in the future, please set
> "skip-if-unavailable: mysql" within your guacamole.properties.
> [0m 04:05:54.434 [http-nio-8080-exec-1] ERROR o.a.g.rest.RESTExceptionMapper
> - Unexpected internal error:
> [0m ### Error querying database. Cause:
> com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link
> failure
> [0m
> [0m The last packet successfully received from the server was 5 milliseconds
> ago. The last packet sent successfully to the server was 5 milliseconds ago.
> [0m ### The error may exist in
> org/apache/guacamole/auth/jdbc/user/UserMapper.xml
> [0m ### The error may involve
> org.apache.guacamole.auth.jdbc.user.UserMapper.selectOne
> [0m ### The error occurred while executing a query
> [0m ### Cause: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException:
> Communications link failure
> [0m
> [0m The last packet successfully received from the server was 5 milliseconds
> ago. The last packet sent successfully to the server was 5 milliseconds ago.
> [0m 04:10:34.913 [http-nio-8080-exec-1] WARN
> o.a.g.e.AuthenticationProviderFacade - The "mysql" authentication provider
> has encountered an internal error which will halt the authentication process.
> If this is unexpected or you are the developer of this authentication
> provider, you may wish to enable debug-level logging. If this is expected and
> you wish to ignore such failures in the future, please set
> "skip-if-unavailable: mysql" within your guacamole.properties.
>
> Any assistance on this issue would be greatly appreciated, thanks!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
