Bitwarden.sh version 2023.9.0
Docker version 24.0.7, build afdd53b
Docker Compose version v2.18.1
I’ve been using Bitwarden for about 1 year, selfhosting on Proxmox LXC container. No issues until recently. When I noticed the instance went offline. When I check the container, the cpu usage was pegged and all 8gb of memory were in use. It had been running for several months without a restart so I executed a ./bitwarden.sh stop
The bitwarden-events and bitwarden-api containers shutdown within 3 secs. bitwarden-nginx, bitwarden-notifications and bitwarden-icons containers took between 289 and 554 secs to shutdown. bitwarden-sso, bitwarden-attachments, bitwarden-web, bitwarden-admin and bitwarden-identity containers all took over 1000 secs. It seemed odd because previous shutdowns tooks less than 60 secs for all containers. I remade the container using a backup from 3 days prior. It started fine and had been running okay for 3-4 days until I again noticed high cpu and memory usage. I doubled the memory to 16gb and the cpu use dropped. I could see a steady increase in the memory use. Again, I executed a ./bitwarden.sh stop
This time the bitwarden-sso, bitwarden-attachments, bitwarden-web, bitwarden-admin and bitwarden-identity containers have not stopped. Checking htop shows the bitwarden user has over 80 threads of the command /opt/mssql/bin/sqlservr running and another 20 or so of the command dotnet /app/api.dll and 1 of /bin/sh /backup-db.sh loop and sleep 86399
While waiting for the containers to stop, the cpu and memory use have dropped considerably. I’m not sure how to stop the containers or if I they will stop on their own eventually. Any help would be appreciated.
Update - Some containers still trying to stop with attachments, web and identity at over 40k secs. The sso container stopped after 38k secs.
I migrated my setup to a dedicated debian vm but after a few hours is now using 95% of the 8gb memory. How much memory should it be consuming? I believe 4gb is the recommended amount so why is mine using so much?