Hi Bibrak,
I think the KEYCLOAK_USER and KEYCLOAK_PASSWORD env variables are causing Keycloak to try to add this user on start up. Try commenting out these lines [1] in docker-compose.yml. [1] https://github.com/apache/airavata/blob/develop/modules/ide-integration/src/main/resources/docker-compose.yml#L6-L7 From: Bibrak Qamar <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Tuesday, May 21, 2019 at 7:01 PM To: "[email protected]" <[email protected]> Subject: docker-compose up errors Hi all, docker-compose up gives me these two errors in its long list of output: keycloak_1 | 22:51:28,774 WARN [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (ServerService Thread Pool -- 49) SQL Error: 23505, SQLState: 23505 keycloak_1 | 22:51:28,774 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (ServerService Thread Pool -- 49) Unique index or primary key violation: "UK_RU8TT6T700S9V50BU18WS5HA6_INDEX_F ON PUBLIC.USER_ENTITY(REALM_ID, USERNAME) VALUES ( /* key:22 */ null, null, null, null, null, null, null, null, 'master', 'admin', null, null)"; SQL statement: keycloak_1 | insert into USER_ENTITY (CREATED_TIMESTAMP, EMAIL, EMAIL_CONSTRAINT, EMAIL_VERIFIED, ENABLED, FEDERATION_LINK, FIRST_NAME, LAST_NAME, REALM_ID, SERVICE_ACCOUNT_CLIENT_LINK, USERNAME, ID) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) [23505-173] keycloak_1 | 22:51:28,788 INFO [org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl] (ServerService Thread Pool -- 49) HHH000010: On release of batch it still contained JDBC statements keycloak_1 | 22:51:28,793 ERROR [org.keycloak.services] (ServerService Thread Pool -- 49) KC-SERVICES0010: Failed to add user 'admin' to realm 'master': user with username exists Is it normal or they need to be fixed before proceeding? Bibrak Qamar
smime.p7s
Description: S/MIME cryptographic signature
