Bitwarden self hosted crashing/starting every 2 mins

Ask the Community Password Manager
,
1

Approximately every 2 minutes my unified bitwarden self hosted, crashes and restarts. I pulled the latest version to make sure it wasn’t that. I am running it with podman on RHEL 9. I don’t see anything much in the notifications log, just:-

2023-05-06 13:53:49.490 +00:00 [WRN] Stopping service.
2023-05-06 13:53:57.924 +00:00 [WRN] Using an in-memory repository. Keys will not be persisted to storage.
2023-05-06 13:53:57.976 +00:00 [WRN] Neither user profile nor HKLM registry available. Using an ephemeral key repository. Protected data will be unavailable when application exits.
2023-05-06 13:53:58.035 +00:00 [WRN] No XML encryptor configured. Key {a176ce6d-e7e0-4f66-a2fa-b23da5c90243} may be persisted to storage in unencrypted form.
2023-05-06 13:55:29.200 +00:00 [WRN] Stopping service.
2023-05-06 13:55:37.645 +00:00 [WRN] Using an in-memory repository. Keys will not be persisted to storage.
2023-05-06 13:55:37.680 +00:00 [WRN] Neither user profile nor HKLM registry available. Using an ephemeral key repository. Protected data will be unavailable when application exits.
2023-05-06 13:55:37.720 +00:00 [WRN] No XML encryptor configured. Key {bc98827e-f83f-4a74-8ebd-69e597e88331} may be persisted to storage in unencrypted form.

It still seems to be accepting connections and I’m not sure how long this has been going on.
Any ideas?

2

Actually I just was this in the journal?

SELinux is preventing /usr/share/dotnet/dotnet from map access on the file /etc/bitwarden/vault.db-shm. For complete SELinux messages run: sealert -l 4cd57147-3225-41ab-9abd-a13ab649c5d0
May 06 15:00:59 docker1 setroubleshoot[652240]: SELinux is preventing /usr/share/dotnet/dotnet from map access on the file /etc/bitwarden/vault.db-shm.

                                                *****  Plugin restorecon (92.2 confidence) suggests   ************************

                                                If you want to fix the label.
                                                /etc/bitwarden/vault.db-shm default label should be etc_t.
                                                Then you can run restorecon. The access attempt may have been stopped due to insufficient permissions to access a parent directory in which case try to change the following command accordingly.
                                                Do
                                                # /sbin/restorecon -v /etc/bitwarden/vault.db-shm

                                                *****  Plugin catchall_boolean (7.83 confidence) suggests   ******************

                                                If you want to allow domain to can mmap files
                                                Then you must tell SELinux about this by enabling the 'domain_can_mmap_files' boolean.

                                                Do
                                                setsebool -P domain_can_mmap_files 1

                                                *****  Plugin catchall (1.41 confidence) suggests   **************************

                                                If you believe that dotnet should be allowed map access on the vault.db-shm file by default.
                                                Then you should report this as a bug.
                                                You can generate a local policy module to allow this access.
                                                Do
                                                allow this access for now by executing:
                                                # ausearch -c '.NET ThreadPool' --raw | audit2allow -M my-NETThreadPool
                                                # semodule -X 300 -i my-NETThreadPool.pp
3

The bitwarden container logs show:-

2023-05-06 21:50:58,158 WARN received SIGTERM indicating exit request
2023-05-06 21:50:58,159 INFO waiting for identity, admin, api, icons, nginx, notifications to die
2023-05-06 21:51:01,188 INFO stopped: notifications (exit status 0)
2023-05-06 21:51:01,189 INFO waiting for identity, admin, api, icons, nginx to die
2023-05-06 21:51:01,191 INFO stopped: nginx (exit status 0)
2023-05-06 21:51:02,215 INFO stopped: icons (exit status 0)
2023-05-06 21:51:04,252 INFO stopped: api (exit status 0)
2023-05-06 21:51:04,253 INFO waiting for identity, admin to die
2023-05-06 21:51:05,292 INFO stopped: admin (exit status 0)
2023-05-06 21:51:06,334 INFO stopped: identity (exit status 0)
addgroup: The group `bitwarden' already exists.
adduser: The user `bitwarden' already exists.
2023-05-06 21:51:07,333 INFO Included extra file "/etc/supervisor.d/admin.ini" during parsing
2023-05-06 21:51:07,333 INFO Included extra file "/etc/supervisor.d/api.ini" during parsing
2023-05-06 21:51:07,333 INFO Included extra file "/etc/supervisor.d/events.ini" during parsing
2023-05-06 21:51:07,333 INFO Included extra file "/etc/supervisor.d/icons.ini" during parsing
2023-05-06 21:51:07,333 INFO Included extra file "/etc/supervisor.d/identity.ini" during parsing
2023-05-06 21:51:07,333 INFO Included extra file "/etc/supervisor.d/nginx.ini" during parsing
2023-05-06 21:51:07,333 INFO Included extra file "/etc/supervisor.d/notifications.ini" during parsing
2023-05-06 21:51:07,333 INFO Included extra file "/etc/supervisor.d/scim.ini" during parsing
2023-05-06 21:51:07,333 INFO Included extra file "/etc/supervisor.d/sso.ini" during parsing
2023-05-06 21:51:07,335 INFO RPC interface 'supervisor' initialized
2023-05-06 21:51:07,335 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2023-05-06 21:51:07,336 INFO supervisord started with pid 1
2023-05-06 21:51:08,338 INFO spawned: 'identity' with pid 36
2023-05-06 21:51:08,340 INFO spawned: 'admin' with pid 37
2023-05-06 21:51:08,342 INFO spawned: 'api' with pid 38
2023-05-06 21:51:08,344 INFO spawned: 'icons' with pid 39
2023-05-06 21:51:08,347 INFO spawned: 'nginx' with pid 40
2023-05-06 21:51:08,350 INFO spawned: 'notifications' with pid 41
2023-05-06 21:51:23,634 INFO success: identity entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-05-06 21:51:23,634 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-05-06 21:51:23,634 INFO success: api entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-05-06 21:51:23,634 INFO success: icons entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-05-06 21:51:23,634 INFO success: nginx entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-05-06 21:51:23,634 INFO success: notifications entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-05-06 21:52:37,042 WARN received SIGTERM indicating exit request
2023-05-06 21:52:37,043 INFO waiting for identity, admin, api, icons, nginx, notifications to die
2023-05-06 21:52:40,072 INFO stopped: notifications (exit status 0)