Stopping Red Hat build of Keycloak service shows status failed

Solution Verified - Updated -

Issue

  • We have configured Red Hat build of Keycloak as a systemd service. The service start and stop is working fine, but when the service is stopped the status is always failed instead of inactive.
# systemctl status xxxxxx.service 
× xxxxx.service - xxxxx.service
     Loaded: loaded (/etc/systemd/system/xxxxx.service; enabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: failed (Result: exit-code) since xxxxxxx; 4s ago
   Duration: 10.016s
    Process: xxxxxx ExecStart=/path/to/bin/kc.sh start (code=exited, status=143)
    Process: xxxxxx ExecStop=/bin/kill -SIGTERM $PID (code=exited, status=0/SUCCESS)

Environment

  • Red Hat build of Keycloak
    • 22.x
    • 24.x
    • 26.0.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content