Keycloak Instances Stopped Working After Subscription Ended and Renewal – "Service Unavailable" Error and Healthcheck Failure

levitation-infotechHOBBY

6 months ago

Yesterday, the subscription for my railway application ended, and as soon as it did, all of my Keycloak instances stopped working. Even after restarting the instances, they continue to fail. Before the subscription expired, everything was working smoothly. However, after making the payment to renew the subscription, the application started experiencing issues.
Here are the error logs from the build and deployment:

Build logs

Attempt #1 failed with service unavailable. Continuing to retry for 4m49s
Oct 24 11:19:43
Attempt #2 failed with service unavailable. Continuing to retry for 4m38s
...
Attempt #12 failed with service unavailable. Continuing to retry for 17s
Oct 24 11:24:05

Oct 24 11:24:05
1/1 replicas never became healthy!
Oct 24 11:24:05
Healthcheck failed!

Deploy log :

2024-10-24 05:52:16,635 INFO  [org.keycloak.broker.provider.AbstractIdentityProviderMapper] (main) Registering class org.keycloak.broker.provider.mappersync.ConfigSyncEventListener
Oct 24 11:22:20
2024-10-24 05:52:20,815 WARN  [io.agroal.pool] (agroal-11) Datasource '': The connection attempt failed.
Oct 24 11:22:21
2024-10-24 05:52:21,720 INFO  [org.infinispan.CLUSTER] (main) ISPN000080: Disconnecting JGroups channel `ISPN`
Oct 24 11:22:21
2024-10-24 05:52:21,728 INFO  [com.arjuna.ats.jbossatx] (main) ARJUNA032014: Stopping transaction recovery manager
Oct 24 11:22:21
2024-10-24 05:52:21,752 ERROR [org.keycloak.quarkus.runtime.cli.ExecutionExceptionHandler] (main) ERROR: Failed to start server in (production) mode
Oct 24 11:22:21
2024-10-24 05:52:21,753 ERROR [org.keycloak.quarkus.runtime.cli.ExecutionExceptionHandler] (main) ERROR: Failed to obtain JDBC connection
Oct 24 11:22:21
2024-10-24 05:52:21,753 ERROR [org.keycloak.quarkus.runtime.cli.ExecutionExceptionHandler] (main) ERROR: Acquisition timeout while waiting for new connection

Problem Summary:
Keycloak instances stopped working immediately after the subscription ended and didn’t resume after renewal.
Repeated connection attempts to the database (JDBC) failed, resulting in "service unavailable" and healthcheck failures.
All replicas failed to become healthy, and attempts to restart the server did not resolve the issue.

View Deploy details

> ⓘ Deployment information is only viewable by project members and Railway employees.

Solved

1 Replies

brodyEMPLOYEE

6 months ago

Looks like you have got keycloak up and running again.

Status changed to Solved brody • 6 months ago

Keycloak Instances Stopped Working After Subscription Ended and Renewal – "Service Unavailable" Error and Healthcheck Failure - Railway Help Station