Immich-Server unhealthy
It was working just fine. Yesterday, I created new user and started backing up its files from mobile to the immich server and now at morning, cannot access immich anymore. immich_server shows as unhealthy.
It is setup through docker inside a LXC.
docker-compose.yml
https://pastebin.com/t1dNAWQj
.env file
https://pastebin.com/vuG0m4ec
Docker container logs
https://pastebin.com/bSR0cSZ7
' SERVICE CREATED STATUS PORTS immich_machine_learning ghcr.io/immich-app/immich-machine-learning:release "tini -- ./start.sh" immich-machine-learning 19 minutes ago Up About a minute (healthy)
immich_postgres docker.io/tensorchord/pgvecto-rs:pg14-v0.2.0@sha256:90724186f0a3517cf6914295b5ab410db9ce23190a2d9d0b9dd6463e3fa298f0 "docker-entrypoint.s…" database 19 minutes ago Up About a minute (healthy) 5432/tcp immich_redis docker.io/redis:6.2-alpine@sha256:eaba718fecd1196d88533de7ba49bf903ad33664a92debb24660a922ecd9cac8 "docker-entrypoint.s…" redis 7 weeks ago Up About a minute (healthy) 6379/tcp immich_server ghcr.io/immich-app/immich-server:release "tini -- /bin/bash s…" immich-server 19 minutes ago Up About a minute (unhealthy) 0.0.0.0:2283->2283/tcp' Server log: Error: connect ETIMEDOUT at Socket.<anonymous> (/usr/src/app/node_modules/ioredis/built/Redis.js:170:41) at Object.onceWrapper (node:events:638:28) at Socket.emit (node:events:524:28) at Socket._onTimeout (node:net:609:8) at listOnTimeout (node:internal/timers:594:17) at process.processTimers (node:internal/timers:529:7) { errorno: 'ETIMEDOUT', code: 'ETIMEDOUT', syscall: 'connect' }
Pastebin
docker-compose.yml - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
Pastebin
immich.env - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
Pastebin
docker container logs - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
5 Replies
:wave: Hey @arnob,
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:Like requested by the bot, can you also post the logs?
Sorry, I only posted partially.. now copied the whole log
It's failing to connect to redis, but I have no idea why
I do know that docker in LXC sometimes tends to give problems, though I've never seen it cause this kind before
Wait I fixed it by
docker compose down
docker compose up -d
:KEKWait: