Closed precurse closed 6 years ago
I can confirm the same symptoms exist with version >=2.0.0 up to 2.0.8
This is underlying issue: https://github.com/flyway/flyway/issues/1556
Pushed commit https://github.com/OpenConext/OpenConext-attribute-aggregation/commit/510c42feaf14dfe2c977ed1f10f45f6be79d021d and made a https://build.openconext.org/repository/public/snapshots/org/openconext/attribute-aggregation-server/2.0.9-SNAPSHOT/ new snapshot release. @precurse can you confirm that this fixes this issue?
Thanks @oharsta that looks like it's resolved. I still had some of these errors on first run:
Migration V4___attribute_skip_consent.sql failed
------------------------------------------------
SQL State : HY000
Error Code : 1105
Message : (conn=258168) Percona-XtraDB-Cluster prohibits use of DML command on a table (aaserver.aggregations_attributes) without an explicit primary key with pxc_strict_mode = ENFORCING or MASTER
Location : db/migration/V4___attribute_skip_consent.sql (/opt/attribute-aggregation/file:/opt/attribute-aggregation/attribute-aggregation-server-2.0.9-20180623.054152-1.jar!/BOOT-INF/classes!/db/migration/V4___attribute_skip_consent.sql)
Line : 5
Statement : DELETE FROM aggregations_attributes
I set strict mode to PERMISSIVE until it was able to create the database structure. After that I set it back to ENFORCING and the AA service started up fine.
Thanks!
I recently tried adding Attribute Aggregation using the OpenConext-Deploy repo (version 247). I first set Percona to
pxc_strict_mode=PERMISSIVE
to get the database structure created. The AA server starts fine and creates the database structure. After this, I setpxc_strict_mode
back toENFORCING
and restart the AA server, but keep getting the same error below:Is there any trick to get working? This seems to be the only OpenConext daemon that refuses to start when XtraDB/InnoDB strict mode is enabled.
Thanks!