Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keycloakx 25.0.1 crashloop without any message #781

Closed
beezerk23 opened this issue Jul 11, 2024 · 2 comments
Closed

Keycloakx 25.0.1 crashloop without any message #781

beezerk23 opened this issue Jul 11, 2024 · 2 comments
Labels

Comments

@beezerk23
Copy link

Hey, im also running into a crashloop. For whatever reason, all my deployment is doing is this:

Appending additional Java properties to JAVA_OPTS
Updating the configuration and installing your custom providers, if any. Please wait.
2024-07-11 12:38:47,833 INFO  [io.qua.dep.QuarkusAugmentor] (main) Quarkus augmentation completed in 110325ms
2024-07-11 12:39:44,173 INFO  [org.infinispan.CONTAINER] (Thread-5) ISPN000556: Starting user marshaller 'org.infinispan.jboss.marshalling.core.JBossUserMarshaller'
2024-07-11 12:39:48,152 INFO  [org.infinispan.CLUSTER] (Thread-5) ISPN000078: Starting JGroups channel `ISPN` with stack `kubernetes`
2024-07-11 12:39:48,162 INFO  [org.jgroups.JChannel] (Thread-5) local_addr: 80abec56-ff79-4a91-b44d-2799b0a24108, name: keycloak-keycloakx-0-61709
2024-07-11 12:39:48,265 INFO  [org.jgroups.protocols.FD_SOCK2] (Thread-5) server listening on *.57800
2024-07-11 12:39:50,311 INFO  [org.jgroups.protocols.pbcast.GMS] (Thread-5) keycloak-keycloakx-0-61709: no members discovered after 2008 ms: creating cluster as coordinator
2024-07-11 12:39:50,690 INFO  [org.infinispan.CLUSTER] (Thread-5) ISPN000094: Received new cluster view for channel ISPN: [keycloak-keycloakx-0-61709|0] (1) [keycloak-keycloakx-0-61709]
2024-07-11 12:39:54,320 INFO  [org.infinispan.CLUSTER] (Thread-5) ISPN000079: Channel `ISPN` local address is `keycloak-keycloakx-0-61709`, physical addresses are `[10.8.2.106:7800]`
2024-07-11 12:39:57,583 INFO  [org.keycloak.broker.provider.AbstractIdentityProviderMapper] (main) Registering class org.keycloak.broker.provider.mappersync.ConfigSyncEventListener
2024-07-11 12:39:59,916 INFO  [org.keycloak.connections.infinispan.DefaultInfinispanConnectionProviderFactory] (main) Node name: keycloak-keycloakx-0-61709, Site name: null
2024-07-11 12:40:16,896 INFO  [io.quarkus] (main) Keycloak 25.0.1 on JVM (powered by Quarkus 3.8.5) started in 88.214s. Listening on: http://0.0.0.0:8080. Management interface listening on http://0.0.0.0:9000.
2024-07-11 12:40:16,906 INFO  [io.quarkus] (main) Profile dev activated.
2024-07-11 12:40:16,912 INFO  [io.quarkus] (main) Installed features: [agroal, cdi, hibernate-orm, jdbc-mysql, keycloak, logging-gelf, micrometer, narayana-jta, reactive-routes, resteasy-reactive, resteasy-reactive-jackson, smallrye-context-propagation, smallrye-health, vertx]
2024-07-11 12:40:16,989 WARN  [org.keycloak.quarkus.runtime.KeycloakMain] (main) Running the server in development mode. DO NOT use this configuration in production.
2024-07-11 12:41:45,889 INFO  [org.infinispan.CLUSTER] (Thread-12) ISPN000080: Disconnecting JGroups channel `ISPN`
2024-07-11 12:41:46,031 INFO  [com.arjuna.ats.jbossatx] (main) ARJUNA032014: Stopping transaction recovery manager
2024-07-11 12:41:46,172 INFO  [io.quarkus] (main) Keycloak stopped in 0.557s

As you can see after some time keycloak just stops. I use 2.4.3 of the helm chart and 25.0.1 as the keycloak version. In my kubernetes logs i get this:

Startup probe failed: HTTP probe failed with statuscode: 404
Startup probe failed: Get "http://10.8.2.106:8080/health": dial tcp 10.8.2.106:8080: connect: connection refused

This is my start command configured in the helm values:

command:
  - "/opt/keycloak/bin/kc.sh"
  - "start-dev"
  - "--verbose"
  - "--hostname=https://MY_DOMAIN"
  - "--http-port=8080"
  - "--hostname-strict=false"

Any help would be highly appreciated.

Originally posted by @beezerk23 in #778 (comment)

@exaV
Copy link

exaV commented Jul 18, 2024

This is most likely cause by the breaking change to health endpoints in 25.x https://www.keycloak.org/docs/latest/release_notes/index.html#management-port-for-metrics-and-health-endpoints

Copy link

This issue has been marked as stale because it has been open for 30 days with no activity. It will be automatically closed in 10 days if no further activity occurs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants