Pod Fails to Start After Applying New YAML Version quay.io/keycloak/keycloak:26.2.5 with Keycloak Container Error #40656

vitorafgomes · 2025-06-22T22:35:45Z

vitorafgomes
Jun 22, 2025

After applying the YAML file provided on the website for the new version, the pod encounters the following error:

Back-off restarting failed container keycloak in pod.

Inside the pod, the following message is logged:

Appending additional Java properties to JAVA_OPTS. Updating the configuration and installing your custom providers, if any. Please wait.

Answered by shawkins

Jun 23, 2025

You could be seeing keycloak/keycloak-quickstarts#698

The quickstart was recently expanded, but the default probes may cause the container to never become ready. Can you try updating the yaml to have probes as shown in the comments of that issue?

View full answer

shawkins · 2025-06-23T11:39:00Z

shawkins
Jun 23, 2025
Collaborator

This isn't showing enough information to determine what is happening. What yaml are you referring to? Is there a stacktrace or other failure shown in the log?

2 replies

vitorafgomes Jun 23, 2025
Author

Cluster ARM 64

Executed steps.
Script execution containing keycloak and postgres

LOG Pod

Log Pod PostgreSQL
initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.
waiting for server to start....2025-06-23 12:10:24.449 UTC [48] LOG: starting PostgreSQL 17.5 (Debian 17.5-1.pgdg120+1) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-06-23 12:10:24.452 UTC [48] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-06-23 12:10:24.472 UTC [51] LOG: database system was shut down at 2025-06-23 12:10:23 UTC
2025-06-23 12:10:24.496 UTC [48] LOG: database system is ready to accept connections
done
server started
CREATE DATABASE

/usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*

