Vaultwarden container exiting for no reason

[rishubn]

Subject of the issue

Vaultwarden container exiting for no reason (?)

Deployment environment

• vaultwarden version: 1.25.2

• Install method: container (podman 3.4.4), amd64 PC

• Other relevant details:

Steps to reproduce

podman run -d --name vaultwarden -v $PWD/data/vw-data:/data/:Z -e ROCKET_PORT=8080 -p 8080:8080 vaultwarden/server:latest

Expected behaviour

The container stays alive until killed by user or shutdown

Actual behaviour

Container runs for several minutes then shuts down for seemingly no reason - no reason is given in the log file

Troubleshooting data

[2022-10-04 08:57:33.528][response][INFO] (icon_internal) GET /icons/<domain>/icon.png => 200 OK
[2022-10-04 08:57:33.567][request][INFO] GET /icons/xilinx.com/icon.png
[2022-10-04 08:57:33.568][response][INFO] (icon_internal) GET /icons/<domain>/icon.png => 200 OK
[2022-10-04 09:00:17.105][vaultwarden][INFO] Exiting vaultwarden! <---- exits after 3 minutes unprompted
[2022-10-04 09:00:17.105][vaultwarden][INFO] Exiting vaultwarden!
[2022-10-04 09:00:17.105][rocket::server][WARN] Received SIGTERM. Shutdown already in progress.
[2022-10-04 09:00:17.106][vaultwarden][INFO] Vaultwarden process exited!

Anyway to get more detailed logs?

[jonas-w]

[2022-10-13 22:26:05.153][response][INFO] (icon_internal) GET /icons/<domain>/icon.png => 200 OK
[2022-10-13 22:51:44.680][vaultwarden][INFO] Exiting vaultwarden!
[2022-10-13 22:51:44.680][rocket::server][WARN] Received SIGTERM. Requesting shutdown.
[2022-10-13 22:51:44.682][vaultwarden][INFO] Vaultwarden process exited!

exactly the same thing happened 2 days ago for me.
I'm using version 1.25.2 (docker, Ubuntu LTS).

Maybe this could be "escalated" to an issue again, as this happened to both of us and maybe has something to do with version 1.25.2 as this never happened before.

[rishubn]

@jonas-w I solved the problem with loginctl enable-linger - I think systemd was killing the process beforehand

[jonas-w]

@rishubn thanks i will try this, if it happens again.

[jonas-w]

It just happened again i just realized it happened nearly at the same time.
First time it was 22:51:40 and now it was 22:45:40, i checked my cron jobs and none are executed at that time, will check if something else is triggered at this time.

[EricDriussi]

This has happened to me a couple of times but I'm unable to see a pattern or find anything in the logs.
I've got a hunch that systemd might be envolved but I can't find out for certain.
I've also checkedjournalctl --list-boots (maybe it wasn't restarting after maintenance on the server?) but there doesn't seem to be a relation.

Any idea how I can further troubleshoot this? Which logs to check specifically or what to try?

[EricDriussi]

Jesus Crist I was running on 1.24 -.-U Prolly gonna fix itself now

[mattv8]

Something very similar is happening to me on the latest version (2023-11). Should I open new issue or post my logs here?

[BlackDex]

Tried testing already?

[mattv8]

Hey I'm sorry for the delayed response. I was able to pin my issue down. It was due to misconfigured SMTP server settings. Once I corrected those, things became much more stable.