Zoltrix
Zoltrix
PostsComments
IImmich
Created by Zoltrix on 4/12/2025 in #help-desk-support
microservices worker exited with code 1
Ok from doing some research you can apply a label to an individual container that is built from a stack... the change will not persist once that stack is re-deployed, but it should not catastrophically break things like it has done with Immich
23 replies
IImmich
Created by Zoltrix on 4/12/2025 in #help-desk-support
microservices worker exited with code 1
No description
23 replies
IImmich
Created by Zoltrix on 4/12/2025 in #help-desk-support
microservices worker exited with code 1
Restored from backup to a second docker server... was all running ok... once I tried to exclude the containers from auto updating with Watchtower (eg, apply the "com.centurylinklabs.watchtower.enable" label to the Immich containers) it shit the bed again and broke... incidentally this is what must have broke it on my first docker server, as I was trying to exclude them from Watchtower, I didn't think it could have been the cause when it first happened... so no idea if this is a bug or not? 🤷‍♂️
23 replies
IImmich
Created by Zoltrix on 4/12/2025 in #help-desk-support
microservices worker exited with code 1
Just confirming that @Alex does mention it is required here: https://discord.com/channels/979116623879368755/1049703391762321418/threads/1359070399916146729
23 replies
IImmich
Created by Zoltrix on 4/12/2025 in #help-desk-support
microservices worker exited with code 1
Might have to try a restore... am concerned though that following the instructions https://immich.app/docs/administration/backup-and-restore/ and running a docker compose down -v command might delete the non Immich containers as well...
23 replies
IImmich
Created by Zoltrix on 4/12/2025 in #help-desk-support
microservices worker exited with code 1
Users here reporting same issue: https://github.com/immich-app/immich/issues/16054 Some reported rolling back to v1.125.7 fixed it. I tried that, now getting the following:
23 replies
IImmich
Created by Zoltrix on 4/12/2025 in #help-desk-support
microservices worker exited with code 1
I noticed this thread mentions permission issues with group and user ID https://discord.com/channels/979116623879368755/1049703391762321418/threads/1359070399916146729 My env doesn't appear to have PUID and PGID variables, but it never has, and has worked. They weren't listed in the instructions I followed here https://immich.app/docs/install/portainer/ Of course I might be on the wrong track 🤷‍♂️
23 replies
IImmich
Created by Zoltrix on 4/12/2025 in #help-desk-support
microservices worker exited with code 1
From latest postgres logs: 
2025-04-12 07:24:45.672 UTC [1] LOG:  starting PostgreSQL 14.17 (Debian 14.17-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-04-12 07:24:45.672 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2025-04-12 07:24:45.672 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2025-04-12 07:24:45.674 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-04-12 07:24:45.678 UTC [28] LOG:  database system was shut down at 2025-04-12 07:24:45 UTC
[2025-04-12T07:24:45Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/17575".
[2025-04-12T07:24:45Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/17331".
[2025-04-12T07:24:45Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/17575/segments/d8d491f2-5cb4-4485-a400-7a7966e3fa2b".
2025-04-12 07:24:45.685 UTC [1] LOG:  database system is ready to accept connections
[2025-04-12T07:24:45Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/17331/segments/a079820e-c1bc-41f7-b040-0f65f1a08e42".
2025-04-12 07:24:45.672 UTC [1] LOG:  starting PostgreSQL 14.17 (Debian 14.17-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-04-12 07:24:45.672 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2025-04-12 07:24:45.672 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2025-04-12 07:24:45.674 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-04-12 07:24:45.678 UTC [28] LOG:  database system was shut down at 2025-04-12 07:24:45 UTC
[2025-04-12T07:24:45Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/17575".
[2025-04-12T07:24:45Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/17331".
[2025-04-12T07:24:45Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/17575/segments/d8d491f2-5cb4-4485-a400-7a7966e3fa2b".
2025-04-12 07:24:45.685 UTC [1] LOG:  database system is ready to accept connections
[2025-04-12T07:24:45Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/17331/segments/a079820e-c1bc-41f7-b040-0f65f1a08e42".
23 replies
IImmich
Created by Zoltrix on 4/12/2025 in #help-desk-support
microservices worker exited with code 1
No description
23 replies
IImmich
Created by Zoltrix on 4/12/2025 in #help-desk-support
microservices worker exited with code 1
23 replies
IImmich
Created by Zoltrix on 4/12/2025 in #help-desk-support
microservices worker exited with code 1
Not sure if the above helps? Assuming that confirms the database has content?
23 replies
IImmich
Created by Zoltrix on 4/12/2025 in #help-desk-support
microservices worker exited with code 1
23 replies