Redis RDB corruption causing Redis to crashloop and immich unresponsive #20777
Unanswered
mason-larobina
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have searched the existing issues, both open and closed, to make sure this is not a duplicate report.
The bug
The Redis container fails to start when encountering corrupted data (common when Docker containers restart unexpectedly or during low-memory situations).
This breaks Immich functionality as the app service fails to connect to Redis. Recovery is cumbersome because:
dump.rdbProposed Solutions:
In my case I used a named volume in the
docker-compose.ymlto change the redis data directory to './redis:/data' which moved away from the corrupt data.rdb and now Immich is operational for me again.The OS that Immich Server is running on
Archlinux
Version of Immich Server
v1.137.3
Version of Immich Mobile App
v1.137.2 build.3002
Platform with the issue
Your docker-compose.yml content
Your .env content
Reproduction steps
Unknown. I just found immich unresponsive and throwing up unable to fetch resource errors.
Relevant log output
Additional information
No response
Beta Was this translation helpful? Give feedback.
All reactions