You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
### Error updating database. Cause: com.mysql.cj.jdbc.exceptions.MySQLTransactionRollbackException: Deadlock found when trying to get lock; try restarting transaction
### The error may exist in org/apache/guacamole/auth/jdbc/permission/UserPermissionMapper.xml
### The error may involve org.apache.guacamole.auth.jdbc.permission.UserPermissionMapper.insert-Inline
### The error occurred while setting parameters
### SQL: INSERT IGNORE INTO guacamole_user_permission ( entity_id, permission, affected_user_id ) SELECT DISTINCT permissions.entity_id, permissions.permission, affected_user.user_id FROM ( SELECT ? AS entity_id, ? AS permission, ? AS affected_name UNION ALL SELECT ? AS entity_id, ? AS permission, ? AS affected_name UNION ALL SELECT ? AS entity_id, ? AS permission, ? AS affected_name UNION ALL SELECT ? AS entity_id, ? AS permission, ? AS affected_name UNION ALL SELECT ? AS entity_id, ? AS permission, ? AS affected_name ) AS permissions JOIN guacamole_entity affected_entity ON affected_entity.name = permissions.affected_name AND affected_entity.type = 'USER' JOIN guacamole_user affected_user ON affected_user.entity_id = affected_entity.entity_id
### Cause: com.mysql.cj.jdbc.exceptions.MySQLTransactionRollbackException: Deadlock found when trying to get lock; try restarting transaction
And the problematic SQL query from above in a nicer format:
INSERT IGNORE INTO guacamole_user_permission (
entity_id,
permission,
affected_user_id
)
SELECT DISTINCTpermissions.entity_id,
permissions.permission,
affected_user.user_idFROM (
SELECT ? AS entity_id,
? AS permission,
? AS affected_name
UNION ALLSELECT ? AS entity_id,
? AS permission,
? AS affected_name
UNION ALLSELECT ? AS entity_id,
? AS permission,
? AS affected_name
UNION ALLSELECT ? AS entity_id,
? AS permission,
? AS affected_name
UNION ALLSELECT ? AS entity_id,
? AS permission,
? AS affected_name
) AS permissions
JOIN guacamole_entity affected_entity ONaffected_entity.name=permissions.affected_nameANDaffected_entity.type='USER'JOIN guacamole_user affected_user ONaffected_user.entity_id=affected_entity.entity_id
Expected Behavior
All three users are created successfully.
Actual Behavior
Only one user gets created while for the other two users, I get the error messages from above.
Important Factoids
Guacamole and MySQL DB are running in an AWS EC2 instance. I connect to Guacamole with the AWS session manager "AWS-StartPortForwardingSession" document.
I don't know where to go from here. This probably is a problem with the guacamole client, right?
My first idea for a workaround would be to put a sleep instruction before client.CreateUser(&user) in resource_user.go with a random amount of milliseconds.
Thank you very much in advance! :-)
The text was updated successfully, but these errors were encountered:
@knorr3, I tested this with guacamole 1.4 with 50 users and it worked every time. I then tested this with 1.5 and ran into issues. My suggestion would be to test on 1.4 while i try to figure out what breaking change happened with 1.5. Thanks
Hi,
I get the following errors when trying to create multiple users.
Terraform Version
Terraform v1.3.9
on darwin_amd64
Affected Resource(s)
Terraform Configuration Files
I want to create three different users. All of them are configured like this:
Debug Output
Terraform Log:
Tomcat/Guacamole-Client Log:
And the problematic SQL query from above in a nicer format:
Expected Behavior
All three users are created successfully.
Actual Behavior
Only one user gets created while for the other two users, I get the error messages from above.
Important Factoids
Guacamole and MySQL DB are running in an AWS EC2 instance. I connect to Guacamole with the AWS session manager "AWS-StartPortForwardingSession" document.
I don't know where to go from here. This probably is a problem with the guacamole client, right?
My first idea for a workaround would be to put a sleep instruction before
client.CreateUser(&user)
in resource_user.go with a random amount of milliseconds.Thank you very much in advance! :-)
The text was updated successfully, but these errors were encountered: