Connectivity to Redis issue?

Greetings, I keep getting logs such as this, any idea what causes this and how to solve it? https://logs.notifiarr.com/?ee78890d585c2f8b#ERWUp1AUd8fPccozcugPS2DaBWU9kSuiJ8vn2PhZWs5z I already verified the stuff is up and running. I have a feeling this is due to updating today but not sure.
user@localhost:~/immich$ sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
70dbbf740fad ghcr.io/immich-app/immich-server:release "tini -- /bin/bash -…" About an hour ago Up 30 minutes (healthy) 0.0.0.0:2283->2283/tcp, [::]:2283->2283/tcp immich_server
12d7c290d3a8 ghcr.io/immich-app/immich-machine-learning:release "tini -- python -m i…" About an hour ago Up 30 minutes (healthy) immich_machine_learning
c8062d745a6a valkey/valkey:8-bookworm "docker-entrypoint.s…" 10 days ago Up 30 minutes (healthy) 6379/tcp immich_redis
86fd50a28c64 ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0 "/usr/local/bin/immi…" 10 days ago Up 30 minutes (healthy) 5432/tcp immich_postgres
user@localhost:~/immich$
user@localhost:~/immich$ sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
70dbbf740fad ghcr.io/immich-app/immich-server:release "tini -- /bin/bash -…" About an hour ago Up 30 minutes (healthy) 0.0.0.0:2283->2283/tcp, [::]:2283->2283/tcp immich_server
12d7c290d3a8 ghcr.io/immich-app/immich-machine-learning:release "tini -- python -m i…" About an hour ago Up 30 minutes (healthy) immich_machine_learning
c8062d745a6a valkey/valkey:8-bookworm "docker-entrypoint.s…" 10 days ago Up 30 minutes (healthy) 6379/tcp immich_redis
86fd50a28c64 ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0 "/usr/local/bin/immi…" 10 days ago Up 30 minutes (healthy) 5432/tcp immich_postgres
user@localhost:~/immich$
PrivateBin
Encrypted note on PrivateBin
Visit this link to see the note. Giving the URL to anyone allows them to access the note, too.
5 Replies
Immich
Immich3w ago
:wave: Hey @Mr. Hoorn (Asp. Learning Expert), 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.
Mraedis
Mraedis3w ago
What are you using to run immich?
Sergey Katsubo
Error: could not renew lock for job 190
Error: could not renew lock for job 190
This error will be gone after immich-server restart. There is a race condition in BullMQ queue manager: sometimes a worker gets stalled/busy (e.g. overloaded system), then it resumes execution, but the job was already processed, so there is no lock anymore -> nothing to renew -> "could not renew". (I encounter it quite regularly on a test instance on my macbook after resuming from sleep) As Joren mentioned, it would be helpful to know your platform.
Mr. Hoorn (Asp. Learning Expert)
Docker compose On Qubes OS Adjusting my compose fixed it. I was dumb and forgot to check for compose changes after updating!
Immich
Immich3w ago
This thread has been closed. To re-open, use the button below.

Did you find this page helpful?