Immich•8mo ago

Fatal error loading the DB

Seems like my redis container isnt working?

1:M 16 May 2025 16:15:20.944 * monotonic clock: POSIX clock_gettime

1:M 16 May 2025 16:15:20.945 * Running mode=standalone, port=6379.

1:M 16 May 2025 16:15:20.945 # Server initialized

1:M 16 May 2025 16:15:20.945 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.

1:M 16 May 2025 16:15:20.945 # Can't handle RDB format version 11

1:M 16 May 2025 16:15:20.945 # Fatal error loading the DB: Invalid argument. Exiting.

1:M 16 May 2025 16:15:20.944 * monotonic clock: POSIX clock_gettime

1:M 16 May 2025 16:15:20.945 * Running mode=standalone, port=6379.

1:M 16 May 2025 16:15:20.945 # Server initialized

1:M 16 May 2025 16:15:20.945 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.

1:M 16 May 2025 16:15:20.945 # Can't handle RDB format version 11

1:M 16 May 2025 16:15:20.945 # Fatal error loading the DB: Invalid argument. Exiting.

1:M 16 May 2025 16:15:20.944 * monotonic clock: POSIX clock_gettime

1:M 16 May 2025 16:15:20.945 * Running mode=standalone, port=6379.

1:M 16 May 2025 16:15:20.945 # Server initialized

1:M 16 May 2025 16:15:20.945 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.

1:M 16 May 2025 16:15:20.945 # Can't handle RDB format version 11

1:M 16 May 2025 16:15:20.945 # Fatal error loading the DB: Invalid argument. Exiting.

1:M 16 May 2025 16:15:20.944 * monotonic clock: POSIX clock_gettime

1:M 16 May 2025 16:15:20.945 * Running mode=standalone, port=6379.

1:M 16 May 2025 16:15:20.945 # Server initialized

1:M 16 May 2025 16:15:20.945 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.

1:M 16 May 2025 16:15:20.945 # Can't handle RDB format version 11

1:M 16 May 2025 16:15:20.945 # Fatal error loading the DB: Invalid argument. Exiting.

Thanks in advance

Immich•5/16/25, 4:16 PM

:wave: Hey @Zippy-boy,

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
```
```
docker compose logs
```
docs
Container Status:
```
docker ps -a
```
```
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

Immich•5/16/25, 4:16 PM

Checklist

I have...

:ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
:ballot_box_with_check: read applicable release notes.
:ballot_box_with_check: reviewed the FAQs for known issues.
:ballot_box_with_check: reviewed Github for known issues.
:ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
:ballot_box_with_check: uploaded the relevant information (see below).
: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
```
```
fdisk -l
```
and
```
df -h
```
```
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

/close

command, and re-open it later if needed.

IImmich ## Checklist I have... 1. :ballot_box_with_check: verified I'm on the latest rel...

ImmichAPP•5/16/25, 4:17 PM

Successfully submitted, a tag has been added to inform contributors. :white_check_mark:

Fatal error loading the DB

References

Checklist

Information

Similar Threads

Similar Threads

References

Checklist

Information

Similar Threads