tried to do postgress dump and something went wrong
Hi everyone!
I tried to do postgress dump and something went wrong. I stopped all containers in immich, but command didn't work so I started only postgress container and did dump with following command:
docker exec -t immich_postgres pg_dumpall --clean --if-exists --username=postgres | gzip > "/media/cavecenter/easystore/DataBaseCopyImmich_AUG_2025/dump.sql.gz"
Copy is on different drive than the actual immich photos.
after that I tried to start all immich services but getting this:
Error: getaddrinfo ENOTFOUND database
immich_server | at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:122:26) {
immich_server | errno: -3008,
immich_server | code: 'ENOTFOUND',
immich_server | syscall: 'getaddrinfo',
immich_server | hostname: 'database'
immich_server | }
immich_server | microservices worker error: Error: getaddrinfo ENOTFOUND database, stack: Error: getaddrinfo ENOTFOUND database
immich_server | at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:122:26)
immich_server | microservices worker exited with code 1
immich_server | Killing api process
immich server and postgress keep restarting.
I have not changed anything inside the .env or docker_compose.yml
Could you advice how I can fix it? 😄
7 Replies
:wave: Hey @Tribux,
Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:.
References
- Container Logs:
docker compose logs docs
- Container Status: docker ps -a docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA
Checklist
I have...
1. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
2. :blue_square: read applicable release notes.
3. :blue_square: reviewed the FAQs for known issues.
4. :blue_square: reviewed Github for known issues.
5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: uploaded the relevant information (see below).
7. :blue_square: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable
(an item can be marked as "complete" by reacting with the appropriate number)
Information
In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:
- Your docker-compose.yml and .env files.
- Logs from all the containers and their status (see above).
- All the troubleshooting steps you've tried so far.
- Any recent changes you've made to Immich or your system.
- Details about your system (both software/OS and hardware).
- Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
- The version of the Immich server, mobile app, and other relevant pieces.
- Any other information that you think might be relevant.
Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)
If this ticket can be closed you can use the /close command, and re-open it later if needed.Did you do a compose up or just docker start
I did both...I have alias immich that is doing docker up but also did manually tried to start with docker start name of service...but it might be weird..I have just restarted machine and now have: 2025-04-01 14:24:41.691 UTC [1] FATAL: could not write lock file "postmaster.pid": No space left on device 👀
Your disk is full
Yep...ufff I prefer that kind of problem haha, but weird that it happend after just database dump..I saved some space removing 4GB of Journal logs, new drive order in progress...Thanks guys for such a
quick response and you can remove thread if needed!
"weird that it happend after just creating a large file" is a bit of an odd take 😛
To my defense hehe, the dump was just 140MB on a different drive :p