James
James
I'm running into these timeouts as well very consistently. Can confirm that bull stacks the concurrency. On v1.52.0 it says 7 thumbnail tasks are running.
According to discord user mudone these errors may be a result of the database timeout. https://github.com/immich-app/immich/blob/c584791b65c88bfc327cfbc55407502362897f14/server/libs/infra/src/database.config.ts#L21
The user on discord had success with a 60s timeout, but I do agree that it is probably more of a symptom. If things are running smoothly 10s should be...
My microservices has been running restricted, but I lessed these errors by expanding the resources available. I was not running into this before v1.50.
That being said I should probably run a test with nothing else running to make sure it is not a case of other services competing for the cpu cycles.
I updated to v1.53.0 and also deployed to a node with more available resources. I am still seeing these errors, but the microservices container has not shutdown and it appears...
> The WiFi setting only applies to the background backup. Was I not backing up in the background? There is significant data usage from the background.
> Is this new websocket what is cauing the feed to jump back up to the top each time a rotation is done - or is that a separate bug?...
Confirmed this is fixed.
@maxi017 I was able to with some trial and error. I used this [article](https://echoicdev.home.blog/2021/12/13/how-to-add-secrets-to-your-docker-containers/) for reference. Make sure the `docker-entrypoint.sh` file is executable and add any other variables you want...