On Fri, Jul 3, 2020 at 11:13 PM Nick Couchman <[email protected]> wrote:
> >>>>>> I don't see anything on the logs (/var/log/tomcat9). Also the >> database seems to be correct: >> > > Which logs are you looking at? Do you see other messages related to > Guacamole in those files? You may need to bump up the log level of the web > application and see if that turns up anything useful: > > > http://guacamole.apache.org/doc/gug/configuring-guacamole.html#webapp-logging > > > >> >> MariaDB [guacamole_db]> select * from guacamole_sharing_profile; >> +--------------------+----------------------+-----------------------+ >> | sharing_profile_id | sharing_profile_name | primary_connection_id | >> +--------------------+----------------------+-----------------------+ >> | 1 | Watch | 1 | >> +--------------------+----------------------+-----------------------+ >> >> MariaDB [guacamole_db]> select * from guacamole_sharing_profile_parameter; >> +--------------------+----------------+-----------------+ >> | sharing_profile_id | parameter_name | parameter_value | >> +--------------------+----------------+-----------------+ >> | 1 | read-only | true | >> +--------------------+----------------+-----------------+ >> >> MariaDB [guacamole_db]> select * from >> guacamole_sharing_profile_permission; >> +-----------+--------------------+------------+ >> | entity_id | sharing_profile_id | permission | >> +-----------+--------------------+------------+ >> | 1 | 1 | READ | >> | 1 | 1 | UPDATE | >> | 1 | 1 | DELETE | >> | 1 | 1 | ADMINISTER | >> +-----------+--------------------+------------+ >> > > What about permissions of the JDBC user to the MariaDB tables? > > I haven’t tried with MariaDB - I’m running Postgres - but I’m able to > correctly add a sharing profile to my instance. The other reason I ask > about the DB is because when I logged on to the Guacamole instance you > provided earlier there were two different connections with the same name, > which should not be allowed. Guacamole enforces unique connection names > within the instance. This makes me think that something is a little messed > up in the DB itself, or that the database has been modified somehow outside > the user interface in a way that it’s causing unexpected behavior. > I tried something else: - installed `mysql-connector-java` - commented out the line `mysql-driver: mariadb` on `/etc/guacamole/guacamole.properties` - restarted Tomcat: `systemctl restart tomcat9` and voila, everything works correctly. Then uncomment `mysql-driver: mariadb` and restart tomcat, and the problem is still there. So, definitely this looks like a bug related to the MariaDB driver. But it has an easy workaround: use `mysql-connector-java` instead. > > -Nick >
