IBM Support

Pod redis-ha-sever-1 in CrashLoopBackOff state

Question & Answer


Question

There are usually 3 redis-ha-sever pods in the statefulset redis-ha-server in CP4D.

Two of the them (redis-ha-server-0 and redis-ha-server-2) are running fine. The problem is that one of them (redis-ha-server-1) is stuck at CrashLoopBackOff state and it exits with the following errors:
1:S 23 Nov 2023 09:02:03.066 # Server initialized
1:S 23 Nov 2023 09:02:03.067 # Wrong signature trying to load DB from file
1:S 23 Nov 2023 09:02:03.067 # Fatal error loading the DB: Invalid argument. Exiting.
However, We try to scale the statefulset redis-ha-server down and up, it doesn't help.
scale sts redis-ha-server --replicas 0
scale sts redis-ha-server --replicas 3

[{"Type":"MASTER","Line of Business":{"code":"LOB76","label":"Data Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSHGYS","label":"IBM Cloud Pak for Data"},"ARM Category":[{"code":"a8m3p000000UoQtAAK","label":"Administration"}],"ARM Case Number":"TS014807183","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.7.3"}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
28 November 2023

UID

ibm17083984