Today, I have issue of n8n redis

[cmdntd987]

Is there any issue with n8n redis nowadays?
I have docker-compose like this:

  redis:
    image: redis:latest
    container_name: io_redis
    restart: always
    networks:
      - bridge_network
    extra_hosts:
      - "host.docker.internal:host-gateway"
    ports:
      - "6379:6379"
    # This redis for server:6379
    volumes:
      - /my/path:/data
    healthcheck:
      test: ['CMD', 'redis-cli', 'ping']
      interval: 5s
      timeout: 5s
      retries: 10
    logging:
      driver: "json-file"
      options:
        max-size: "10m"
        max-file: "3"

It is ran ok. But today, it has errors:

1:M 22 Mar 2025 04:26:21.559 * monotonic clock: POSIX clock_gettime

1:M 22 Mar 2025 04:26:21.560 * Running mode=standalone, port=6379.

1:M 22 Mar 2025 04:26:21.560 * Server initialized

1:M 22 Mar 2025 04:26:21.560 # Wrong signature trying to load DB from file

1:M 22 Mar 2025 04:26:21.560 # Fatal error loading the DB, check server logs. Exiting.

1:C 22 Mar 2025 04:27:21.898 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo

1:C 22 Mar 2025 04:27:21.898 * Redis version=7.4.2, bits=64, commit=00000000, modified=0, pid=1, just started

1:C 22 Mar 2025 04:27:21.898 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf

1:M 22 Mar 2025 04:27:21.899 * monotonic clock: POSIX clock_gettime

1:M 22 Mar 2025 04:27:21.900 * Running mode=standalone, port=6379.

1:M 22 Mar 2025 04:27:21.900 * Server initialized

1:M 22 Mar 2025 04:27:21.901 # Wrong signature trying to load DB from file

1:M 22 Mar 2025 04:27:21.901 # Fatal error loading the DB, check server logs. Exiting.

[Miquel_Colomer]

Hi @cmdntd987

It looks like you’re having an issue with Redis not being able to load the database due to a “wrong signature” error. This typically happens if the RDB file is corrupted or incompatible with your current Redis version. Here’s what you can try to fix it:

1. Remove the Corrupted RDB File: If you’re okay with losing the current data, you can remove the existing RDB file in the /my/path directory and let Redis create a new one on startup. After deleting the RDB file, restart the Redis container.
2. Check Redis Logs: Look at the logs for any additional information. You can run:

docker logs io_redis

to see if there’s anything more helpful to identify the root cause.
3. Ensure Version Compatibility: If you’ve recently upgraded Redis, the format of the RDB file might be incompatible with the newer version. Check if the version you’re running matches the version that created the RDB file.
4. Use a Redis Config File: Redis is warning about no config file being specified. Consider providing a custom redis.conf to ensure Redis is configured as expected.
5. Redis Data Cleanup: If it’s not critical to preserve the data, try wiping the Redis data entirely by deleting the contents in the /my/path directory.
6. Volume Issues: Make sure the directory you’re mounting for Redis data (/my/path:/data) has the correct permissions and is accessible.
7. Try a Different Redis Version: If none of the above works, try running a different Redis version in case there’s an issue with the specific one you’re using.

I hope this helps!

[cmdntd987]

I see 3 files here:

backup.db
dump.rdb
temp-xx.rdb

[cmdntd987]

I deleted dump.rdb and temp.rdb.
Now it is ok.