Nc-aio stuck loading redis

ℹ️ Support 📦 Appliances (Docker, Snappy, VM, NCP, AIO)
, ,
1
Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

The Basics

  • Operating system and version (e.g., Ubuntu 24.04):
    • Unraid 7.2.3
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • Aio v 12.3.0
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • Cloudflared tunnel

Summary of the issue you are facing:

Nc-aio master container is failing to start the next cloud container, which appears to be being caused by redis throwing an error

Log entries

#### 2026-01-12T02:09:47.585947956Z Memory overcommit is disabled but necessary for safe operation

2026-01-12T02:09:47.585980567Z See https://github.com/nextcloud/all-in-one/discussions/1731 how to enable overcommit

2026-01-12T02:09:47.585983392Z Redis has started

2026-01-12T02:09:47.596294248Z 7:C 12 Jan 2026 02:09:47.596 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it 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.

2026-01-12T02:09:47.600050516Z 7:M 12 Jan 2026 02:09:47.600 # Short read or OOM loading DB. Unrecoverable error, aborting now.

2026-01-12T02:09:47.600062799Z 7:M 12 Jan 2026 02:09:47.600 # Internal error in RDB reading offset 0, function at rdb.c:3714 -> Unexpected EOF reading RDB file

2026-01-12T02:09:47.601471362Z \[offset 0\] Checking RDB file dump.rdb

2026-01-12T02:09:47.601481461Z \[offset 26\] AUX FIELD redis-ver = '8.2.3'

2026-01-12T02:09:47.601483464Z \[offset 40\] AUX FIELD redis-bits = '64'

2026-01-12T02:09:47.601484917Z \[offset 52\] AUX FIELD ctime = '1767391714'

2026-01-12T02:09:47.601486149Z \[offset 67\] AUX FIELD used-mem = '2246088'

2026-01-12T02:09:47.601487302Z \[offset 79\] AUX FIELD aof-base = '0'

2026-01-12T02:09:47.601488544Z \[offset 81\] Selecting DB ID 0

2026-01-12T02:09:47.601489706Z --- RDB ERROR DETECTED ---

2026-01-12T02:09:47.601490858Z \[offset 495616\] Unexpected EOF reading RDB file

2026-01-12T02:09:47.601492040Z \[additional info\] While doing: read-key

2026-01-12T02:09:47.601493203Z \[additional info\] Reading type 0 (string)

2026-01-12T02:09:47.601494375Z \[info\] 846 keys read

2026-01-12T02:09:47.601495607Z \[info\] 844 expires

2026-01-12T02:09:47.601497491Z \[info\] 837 already expired

2026-01-12T02:09:47.601499434Z \[info\] 0 subexpires
2

Hi, first of all I would recommend that you follow the instructions below. Maybe this fixes your problem already:

3

I followed the steps on that link, and verified that the file is there with that flag set, but I am still getting the same errors each time it reboots

4

Hm, can you stop the containers via the AIO interface, run sudo docker rm nextcloud-aio-redis; sudo docker volume rm nextcloud_aio_redis and start the containers again via the AIO interface and check if that helps?

5

That seems to have resolved the memory overcommit bit, but the logs are showing redis still isn’t happy, and NC is still waiting for it before launching

2026-01-12T21:32:56.227538834Z Redis has started
2026-01-12T21:32:56.235483345Z 7:M 12 Jan 2026 21:32:56.235 # Short read or OOM loading DB. Unrecoverable error, aborting now.
2026-01-12T21:32:56.235497952Z 7:M 12 Jan 2026 21:32:56.235 # Internal error in RDB reading offset 0, function at rdb.c:3714 -> Unexpected EOF reading RDB file
2026-01-12T21:32:56.236708121Z [offset 0] Checking RDB file dump.rdb
2026-01-12T21:32:56.236709974Z [offset 26] AUX FIELD redis-ver = '8.2.3'
2026-01-12T21:32:56.236711407Z [offset 40] AUX FIELD redis-bits = '64'
2026-01-12T21:32:56.236712689Z [offset 52] AUX FIELD ctime = '1767391714'
2026-01-12T21:32:56.236713892Z [offset 67] AUX FIELD used-mem = '2246088'
2026-01-12T21:32:56.236715104Z [offset 79] AUX FIELD aof-base = '0'
2026-01-12T21:32:56.236716416Z [offset 81] Selecting DB ID 0
2026-01-12T21:32:56.236717759Z --- RDB ERROR DETECTED ---
2026-01-12T21:32:56.236718981Z [offset 495616] Unexpected EOF reading RDB file
2026-01-12T21:32:56.236720213Z [additional info] While doing: read-key
2026-01-12T21:32:56.236721406Z [additional info] Reading type 0 (string)
2026-01-12T21:32:56.236722618Z [info] 846 keys read
2026-01-12T21:32:56.236723820Z [info] 844 expires
2026-01-12T21:32:56.236725093Z [info] 837 already expired
2026-01-12T21:32:56.236726315Z [info] 0 subexpires