On 9/5/2023 3:24 AM, Viktor Nikolov wrote:
Big thanks Lorenzo! It was the issue you mentioned.
I don't know how to tell Guacamole to use jdbc:mariadb://. I guess
jdbc:mysql is simply hard-coded, because it was working till MariaDB
Connector/J 3.0.
I installed Connector/J 2.7.10 (the newest one before 3.0).
Then I got error "Trying to connect with ssl, but ssl not enabled in the
server", which I resolved by adding "mysql-ssl-mode: disabled" to the
guacamole.properties.
So to summarize I faced 3 issues when upgrading from 1.4.0 to 1.5.3 on
native installation:
1. Guacamole 1.5.3 installation guide provides URL to the MariaDB
Connector/J 3.2, however Guacamole doesn't work with Connector/J 3.0 and
later.
2. Guacamole uses connection string jdbc:mysql:// even when it knows
from guacamole.properties that parameter mysql-driver is set to mariadb.
Starting with MariaDB Connector/J 3.0 the connection string jdbc:mariadb
must be used.
3. Compared to previous version of Guacamole and MariaDB Connector/J the
Guacamole 1.5.3 and Connector/J 2.7.10 by default connect to DB via SSL
if not told otherwise in guacamole.properties.
I believe No. 1 is a bug in documentation and No. 2 is a bug in SW.
I there a way for me to report the bugs?
In this case, the issue is in the underlying JDBC library that we use to
load the driver (MyBatis Guice). I've opened an issue covering what you
encountered:
https://github.com/mybatis/guice/issues/589
If there is a workaround, then we could implement that. The place to
report things on the Guacamole side is our JIRA:
https://issues.apache.org/jira/browse/GUACAMOLE/
If you don't have an account in our JIRA, you'll need to request an
account (you do this by clicking the link in the banner at the top of
JIRA). Be sure you provide a descriptive reason in the request
describing the need for the account so we can tell that the account
creation request is legitimate.
- Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
