[ 
https://issues.apache.org/jira/browse/GUACAMOLE-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17731453#comment-17731453
 ] 

ClassicGOD edited comment on GUACAMOLE-1808 at 6/12/23 8:24 PM:
----------------------------------------------------------------

Having the same issue and rolling back to 1.5.0 does not help.

The issue is probably related/caused by the recent MariaDB update 11.1.1:
 * The 
[transaction_isolation|https://mariadb.com/kb/en/server-system-variables/#transaction_isolation]
 option is now a system variable, and the tx_isolation system variable is 
deprecated ([MDEV-21921|https://jira.mariadb.org/browse/MDEV-21921])

Update:

Tried rolling MariaDB back to 11.0.2 - issue persists

Rolled MariaDB back to 10.11.4 - Guacamole working again. 

Looks like the issue is with MariaDB 11 and official container was probably 
moved to 11 semi-recently. Other applications using this container have no 
issues with both MariaDB 10 and 11, the issue seems to be only with Guacamole 
Client. 

EDIT: A little bit off-topic but I feel that I need to write this:

To anyone reading this to find a solution +*DO NOT*+ downgrade your MariaDB 
server haphazardly, especially if you already ran mariadb-upgrade. [Downgrading 
between major versions is not 
supported|https://mariadb.com/kb/en/downgrading-between-major-versions-of-mariadb/]
 and can break your database. At the very least do a proper backup of your 
database before doing this. My DB has regular snapshots and backups so I was 
not worried when jumping between versions, I was investigating the issue not 
suggesting it as a solution. I'm not responsible if you loose your data. 


was (Author: JIRAUSER283305):
Having the same issue and rolling back to 1.5.0 does not help.

The issue is probably related/caused by the recent MariaDB update 11.1.1:
 * The 
[transaction_isolation|https://mariadb.com/kb/en/server-system-variables/#transaction_isolation]
 option is now a system variable, and the tx_isolation system variable is 
deprecated ([MDEV-21921|https://jira.mariadb.org/browse/MDEV-21921])

Update:

Tried rolling MariaDB back to 11.0.2 - issue persists

Rolled MariaDB back to 10.11.4 - Guacamole working again. 

Looks like the issue is with MariaDB 11 and official container was probably 
moved to 11 semi-recently. Other applications using this container have no 
issues with both MariaDB 10 and 11, the issue seems to be only with Guacamole 
Client. 

> Add support for MariaDB 11.x to Docker image
> --------------------------------------------
>
>                 Key: GUACAMOLE-1808
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1808
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: guacamole-docker
>            Reporter: Pete Anderson
>            Priority: Minor
>
> I have been running guacamole in docker without issue using mariadb for 
> years.  After Watchtower updated me to the latest version I can no longer 
> access guacamole:
>  
> {code:none}
> ...
> 00:22:42.601 [http-nio-8080-exec-6] 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.
> 00:22:42.607 [http-nio-8080-exec-6] ERROR o.a.g.rest.RESTExceptionMapper - 
> Unexpected internal error: 
> ### Error querying database. Cause: java.sql.SQLException: Unknown system 
> variable 'transaction_isolation'
> ### The error may exist in org/apache/guacamole/auth/jdbc/user/UserMapper.xml
> ### The error may involve 
> org.apache.guacamole.auth.jdbc.user.UserMapper.selectOne
> ### The error occurred while executing a query
> ### Cause: java.sql.SQLException: Unknown system variable 
> 'transaction_isolation'
> ...
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to