not sure how this happened
this error keeps spaming in the console and immich is not accessible at all
[Nest] 11044 - 05/07/2023, 4:55:41 PM ERROR [TypeOrmModule] Unable to connect to the database. Retrying (9)...
Error: connect ECONNREFUSED 127.0.0.1:5432
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
[Nest] 11044 - 05/07/2023, 4:55:41 PM ERROR [ExceptionHandler] connect ECONNREFUSED 127.0.0.1:5432
Error: connect ECONNREFUSED 127.0.0.1:5432
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
16 Replies
prior to the error this is in the console prior
[Nest] 11228 - 05/07/2023, 4:58:46 PM LOG [NestFactory] Starting Nest application...
[Nest] 11228 - 05/07/2023, 4:58:46 PM LOG [InstanceLoader] TypeOrmModule dependencies initialized +87ms
[Nest] 11228 - 05/07/2023, 4:58:46 PM LOG [InstanceLoader] BullModule dependencies initialized +1ms
[Nest] 11228 - 05/07/2023, 4:58:46 PM LOG [InstanceLoader] DownloadModule dependencies initialized +0ms
[Nest] 11228 - 05/07/2023, 4:58:46 PM LOG [InstanceLoader] ConfigHostModule dependencies initialized +1ms
[Nest] 11228 - 05/07/2023, 4:58:46 PM LOG [InstanceLoader] DiscoveryModule dependencies initialized +1ms
[Nest] 11228 - 05/07/2023, 4:58:46 PM LOG [InstanceLoader] ConfigModule dependencies initialized +9ms
[Nest] 11228 - 05/07/2023, 4:58:46 PM LOG [InstanceLoader] ScheduleModule dependencies initialized +1ms
[Nest] 11228 - 05/07/2023, 4:58:46 PM LOG [InstanceLoader] BullModule dependencies initialized +0ms
[Nest] 11228 - 05/07/2023, 4:58:46 PM LOG [InstanceLoader] BullModule dependencies initialized +1ms
Looks like it can't access the database. You can try restarting the server
docker-compose restart immich-server. If that doesn't help, use docker-compose ps to check whether the DB is running.i have tried restarting its very odd cause nothing changed in the past few days
Do you use docker-compose or Portainer?
cli
Do you see this line?
immich_postgres ... Up
imma just delete it all and try a reinstall keeping configs
It might be worth investigating the root-cause. This is definitely not normal behavior and could happen again
yer i had been running everything fine until recently
the other issue i posted about a few days ago and now this one
They're probably unrelated
oh yer definitely unrelated
Can you check?
my install doesnt show that way
postgres is running as its own container and yes is running
What did you use for installing?
can i pm you ?
Sure