F5 DSSM Log Message ListΒΆ
| ID Number | Description |
| 06200000 | Started log level watcher (PID: $LOGLEVEL_WATCHER_PID) monitoring $LOGLEVEL_FILE |
| 06200001 | dssm:start |
| 06200002 | This is for SPK |
| 06200003 | TLS is explicitly disabled |
| 06200004 | TLS is enabled (default) |
| 06200005 | db_tlscert_string = $db_tlscert_string |
| 06200006 | sentinel_tlscert_string = $sentinel_tlscert_string |
| 06200007 | tlscert_string = $tlscert_string |
| 06200008 | Logging POD details for $HOSTNAME... |
| 06200009 | Sentinel-0: get-master-addr-by-name |
| 0620000a | Sentinel-1: get-master-addr-by-name |
| 0620000b | Sentinel-2: get-master-addr-by-name |
| 0620000c | DB-0: role |
| 0620000d | DB-1: role |
| 0620000e | DB-2: role |
| 0620000f | No DB Pod is active |
| 06200010 | Got active DB Pods |
| 06200011 | Checking master status for DB pod $db_host-$i.$db_host.{{ .Release.Namespace }}.svc.cluster.local |
| 06200012 | Role master check, got DB-$i as non-master/non-active |
| 06200013 | Role master check, got DB-$i as master |
| 06200014 | Role slave check, got DB-$i as master |
| 06200015 | Role slave check, got DB-$i as slave, master_host: $role_slave_svcname |
| 06200016 | get_master_db invoked |
| 06200017 | Contents of $sentinel_gm_op: |
| 06200018 | Got master_db_addr: $master_db_addr |
| 06200019 | Empty master_db_addr |
| 0620001a | Got master_db_svcname: $master_db_svcname from redis |
| 0620001b | Got Master DB POD is ctive |
| 0620001c | Non Empty master_db_addr |
| 0620001d | Contents of $sentinel_master_status: |
| 0620001e | Empty master_status, setting it to DOWN to continue wait... |
| 0620001f | Checking if the db pod '$master_db_svcname' is master |
| 06200020 | the db pod '$master_db_svcname' is non-master/non-active, setting master_status to DOWN |
| 06200021 | the master db pod '$master_db_svcname' is active, breaking loop |
| 06200022 | Incremented value for master_status_down_count: $master_status_down_count |
| 06200023 | master_status_down_count exceeded threshold |
| 06200024 | There is no other master pod running.. |
| 06200025 | Forcibly making current pod '$HOSTNAME' as master, breaking loop |
| 06200026 | Unable to get master, breaking loop |
| 06200027 | Forcibly Continuing with $master_db_svcname as master db, breaking loop |
| 06200028 | Master db svc name: $master_db_svcname, status: $master_db_svcstatus, HOSTNAME: $HOSTNAME, db_host: $db_host |
| 06200029 | Hostname matched with master db service name, breaking loop |
| 0620002a | Host is different from the master DB, continuing |
| 0620002b | masterdb addr: $master_db_addr |
| 0620002c | masterdb svcname: $master_db_svcname |
| 0620002d | start_sentinel invoked, arg1: $1 |
| 0620002e | start_redis invoked, arg1: $1 |
| 0620002f | Replica of $1 |
| 06200030 | redis_pod_bootup invoked |
| 06200031 | Empty master_db_svcname, Hostname: $HOSTNAME |
| 06200032 | Going to start the first db pod |
| 06200033 | NonEmpty master_db_svcname: $master_db_svcname, $HOSTNAME.$db_host.{{ .Release.Namespace }}.svc.cluster.local |
| 06200034 | Hostname matched with master db service name, starting pod as Master |
| 06200035 | Hostname didn't match master_db_svcname, starting pod as Replica |
| 06200036 | $aof_instance is corrupted |
| 06200037 | $aof_instance is not corrupted |
| 06200038 | Will check again |
| 06200039 | sentinel_pod_bootup invoked |
| 0620003a | Got master_db_svcname: $master_db_svcname |
| 0620003b | Got empty master_db_svcname |
| 0620003c | Going to start the first sentinel pod |
| 0620003d | Going to start other sentinel pods |
| 0620003e | Will check again |
| 0620003f | calling probe |
| 06200040 | IS_DB_POD is true: $IS_DB_POD, calling redis_pod_bootup() |
| 06200041 | delaying the redis process by $redis_startup_delay seconds to hit failover in case of restart |
| 06200042 | IS_SENTINEL_POD is true: $IS_SENTINEL_POD, calling sentinel_pod_bootup() |
Log Message Details
06200000 : Started log level watcher (PID: $LOGLEVEL_WATCHER_PID) monitoring $LOGLEVEL_FILE
sev:
Info
Type:
Application
args:
- LOGLEVEL_FILE
- LOGLEVEL_WATCHER_PID
cause:
Log level watcher started successfully
workaround:
Verify watcher process is running if logs are not filtered correctly
06200001 : dssm:start
sev:
Info
Type:
Application
args:
N/A
cause:
DSSM initialization started
workaround:
Check pod logs if initialization fails
06200002 : This is for SPK
sev:
Info
Type:
Application
args:
N/A
cause:
SPK version of DSSM
workaround:
N/A
06200003 : TLS is explicitly disabled
sev:
Info
Type:
Application
args:
N/A
cause:
TLS disabled via configuration
workaround:
Enable TLS for production environments
06200004 : TLS is enabled (default)
sev:
Info
Type:
Application
args:
N/A
cause:
TLS enabled with certificate paths configured
workaround:
N/A
06200005 : db_tlscert_string = $db_tlscert_string
sev:
Debug
Type:
Application
args:
- db_tlscert_string
cause:
Database TLS certificate configuration
workaround:
N/A
06200006 : sentinel_tlscert_string = $sentinel_tlscert_string
sev:
Debug
Type:
Application
args:
- sentinel_tlscert_string
cause:
Sentinel TLS certificate configuration
workaround:
N/A
06200007 : tlscert_string = $tlscert_string
sev:
Debug
Type:
Application
args:
- tlscert_string
cause:
TLS certificate string selected based on pod type
workaround:
N/A
06200008 : Logging POD details for $HOSTNAME...
sev:
Debug
Type:
Application
args:
- HOSTNAME
cause:
redis-cli binary and logs all associated state information
workaround:
N/A
06200009 : Sentinel-0: get-master-addr-by-name
sev:
Debug
Type:
Application
args:
N/A
cause:
Querying Sentinel-0 for master address
workaround:
N/A
0620000a : Sentinel-1: get-master-addr-by-name
sev:
Debug
Type:
Application
args:
N/A
cause:
Querying Sentinel-1 for master address
workaround:
N/A
0620000b : Sentinel-2: get-master-addr-by-name
sev:
Debug
Type:
Application
args:
N/A
cause:
Querying Sentinel-2 for master address
workaround:
N/A
0620000c : DB-0: role
sev:
Debug
Type:
Application
args:
N/A
cause:
Querying DB-0 for role status
workaround:
N/A
0620000d : DB-1: role
sev:
Debug
Type:
Application
args:
N/A
cause:
Querying DB-1 for role status
workaround:
N/A
0620000e : DB-2: role
sev:
Debug
Type:
Application
args:
N/A
cause:
Querying DB-2 for role status
workaround:
N/A
0620000f : No DB Pod is active
sev:
Warning
Type:
Application
args:
N/A
cause:
Redis service did not respond with PONG
workaround:
Check if DB pods are running and network connectivity is working
06200010 : Got active DB Pods
sev:
Info
Type:
Application
args:
N/A
cause:
At least one DB pod responded to ping
workaround:
N/A
06200011 : Checking master status for DB pod $db_host-$i.$db_host.{{ .Release.Namespace }}.svc.cluster.local
sev:
Debug
Type:
Application
args:
- db_host
- i
cause:
Checking master role for DB pod instance
workaround:
N/A
06200012 : Role master check, got DB-$i as non-master/non-active
sev:
Debug
Type:
Application
args:
- i
cause:
DB pod is not configured as master
workaround:
N/A
06200013 : Role master check, got DB-$i as master
sev:
Info
Type:
Application
args:
- i
cause:
DB pod confirmed as master
workaround:
N/A
06200014 : Role slave check, got DB-$i as master
sev:
Debug
Type:
Application
args:
- i
cause:
DB pod is not configured as slave
workaround:
N/A
06200015 : Role slave check, got DB-$i as slave, master_host: $role_slave_svcname
sev:
Info
Type:
Application
args:
- i
- role_slave_svcname
cause:
DB pod is slave, extracting master host information
workaround:
N/A
06200016 : get_master_db invoked
sev:
Debug
Type:
Application
args:
N/A
cause:
Starting master DB discovery process
workaround:
N/A
06200017 : Contents of $sentinel_gm_op:
sev:
Debug
Type:
Application
args:
- sentinel_gm_op
cause:
Sentinel query response captured
workaround:
N/A
06200018 : Got master_db_addr: $master_db_addr
sev:
Debug
Type:
Application
args:
- master_db_addr
cause:
Master database address extracted from sentinel
workaround:
N/A
06200019 : Empty master_db_addr
sev:
Warning
Type:
Application
args:
N/A
cause:
Sentinel did not return master address
workaround:
Check sentinel pod status and connectivity
0620001a : Got master_db_svcname: $master_db_svcname from redis
sev:
Debug
Type:
Application
args:
- master_db_svcname
cause:
Retrieved master service name from DB pods
workaround:
N/A
0620001b : Got Master DB POD is ctive
sev:
Info
Type:
Application
args:
N/A
cause:
Master DB pod is active and reachable
workaround:
N/A
0620001c : Non Empty master_db_addr
sev:
Debug
Type:
Application
args:
N/A
cause:
Master address obtained from sentinel
workaround:
N/A
0620001d : Contents of $sentinel_master_status:
sev:
Debug
Type:
Application
args:
- sentinel_master_status
cause:
Sentinel master status response
workaround:
N/A
0620001e : Empty master_status, setting it to DOWN to continue wait...
sev:
Warning
Type:
Application
args:
N/A
cause:
Sentinel query timed out or DNS resolution failed
workaround:
Check network connectivity and DNS configuration
0620001f : Checking if the db pod '$master_db_svcname' is master
sev:
Debug
Type:
Application
args:
- master_db_svcname
cause:
Verifying DB pod has master role
workaround:
N/A
06200020 : the db pod '$master_db_svcname' is non-master/non-active, setting master_status to DOWN
sev:
Warning
Type:
Application
args:
- master_db_svcname
cause:
DB pod does not have master role despite sentinel claim
workaround:
Wait for sentinel to detect correct master or trigger manual failover
06200021 : the master db pod '$master_db_svcname' is active, breaking loop
sev:
Info
Type:
Application
args:
- master_db_svcname
cause:
Master DB pod verified and active
workaround:
N/A
06200022 : Incremented value for master_status_down_count: $master_status_down_count
sev:
Debug
Type:
Application
args:
- master_status_down_count
cause:
Master status down count incremented
workaround:
N/A
06200023 : master_status_down_count exceeded threshold
sev:
Warning
Type:
Application
args:
N/A
cause:
Master has been down for extended period exceeding threshold
workaround:
Consider manual intervention or check for cluster split-brain scenario
06200024 : There is no other master pod running..
sev:
Warning
Type:
Application
args:
N/A
cause:
No master pod detected in cluster
workaround:
Verify all DB pods are running and check sentinel configuration
06200025 : Forcibly making current pod '$HOSTNAME' as master, breaking loop
sev:
Warning
Type:
Application
args:
- HOSTNAME
cause:
Forcing current DB pod to become master due to no viable master
workaround:
Review cluster state after this forced promotion
06200026 : Unable to get master, breaking loop
sev:
Error
Type:
Application
args:
N/A
cause:
Sentinel pod cannot determine master
workaround:
Check DB pod status and sentinel configuration
06200027 : Forcibly Continuing with $master_db_svcname as master db, breaking loop
sev:
Warning
Type:
Application
args:
- master_db_svcname
cause:
Using detected master despite sentinel disagreement
workaround:
Monitor for split-brain or inconsistent cluster state
06200028 : Master db svc name: $master_db_svcname, status: $master_db_svcstatus, HOSTNAME: $HOSTNAME, db_host: $db_host
sev:
Info
Type:
Application
args:
- HOSTNAME
- db_host
- master_db_svcname
- master_db_svcstatus
cause:
Master db svc name: $master_db_svcname, status: $master_db_svcstatus, HOSTNAME: $HOSTNAME, db_host: $db_host
workaround:
N/A
06200029 : Hostname matched with master db service name, breaking loop
sev:
Info
Type:
Application
args:
N/A
cause:
Hostname matched with master db service name, breaking loop
workaround:
N/A
0620002a : Host is different from the master DB, continuing
sev:
Info
Type:
Application
args:
N/A
cause:
Host is different from the master DB, continuing
workaround:
N/A
0620002b : masterdb addr: $master_db_addr
sev:
Info
Type:
Application
args:
- master_db_addr
cause:
Final master database address determined
workaround:
N/A
0620002c : masterdb svcname: $master_db_svcname
sev:
Info
Type:
Application
args:
- master_db_svcname
cause:
Final master database service name determined
workaround:
N/A
0620002d : start_sentinel invoked, arg1: $1
sev:
Info
Type:
Application
args:
N/A
cause:
Starting sentinel service with master configuration
workaround:
N/A
0620002e : start_redis invoked, arg1: $1
sev:
Info
Type:
Application
args:
N/A
cause:
Starting Redis database service
workaround:
N/A
0620002f : Replica of $1
sev:
Info
Type:
Application
args:
N/A
cause:
Redis configured as replica of specified master
workaround:
N/A
06200030 : redis_pod_bootup invoked
sev:
Info
Type:
Application
args:
N/A
cause:
Initiating Redis pod bootup sequence
workaround:
N/A
06200031 : Empty master_db_svcname, Hostname: $HOSTNAME
sev:
Info
Type:
Application
args:
- HOSTNAME
cause:
Start this pod as master pod
workaround:
N/A
06200032 : Going to start the first db pod
sev:
Info
Type:
Application
args:
N/A
cause:
Starting first DB pod as initial master
workaround:
N/A
06200033 : NonEmpty master_db_svcname: $master_db_svcname, $HOSTNAME.$db_host.{{ .Release.Namespace }}.svc.cluster.local
sev:
Info
Type:
Application
args:
- HOSTNAME
- db_host
- master_db_svcname
cause:
Master database service identified in cluster
workaround:
N/A
06200034 : Hostname matched with master db service name, starting pod as Master
sev:
Info
Type:
Application
args:
N/A
cause:
Current pod is designated master
workaround:
N/A
06200035 : Hostname didn't match master_db_svcname, starting pod as Replica
sev:
Info
Type:
Application
args:
N/A
cause:
start the redis replica
workaround:
N/A
06200036 : $aof_instance is corrupted
sev:
Warning
Type:
Application
args:
- aof_instance
cause:
AOF file validation failed
workaround:
Attempting automatic repair, backup recommended
06200037 : $aof_instance is not corrupted
sev:
Debug
Type:
Application
args:
- aof_instance
cause:
AOF file is valid
workaround:
N/A
06200038 : Will check again
sev:
Info
Type:
Application
args:
N/A
cause:
Will check again
workaround:
N/A
06200039 : sentinel_pod_bootup invoked
sev:
Info
Type:
Application
args:
N/A
cause:
Initiating Sentinel pod bootup sequence
workaround:
N/A
0620003a : Got master_db_svcname: $master_db_svcname
sev:
Debug
Type:
Application
args:
- master_db_svcname
cause:
Master database service name retrieved
workaround:
N/A
0620003b : Got empty master_db_svcname
sev:
Debug
Type:
Application
args:
N/A
cause:
No master database service found
workaround:
N/A
0620003c : Going to start the first sentinel pod
sev:
Info
Type:
Application
args:
N/A
cause:
Starting first sentinel pod with default DB-0 as master
workaround:
N/A
0620003d : Going to start other sentinel pods
sev:
Info
Type:
Application
args:
N/A
cause:
start another sentinel
workaround:
N/A
0620003e : Will check again
sev:
Info
Type:
Application
args:
N/A
cause:
Will check again
workaround:
N/A
0620003f : calling probe
sev:
Debug
Type:
Application
args:
N/A
cause:
Starting probe process for DB pod
workaround:
N/A
06200040 : IS_DB_POD is true: $IS_DB_POD, calling redis_pod_bootup()
sev:
Info
Type:
Application
args:
- IS_DB_POD
cause:
DB pod detected, initiating bootup process
workaround:
N/A