Skip to main content
NetApp Knowledge Base

Data Classification inaccessible due to Redis Container Crash

Views:
96
Visibility:
not set
Votes:
0
Category:
netapp_console
Specialty:
ds_dc
Last Updated:

Applies to

NetApp Data Classification

Issue

Data Classification Governance console fails to load with the error below:
clipboard_2dc547d0-e093-4eef-bbe3-3978df0334b4.png

Cause

The Redis Container getting crashed due to corrupted AOF file.
  • Classification container logs reports Redis service not ready
    Log : datasense-ds_reports-1:

log v1.0 | 2026-02-12 09:57:49,655 | INFO | ds_logger | waitfor | 344 | 16 | None | waitfor_344 | Checking readiness of [redis]
log v1.0 | 2026-02-12 09:57:49,657 | ERROR | ds_logger | waitfor | 46 | 16 | None | waitfor_46 | Service [redis] is not ready:
Error 111 connecting to redis:6379. Connection refused.
log v1.0 | 2026-02-12 09:57:50,658 | INFO | ds_logger | waitfor | 344 | 16 | None | waitfor_344 | Checking readiness of [redis]
log v1.0 | 2026-02-12 09:57:50,659 | ERROR | ds_logger | waitfor | 46 | 16 | None | waitfor_46 | Service [redis] is not ready:
Error 111 connecting to redis:6379. Connection refused.
log v1.0 | 2026-02-12 09:57:51,660 | INFO | ds_logger | waitfor | 344 | 16 | None | waitfor_344 | Checking readiness of [redis]
log v1.0 | 2026-02-12 09:57:51,671 | ERROR | ds_logger | waitfor | 46 | 16 | None | waitfor_46 | Service [redis] is not ready:
Redis is loading the dataset in memory

  • The Redis container getting crashed for every 4-5 seconds.

# podman ps |grep redis
e0b94722d0d5  docker.io/datasense/redis:ef9013fa0648b8d0b7a065f23f046918            bash /etc/redis/r...  5 weeks ago   Up 28 hours                     
2fd9105f4f93     docker.io/datasense/redis:ef9013fa0648b8d0b7a065f23f046918            bash /etc/redis/r...  5 weeks ago   Up 1 second  <==    

  • The AOF file in redis container got corrupted.
    Log : datasense-redis-1

1:M 12 Feb 2026 09:57:37.258 * Server initialized
1:M 12 Feb 2026 09:57:37.259 * Reading RDB base file on AOF loading...
1:M 12 Feb 2026 09:57:37.259 * Loading RDB produced by version 7.4.3
1:M 12 Feb 2026 09:57:37.259 * RDB age 590096 seconds
1:M 12 Feb 2026 09:57:37.259 * RDB memory usage when created 199.17 Mb
1:M 12 Feb 2026 09:57:37.259 * RDB is base AOF
1:M 12 Feb 2026 09:57:37.521 * Done loading RDB, keys loaded: 9567, keys expired: 0.
1:M 12 Feb 2026 09:57:37.521 * DB loaded from base file appendonly.aof.5815.base.rdb: 0.262 seconds
1:M 12 Feb 2026 09:57:37.586 # Bad file format reading the append only file appendonly.aof.5815.incr.aof: make a backup of your AOF file, then use ./redis-check-aof --fix <filename.manifest>

Solution


Procedure : 
  1. Start Redis container manually with bash from path /opt/netapp/Datasense
    cd /opt/netapp/Datasense
    docker-compose run redis bash
  2. List the files under the target directory:
    redis@:/data$ cd /data/appendonlydir
    redis@:/data$ ls -la
  3. Check all "*.incr.aof" file and fix it one-by-one with below command:
    redis@:/data$ redis-check-aof --fix appendonly.aof.222.incr.aof (file names may be different, they are in /data/appendonlydir inside the container)
  4. Exit from the container:
    redis@:/data$ exit 
  5. Check if the Redis container is now running:
    sudo docker ps | grep -i redis
  6. Check if Data Classification Governance UI on the NetApp Console is now accessible.

Partner Notes

partnerNotes_text

Internal Notes

On case# 2010618285, docker-compose version GLIBC error reported while starting the redis container with bash.

[root@]# docker-compose run redis bash
docker-compose: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by docker-compose)
docker-compose: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by docker-compose)

Followed the procedure in below Jira text and upgraded the docker-compose version.
https://jira.ngage.netapp.com/secure...0/CPE-9310.txt

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support