Keycloak was unable to start

1

Hi Everyone,

I had an issue with keycloak where the server didn’t start properly and the below errors where generated in the log. Using the below information I couldn’t identify the root cause the issue. Do you have any idea what to check further?

Thank you.

2021-10-15 03:04:28,766 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool – 19) WFLYCTL0028: Attribute ‘security-realm’ in the resource at address ‘/subsystem=undertow/server=default-server/https-listener=https’ is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
2021-10-15 03:04:28,812 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool – 28) WFLYCTL0013: Operation (“add”) failed - address: ([(“deployment” => “keycloak-server.war”)]) - failure description: “WFLYCTL0155: ‘runtime-name’ may not be null”
2021-10-15 03:04:29,000 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) “WFLYCTL0193: Failed executing subsystem keycloak-server boot operations”
2021-10-15 03:04:29,016 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation (“parallel-subsystem-boot”) failed - address: ([]) - failure description: ““WFLYCTL0193: Failed executing subsystem keycloak-server boot operations””
2021-10-15 03:04:29,016 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
2021-10-15 03:04:29,050 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0050: Keycloak 9.0.0 (WildFly Core 10.0.3.Final) stopped in 24ms

2

Could it be that the port is already in use?

3

→ seems like something is not correctly configured

4

I’m running into the same issue and the failure is nondeterministic. If the issue were with the configuration I’d expect it to fail every time.

Keycloak starts in it’s own container so I don’t think it’s an issue with port being already taken. Do you have any other insights?