Release 3.0.0 Issue - Reading RDB base file on AOF loading...Can't handle RDB format version 12 #1310
-
Current BehaviorAfter upgrading to release 3.0.0, I've found that Redis Image fails to start with error "Can't handle RDB format version 12". Expected BehaviorValkey 8 does not support the proprietary 7.4.0 Redis database format. Workaround required or a version that will allow Redis / Valkey to start properly. Docker Compose VersionDocker Compose version v2.29.2-desktop.2 Docker VersionThe git RevisionThe git StatusStartup Commanddocker compose up --detach NetBox LogsContent of docker-compose.override.ymlservices:
netbox:
image: netbox:latest-plugins
ports:
- "8000:8080"
# If you want the Nginx unit status page visible from the
# outside of the container add the following port mapping:
# - "8001:8081"
healthcheck:
# Time for which the health check can fail after the container is started.
# This depends mostly on the performance of your database. On the first start,
# when all tables need to be created the start_period should be higher than on
# subsequent starts. For the first start after major version upgrades of NetBox
# the start_period might also need to be set higher.
# Default value in our docker-compose.yml is 60s
start_period: 120s
# environment:
# SKIP_SUPERUSER: "false"
# SUPERUSER_API_TOKEN: ""
# SUPERUSER_EMAIL: ""
# SUPERUSER_NAME: ""
# SUPERUSER_PASSWORD: ""
build:
context: .
dockerfile: Dockerfile-Plugins
restart: unless-stopped
netbox-worker:
image: netbox:latest-plugins
build:
context: .
dockerfile: Dockerfile-Plugins
restart: unless-stopped
netbox-housekeeping:
image: netbox:latest-plugins
build:
context: .
dockerfile: Dockerfile-Plugins
restart: unless-stopped
postgres:
restart: unless-stopped
redis:
restart: unless-stopped
redis-cache:
restart: unless-stopped
tls:
image: caddy:2-alpine
depends_on:
- netbox
volumes:
- ./ssl/localhost+2.pem:/etc/ssl/private/localhost.crt:ro,z
- ./ssl/localhost+2-key.pem:/etc/ssl/private/localhost.key:ro,z
- ./ssl/Caddyfile:/etc/caddy/Caddyfile:ro
ports:
- 80:80 # Allows for http redirection
- 443:443
restart: unless-stopped |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
|
same here... This error message indicates that is attempting to load an RDB file that is in a newer or incompatible format (version 12) that is not supported by the currently running version (7.9.240). 1:C 04 Sep 2024 13:34:19.489 * oO0OoO0OoO0Oo Valkey is starting oO0OoO0OoO0Oo |
Beta Was this translation helpful? Give feedback.
-
|
Hi @AnID-BW To work around the issue I first did a "docker compose down" and then deleted the netbox-redis-data and netbox-redis-cache-data volumes. These are recreated after the "docker compose up". I was then able to get Netbox running. I have a separate issue where I seem to be getting Netbox 4.0.11 instead of 4.1, but I'm unsure if these issues are related. |
Beta Was this translation helpful? Give feedback.
-
|
The data in Redis / Valkey is used as transient data so the volumes can be re-created without problem. |
Beta Was this translation helpful? Give feedback.
Hi @AnID-BW
The core data is in the Postgres database, so I'm not sure if this is transient data that gets rebuilt from the Postgres data.
Whenever I've moved data between different instances of Netbox, I've only copied a dump of the Postgres database and I've not experienced any issues.
To work around the issue I first did a "docker compose down" and then deleted the netbox-redis-data and netbox-redis-cache-data volumes. These are recreated after the "docker compose up".
I was then able to get Netbox running.
I have a separate issue where I seem to be getting Netbox 4.0.11 instead of 4.1, but I'm unsure if these issues are related.
#1305