Keycloak 25 not able to start from command line

[uday kumar]

HI Team,

I was using key cloak 24.0.2 its working fine 

Later i download the key cloak 25.0.1  ,but i am not able to start the sever

i have updated JDK 21 also

error

2024-07-08 20:42:54,752 WARN  [org.keycloak.quarkus.runtime.cli.Picocli] (main) The following used options or option values are DEPRECATED and will be removed or their behaviour changed in a future release:
- proxy: Use proxy-headers.
Consult the Release Notes for details.
2024-07-08 20:42:59,449 INFO  [org.infinispan.CONTAINER] (Thread-5) ISPN000556: Starting user marshaller 'org.infinispan.jboss.marshalling.core.JBossUserMarshaller'
2024-07-08 20:42:59,939 INFO  [org.infinispan.CLUSTER] (Thread-5) ISPN000088: Unable to use any JGroups configuration mechanisms provided in properties {}. Using default JGroups configuration!
2024-07-08 20:43:00,276 INFO  [org.infinispan.CLUSTER] (Thread-5) ISPN000078: Starting JGroups channel `ISPN`
2024-07-08 20:43:00,281 INFO  [org.jgroups.JChannel] (Thread-5) local_addr: 875282e2-10b5-4adf-9645-065f49508a88, name: WIN-H658ABQSVG2-35313
2024-07-08 20:43:00,358 INFO  [org.jgroups.protocols.FD_SOCK2] (Thread-5) server listening on *.37163
2024-07-08 20:43:00,811 WARN  [io.quarkus.vertx.http.runtime.VertxHttpRecorder] (main) The X-Forwarded-* and Forwarded headers will be considered when determining the proxy address. This configuration can cause a security issue as clients can forge requests and send a forwarded header that is not overwritten by the proxy. Please consider use one of these headers just to forward the proxy address in requests.
2024-07-08 20:43:00,841 INFO  [org.keycloak.broker.provider.AbstractIdentityProviderMapper] (main) Registering class org.keycloak.broker.provider.mappersync.ConfigSyncEventListener
2024-07-08 20:43:02,368 INFO  [org.jgroups.protocols.pbcast.GMS] (Thread-5) WIN-H658ABQSVG2-35313: no members discovered after 2006 ms: creating cluster as coordinator
2024-07-08 20:43:02,375 INFO  [org.infinispan.CLUSTER] (Thread-5) ISPN000094: Received new cluster view for channel ISPN: [WIN-H658ABQSVG2-35313|0] (1) [WIN-H658ABQSVG2-35313]
2024-07-08 20:43:02,406 INFO  [org.infinispan.CLUSTER] (Thread-5) ISPN000079: Channel `ISPN` local address is `WIN-H658ABQSVG2-35313`, physical addresses are `[192.168.164.223:52699]`
2024-07-08 20:43:02,812 INFO  [org.keycloak.connections.infinispan.DefaultInfinispanConnectionProviderFactory] (main) Node name: WIN-H658ABQSVG2-35313, Site name: null
2024-07-08 20:43:04,019 INFO  [org.infinispan.CLUSTER] (main) ISPN000080: Disconnecting JGroups channel `ISPN`
2024-07-08 20:43:04,031 INFO  [com.arjuna.ats.jbossatx] (main) ARJUNA032014: Stopping transaction recovery manager
2024-07-08 20:43:04,067 ERROR [org.keycloak.quarkus.runtime.cli.ExecutionExceptionHandler] (main) ERROR: Failed to start server in (production) mode
2024-07-08 20:43:04,071 ERROR [org.keycloak.quarkus.runtime.cli.ExecutionExceptionHandler] (main) ERROR: Unable to start HTTP server
2024-07-08 20:43:04,072 ERROR [org.keycloak.quarkus.runtime.cli.ExecutionExceptionHandler] (main) ERROR: java.lang.IllegalStateException: Unable to start the management interface
2024-07-08 20:43:04,073 ERROR [org.keycloak.quarkus.runtime.cli.ExecutionExceptionHandler] (main) ERROR: Unable to start the management interface
2024-07-08 20:43:04,074 ERROR [org.keycloak.quarkus.runtime.cli.ExecutionExceptionHandler] (main) ERROR: Address already in use: bind
2024-07-08 20:43:04,077 ERROR [org.keycloak.quarkus.runtime.cli.ExecutionExceptionHandler] (main) For more details run the same command passing the '--verbose' option. Also you can use '--help' to see the details about the usage of the particular command.

[Alexander Schwartz]

Hi,

In Keycloak version 25, the metrics and health endpoints were moved to a management port which is using by default Port 9000. It seems that this port is blocked on your machine. 

You can choose to disable this feature, free the port, or move Keycloak's management port to a different port. 

As we recommend to not expose metrics or health probes on Keycloak's regular endpoint, I'd suggest to not disable it. 

See the release notes on more details: https://www.keycloak.org/docs/latest/release_notes/index.html#management-port-for-metrics-and-health-endpoints 

Best,
Alexander

--
You received this message because you are subscribed to the Google Groups "Keycloak User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to keycloak-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/keycloak-user/1010bd2a-85a8-4c00-8a4a-cbe07992cf2dn%40googlegroups.com.

--

Alexander Schwartz, RHCE

He/Him

Principal Software Engineer, Keycloak Maintainer

Red Hat - Germany remote

asch...@redhat.com   

Red Hat GmbH, Registered seat: Werner von Siemens Ring 12, D-85630 Grasbrunn, Germany 
Commercial register: Amtsgericht Muenchen/Munich, HRB 153243,
Managing Directors: Ryan Barnhart, Charles Cachera, Michael O'Neill, Amy Ross