Bitwarden unresponsive and requires restarts, api terminated by SIGKILL

[Bramzor]

Self-host installation scripts issue

• I understand this repository only tracks self-host installation scripts and any other issues should be reported in bitwarden/server

Steps To Reproduce

I'm running the latest version.

image: ghcr.io/bitwarden/self-host

Logs:

bitwarden-bitwarden-1  | 2025-04-18 08:07:42,045 INFO spawned: 'identity' with pid 41
bitwarden-bitwarden-1  | 2025-04-18 08:07:42,049 INFO spawned: 'admin' with pid 42
bitwarden-bitwarden-1  | 2025-04-18 08:07:42,052 INFO spawned: 'api' with pid 43
bitwarden-bitwarden-1  | 2025-04-18 08:07:42,060 INFO spawned: 'icons' with pid 44
bitwarden-bitwarden-1  | 2025-04-18 08:07:42,069 INFO spawned: 'nginx' with pid 45
bitwarden-bitwarden-1  | 2025-04-18 08:07:42,090 INFO spawned: 'notifications' with pid 46
bitwarden-bitwarden-1  | 2025-04-18 08:07:57,140 INFO success: identity entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
bitwarden-bitwarden-1  | 2025-04-18 08:07:57,144 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
bitwarden-bitwarden-1  | 2025-04-18 08:07:57,144 INFO success: api entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
bitwarden-bitwarden-1  | 2025-04-18 08:07:57,145 INFO success: icons entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
bitwarden-bitwarden-1  | 2025-04-18 08:07:57,145 INFO success: nginx entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
bitwarden-bitwarden-1  | 2025-04-18 08:07:57,146 INFO success: notifications entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
bitwarden-bitwarden-1  | 2025-04-18 08:08:39,398 WARN exited: api (terminated by SIGKILL; not expected)
bitwarden-bitwarden-1  | 2025-04-18 08:08:40,444 INFO spawned: 'api' with pid 152
bitwarden-bitwarden-1  | 2025-04-18 08:08:56,011 INFO success: api entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
bitwarden-bitwarden-1  | 2025-04-18 08:10:04,954 WARN exited: api (terminated by SIGKILL; not expected)
bitwarden-bitwarden-1  | 2025-04-18 08:10:05,973 INFO spawned: 'api' with pid 211
bitwarden-bitwarden-1  | 2025-04-18 08:10:21,592 INFO success: api entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)

Expected Result

Running stable for a long time, like it did before.

Actual Result

A short amount of time after the startup, Bitwarden becomes unresponsive because api throws terminated by SIGKILL.

Screenshots or Videos

No response

Additional Context

No response

Build Version

latest: Pulling from bitwarden/self-host Digest: sha256:54752399d72a4559805cb1ee0152a64e5da8acfe4929c7419a0eac8ba9813ba2

Environment

Self-Hosted

Environment Details

• Ubuntu 22.04.1 LTS
• Docker Engine Version: 24.0.2

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[NovaSilentium]

Hi there,

I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks!

[trmartin4]

@Bramzor we have not been able to reproduce this issue internally. Can you confirm that you are still experiencing this on startup consistently? If so, are there any other errors that you see in the logs that you could provide?

Thank you for your help.