ImmichI
Immich3y ago
Alan

immich_postgres exited with code 0/135

I messed up after the null-checksum issue in 1.58. I was unable to run the fix for it, so I decided to just restart everyting.

I have used the docker compose down -v command to purge everything.
I have updated my OS (apt update, apt upgrade).
I have rebooted my computer.
I have made sure that I have the newest docker-compose.yml.
I have made sure that I have the newest .env file.
I have done all this multiple times.

I have kept my upload folder as is, hoping that it can be re-used by the new installation.

I'm running Ubuntu 22.04.

Still, after running docker compose up, I keep getting weird errors. I am a complete newbie with docker, so I haven't been able to figure out what's wrong, but I believe it has to do with the database.

I keep seeing these messages in the log (when running docker compose up without -d):

immich_postgres exited with code 0
immich_postgres exited with code 135

(They repeat regularly, sometimes with code 0, sometimes with code 135.)

And then immich_microservices prints this, but I assume that's because the database isn't running:

immich_microservices | Error: connect ETIMEDOUT
immich_microservices | at Socket.<anonymous> (/usr/src/app/node_modules/ioredis/built/Redis.js:170:41)
immich_microservices | at Object.onceWrapper (node:events:627:28)
immich_microservices | at Socket.emit (node:events:513:28)
immich_microservices | at Socket._onTimeout (node:net:570:8)
immich_microservices | at listOnTimeout (node:internal/timers:569:17)
immich_microservices | at process.processTimers (node:internal/timers:512:7) {
immich_microservices | errorno: 'ETIMEDOUT',
immich_microservices | code: 'ETIMEDOUT',
immich_microservices | syscall: 'connect'
immich_microservices | }

And immich-server:

immich_server | [Nest] 1 - 06/10/2023, 6:30:32 PM ERROR [TypeOrmModule] Unable to connect to the database. Retrying (7)...

Any pointers would be very much appreciated!
Was this page helpful?