Immich server failed starting after deploying latest upgrade v1.135.0
Hi guys,
First time reaching you asking for help as I'm unable to find any solution to my issue.
After upgrading to 1.135.0 from 1.134 via Portainer (Community Edition2.30.0 STS) I'm getting the following error: "Failure Failed to deploy a stack: compose up operation failed: dependency failed to start: container immich_server is unhealthy"
Background information:
My current Immich instance is running "tensorchord/pgvecto-rs:pg14-v0.2.0" (the one before immich moved to ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0 in the "Hot Summer Release" version 133.
Actions:
Today I saw that a new version was released and proceeded to read the info.
I decided to start step by step and upgrade first the redis image version (ok). Then the immich server and machine learning image version (ok). So the situation at this point was having all the stack updated BUT the postgreSQL database.
Because the project is aiming for this new database image (due to the new features) I felt like I was falling out of date
with the database and - like it happened before when trying to update the database from tensorchord/pgvecto-rs:pg14-v0.2.0 to postgres:14-vectorchord0.3.0-pgvectors0.2.0 - I was confident I could roll back if something happen.. which obviously (murphy's law says) doesn't happened.
The error was the same: "immich_server is unhealthy" when trying to deploy the new db image AND after trying to re-deploy my current one tensorchord/pgvecto-rs:pg14-v0.2.0 I got again "immich_server is unhealthy".I'm pretty confident that if I could redeploy the 1.34 immich server and its machine-learning pair the service would start again. That could be a solution.
Current situation:
Currently the service is down. No possibility to access the containers (as the stack can't be deployed).
I would like to keep up to date with the product as much as possible (is evolving really fast and with GREAT features) so that's what brought me here asking (almost begging) for help. Thanks.
First time reaching you asking for help as I'm unable to find any solution to my issue.
After upgrading to 1.135.0 from 1.134 via Portainer (Community Edition2.30.0 STS) I'm getting the following error: "Failure Failed to deploy a stack: compose up operation failed: dependency failed to start: container immich_server is unhealthy"
Background information:
My current Immich instance is running "tensorchord/pgvecto-rs:pg14-v0.2.0" (the one before immich moved to ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0 in the "Hot Summer Release" version 133.
Actions:
Today I saw that a new version was released and proceeded to read the info.
I decided to start step by step and upgrade first the redis image version (ok). Then the immich server and machine learning image version (ok). So the situation at this point was having all the stack updated BUT the postgreSQL database.
Because the project is aiming for this new database image (due to the new features) I felt like I was falling out of date
with the database and - like it happened before when trying to update the database from tensorchord/pgvecto-rs:pg14-v0.2.0 to postgres:14-vectorchord0.3.0-pgvectors0.2.0 - I was confident I could roll back if something happen.. which obviously (murphy's law says) doesn't happened.
The error was the same: "immich_server is unhealthy" when trying to deploy the new db image AND after trying to re-deploy my current one tensorchord/pgvecto-rs:pg14-v0.2.0 I got again "immich_server is unhealthy".I'm pretty confident that if I could redeploy the 1.34 immich server and its machine-learning pair the service would start again. That could be a solution.
Current situation:
Currently the service is down. No possibility to access the containers (as the stack can't be deployed).
I would like to keep up to date with the product as much as possible (is evolving really fast and with GREAT features) so that's what brought me here asking (almost begging) for help. Thanks.
