EAI_AGAIN log V2.0.0
Updated to V2.0.0 this evening and this is the server log. It appears the EAI_AGAIN database isn’t responding. I’m using Portainer, and repulled/redeployed the image to update like I usually do. I restarted the stack, then independently restarted the server then the database container. Here’s the full log.
I’ve tried in chrome and safari, and in incognito. I’m not on a reverse proxy.
Initializing Immich v2.0.0
Detected CPU Cores: 12
Starting api worker
Starting microservices worker
[Nest] 7 - 10/02/2025, 2:30:20 AM LOG [Microservices:EventRepository] Initialized websocket server
Error: getaddrinfo EAI_AGAIN database
at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:122:26) {
errno: -3001,
code: 'EAI_AGAIN',
syscall: 'getaddrinfo',
hostname: 'database'
}
microservices worker error: Error: getaddrinfo EAI_AGAIN database, stack: Error: getaddrinfo EAI_AGAIN database
at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:122:26)
microservices worker exited with code 1
Killing api process
5 Replies
:wave: Hey @monk(david),
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. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
2. :ballot_box_with_check: read applicable release notes.
3. :ballot_box_with_check: reviewed the FAQs for known issues.
4. :ballot_box_with_check: reviewed Github for known issues.
5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
6. :ballot_box_with_check: uploaded the relevant information (see below).
7. :ballot_box_with_check: 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.
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:I use portainer/docker compose on Ubuntu and rarely do anything outside of portainer. I’ve had issues setting up volumes on the past and lost data, so I’m very cautious on any changes.
The database isn't running
Well damn. Database wasn’t running because the hard drive was full. Thanks boOtzz
This thread has been closed. To re-open, use the button below.