waiting for server to shut down....2025-06-23 12:10:25.129 UTC [48] LOG: received fast shutdown request
2025-06-23 12:10:25.132 UTC [48] LOG: aborting any active transactions
2025-06-23 12:10:25.144 UTC [48] LOG: background worker "logical replication launcher" (PID 54) exited with exit code 1
2025-06-23 12:10:25.146 UTC [49] LOG: shutting down
2025-06-23 12:10:25.147 UTC [49] LOG: checkpoint starting: shutdown immediate
2025-06-23 12:10:25.291 UTC [49] LOG: checkpoint complete: wrote 921 buffers (5.6%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.086 s, sync=0.051 s, total=0.146 s; sync files=301, longest=0.002 s, average=0.001 s; distance=4238 kB, estimate=4238 kB; lsn=0/1908958, redo lsn=0/1908958
2025-06-23 12:10:25.321 UTC [48] LOG: database system is shut down
done
server stopped

PostgreSQL init process complete; ready for start up.

2025-06-23 12:10:25.444 UTC [1] LOG: starting PostgreSQL 17.5 (Debian 17.5-1.pgdg120+1) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-06-23 12:10:25.445 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2025-06-23 12:10:25.445 UTC [1] LOG: listening on IPv6 address "::", port 5432
2025-06-23 12:10:25.449 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-06-23 12:10:25.468 UTC [64] LOG: database system was shut down at 2025-06-23 12:10:25 UTC
2025-06-23 12:10:25.498 UTC [1] LOG: database system is ready to accept connections
2025-06-23 12:10:31.139 UTC [68] ERROR: relation "migration_model" does not exist at character 25
2025-06-23 12:10:31.139 UTC [68] STATEMENT: SELECT ID, VERSION FROM MIGRATION_MODEL ORDER BY UPDATE_TIME DESC
2025-06-23 12:10:32.550 UTC [68] ERROR: relation "public.databasechangelog" does not exist at character 22
2025-06-23 12:10:32.550 UTC [68] STATEMENT: SELECT COUNT() FROM public.databasechangelog
2025-06-23 12:10:33.353 UTC [69] ERROR: relation "public.databasechangeloglock" does not exist at character 22
2025-06-23 12:10:33.353 UTC [69] STATEMENT: SELECT COUNT() FROM public.databasechangeloglock
2025-06-23 12:10:33.491 UTC [68] ERROR: relation "public.databasechangelog" does not exist at character 22
2025-06-23 12:10:33.491 UTC [68] STATEMENT: SELECT COUNT(*) FROM public.databasechangelog
2025-06-23 12:10:47.405 UTC [69] LOG: unexpected EOF on client connection with an open transaction
2025-06-23 12:10:47.405 UTC [68] LOG: could not receive data from client: Connection reset by peer
2025-06-23 12:10:47.405 UTC [68] LOG: unexpected EOF on client connection with an open transaction
2025-06-23 12:12:03.435 UTC [73] ERROR: column "update_time" does not exist at character 50
2025-06-23 12:12:03.435 UTC [73] STATEMENT: SELECT ID, VERSION FROM MIGRATION_MODEL ORDER BY UPDATE_TIME DESC
2025-06-23 12:12:17.392 UTC [75] LOG: unexpected EOF on client connection with an open transaction
2025-06-23 12:12:17.392 UTC [73] LOG: could not receive data from client: Connection reset by peer
2025-06-23 12:12:17.392 UTC [73] LOG: unexpected EOF on client connection with an open transaction
2025-06-23 12:13:00.558 UTC [78] ERROR: column "update_time" does not exist at character 50
2025-06-23 12:13:00.558 UTC [78] STATEMENT: SELECT ID, VERSION FROM MIGRATION_MODEL ORDER BY UPDATE_TIME DESC
2025-06-23 12:13:17.409 UTC [79] LOG: unexpected EOF on client connection with an open transaction
2025-06-23 12:13:17.410 UTC [78] LOG: could not receive data from client: Connection reset by peer
2025-06-23 12:13:17.410 UTC [78] LOG: unexpected EOF on client connection with an open transaction
2025-06-23 12:14:17.402 UTC [83] LOG: unexpected EOF on client connection with an open transaction
2025-06-23 12:15:25.563 UTC [62] LOG: checkpoint starting: time
2025-06-23 12:16:19.994 UTC [62] LOG: checkpoint complete: wrote 542 buffers (3.3%); 1 WAL file(s) added, 0 removed, 0 recycled; write=54.049 s, sync=0.157 s, total=54.431 s; sync files=624, longest=0.002 s, average=0.001 s; distance=3992 kB, estimate=3992 kB; lsn=0/1CFB200, redo lsn=0/1CEEC38
2025-06-23 12:20:26.062 UTC [62] LOG: checkpoint starting: time
2025-06-23 12:20:29.001 UTC [62] LOG: checkpoint complete: wrote 30 buffers (0.2%); 0 WAL file(s) added, 0 removed, 0 recycled; write=2.922 s, sync=0.008 s, total=2.939 s; sync files=24, longest=0.002 s, average=0.001 s; distance=54 kB, estimate=3598 kB; lsn=0/1CFC598, redo lsn=0/1CFC508
2025-06-23 12:25:26.097 UTC [62] LOG: checkpoint starting: time
2025-06-23 12:25:26.215 UTC [62] LOG: checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; wri 8000 te=0.106 s, sync=0.003 s, total=0.118 s; sync files=2, longest=0.002 s, average=0.002 s; distance=0 kB, estimate=3239 kB; lsn=0/1CFC7A0, redo lsn=0/1CFC748
2025-06-23 12:30:26.293 UTC [62] LOG: checkpoint starting: time
2025-06-23 12:30:26.412 UTC [62] LOG: checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.107 s, sync=0.003 s, total=0.119 s; sync files=2, longest=0.002 s, average=0.002 s; distance=0 kB, estimate=2915 kB; lsn=0/1CFCA40, redo lsn=0/1CFC9E8
2025-06-23 12:35:26.491 UTC [62] LOG: checkpoint starting: time
2025-06-23 12:35:26.608 UTC [62] LOG: checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.107 s, sync=0.003 s, total=0.117 s; sync files=2, longest=0.002 s, average=0.002 s; distance=0 kB, estimate=2623 kB; lsn=0/1CFCC48, redo lsn=0/1CFCBF0
2025-06-23 12:40:26.661 UTC [62] LOG: checkpoint starting: time
2025-06-23 12:40:26.779 UTC [62] LOG: checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.106 s, sync=0.003 s, total=0.119 s; sync files=2, longest=0.002 s, average=0.002 s; distance=0 kB, estimate=2361 kB; lsn=0/1CFCE18, redo lsn=0/1CFCDC0
2025-06-23 12:45:26.862 UTC [62] LOG: checkpoint starting: time
2025-06-23 12:45:26.980 UTC [62] LOG: checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.107 s, sync=0.003 s, total=0.119 s; sync files=2, longest=0.002 s, average=0.002 s; distance=0 kB, estimate=2125 kB; lsn=0/1CFD0B8, redo lsn=0/1CFD060
2025-06-23 12:50:27.063 UTC [62] LOG: checkpoint starting: time
2025-06-23 12:50:27.181 UTC [62] LOG: checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.107 s, sync=0.003 s, total=0.119 s; sync files=2, longest=0.002 s, average=0.002 s; distance=0 kB, estimate=1912 kB; lsn=0/1CFD2C0, redo lsn=0/1CFD268
2025-06-23 13:00:27.357 UTC [62] LOG: checkpoint starting: time
2025-06-23 13:00:27.475 UTC [62] LOG: checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.107 s, sync=0.003 s, total=0.118 s; sync files=2, longest=0.002 s, average=0.002 s; distance=0 kB, estimate=1721 kB; lsn=0/1CFD560, redo lsn=0/1CFD508

shawkins Jun 23, 2025
Collaborator

You could be seeing keycloak/keycloak-quickstarts#698

The quickstart was recently expanded, but the default probes may cause the container to never become ready. Can you try updating the yaml to have probes as shown in the comments of that issue?

Answer selected by vitorafgomes

Navigation Menu

Repository navigation

Pod Fails to Start After Applying New YAML Version quay.io/keycloak/keycloak:26.2.5 with Keycloak Container Error #40656

Uh oh!

{{title}}

Uh oh!

Replies: 1 comment 2 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Pod Fails to Start After Applying New YAML Version quay.io/keycloak/keycloak:26.2.5 with Keycloak Container Error #40656

Uh oh!

vitorafgomes Jun 22, 2025

Replies: 1 comment · 2 replies

Uh oh!

Uh oh!

shawkins Jun 23, 2025 Collaborator

Uh oh!

vitorafgomes Jun 23, 2025 Author

Uh oh!

shawkins Jun 23, 2025 Collaborator

vitorafgomes
Jun 22, 2025

Replies: 1 comment 2 replies

shawkins
Jun 23, 2025
Collaborator

vitorafgomes Jun 23, 2025
Author

shawkins Jun 23, 2025
Collaborator