Healthcheck still working in 26.0? #36526

col-panic · 2025-01-16T12:46:03Z

col-panic
Jan 16, 2025

Could anyone confirm, if healthcheck is still working for him on 26.0?

I have KC_HEALTH_ENABLED=true but I only receive

bash-5.1$ exec 3<>/dev/tcp/127.0.0.1/9000;echo -e 'HEAD /health/ready HTTP/1.1\r\nhost: http://localhost\r\nConnection: close\r\n\r\n' >&3;cat <&3
HTTP/1.1 400 Bad Request
connection: close

accessing the declared management port - and everytime the code runs, log says

keycloak-1  | 2025-01-16T09:22:12.225286063Z 2025-01-16 09:22:12,224 ERROR [io.vertx.ext.web.RoutingContext] (vert.x-eventloop-thread-3) Unhandled exception in router

???

col-panic · 2025-01-16T12:49:20Z

col-panic
Jan 16, 2025
Author

Related #32363

0 replies

shawkins · 2025-01-16T14:33:46Z

shawkins
Jan 16, 2025
Collaborator

I have KC_HEALTH_ENABLED=true but I only receive

Do you have metrics-enabled=true as well? The current code

keycloak/quarkus/deployment/src/main/java/org/keycloak/quarkus/deployment/KeycloakProcessor.java

Line 614 in 992bcde

if (!isHealthEnabled() || !isMetricsEnabled()) {

when either is diabled our bean to customize readiness is removed - that may be causing the default endpoint from working. cc @mabartos

4 replies

col-panic Jan 16, 2025
Author

I have to check, according to the documentation in https://www.keycloak.org/server/management-interface "The management interface is turned on when something is exposed on it." so I guess the code contradicts the documentation in this case!

col-panic Jan 16, 2025
Author

I just enabled KC_METRICS_ENABLED=true too, and restarted Keycloak - still the Bad request ist occuring and keycloak-1 | 2025-01-16 15:46:56,006 ERROR [io.vertx.ext.web.RoutingContext] (vert.x-eventloop-thread-0) Unhandled exception in router is reported

shawkins Jan 16, 2025
Collaborator

Ok, double checked locally as well and everything works as expected when just health-enabled=true is supplied - so everything is good with the docs.

The problem is with your bash call. Try using curl or a browser and you can confirm that the endpoint is working.

col-panic Jan 16, 2025
Author

you are absolutely right, thanks for confirming. I used https://github.com/moparisthebest/static-curl/releases to run it from within the container

sh-5.1$ ./curl-amd64 -v --head -fsS http://localhost:9000/health/ready
* Host localhost:9000 was resolved.
* IPv6: ::1
* IPv4: 127.0.0.1
*   Trying [::1]:9000...
* Connected to localhost (::1) port 9000
* using HTTP/1.x
> HEAD /health/ready HTTP/1.1
> Host: localhost:9000
> User-Agent: curl/8.11.0
> Accept: */*
> 
* Request completely sent off
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< content-type: application/json; charset=UTF-8
content-type: application/json; charset=UTF-8
< cache-control: no-store
cache-control: no-store
< 

* Connection #0 to host localhost left intact

which led to adaptation to

sh-5.1$ exec 3<>/dev/tcp/127.0.0.1/9000;echo -e 'HEAD /health/ready HTTP/1.1\r\nHost: localhost:9000\r\nConnection: close\r\n\r\n' >&3;cat <&3
HTTP/1.1 200 OK
content-type: application/json; charset=UTF-8
cache-control: no-store
connection: close

which now works!

Navigation Menu

Repository navigation

Healthcheck still working in 26.0? #36526

Uh oh!

{{title}}

Uh oh!

Replies: 2 comments 4 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Healthcheck still working in 26.0? #36526

Uh oh!

col-panic Jan 16, 2025

Replies: 2 comments · 4 replies

Uh oh!

col-panic Jan 16, 2025 Author

Uh oh!

shawkins Jan 16, 2025 Collaborator

Uh oh!

col-panic Jan 16, 2025 Author

Uh oh!

col-panic Jan 16, 2025 Author

Uh oh!

shawkins Jan 16, 2025 Collaborator

Uh oh!

col-panic Jan 16, 2025 Author

col-panic
Jan 16, 2025

Replies: 2 comments 4 replies

col-panic
Jan 16, 2025
Author

shawkins
Jan 16, 2025
Collaborator

col-panic Jan 16, 2025
Author

col-panic Jan 16, 2025
Author

shawkins Jan 16, 2025
Collaborator

col-panic Jan 16, 2025
Author