PowerFlex: NO_MASTER_POSTGRES_POD PFX00001.0704001-02-03-04
Resumen: This article explains how to troubleshoot events PFX00001.0704001 PFX00001.0704002 PFX00001.0704003 PFX00001.0704004
Instrucciones
Alerts PFX00001.0704XXX are monitoring alerts that can be triggered while postgres pods are still trying to recover from a previous action
Recommend Action:
- Wait 10-15 minutes for the database cluster to recover. Pod should auto recover
- PowerFlex 4.X: How to Perform a Graceful Reboot on PFMP MVM Management VMs
|
Code |
Name |
Description |
Severity |
System impact |
Repair flow |
SNMP code |
SCG symptom ID |
|
70401011 |
|
No Master postgres pod in cluster! |
CRITICAL |
No primary database instance detected. The UI and most API endpoints will not be functional. |
Wait 10-15 minutes for the database cluster to recover. Pod should auto recover |
|
|
|
70401010 |
|
Postgres instance {{instanceNa me}} has the role of {{replicaRole} } which is invalid. |
MAJOR |
A database instance is reporting an invalid role and may not be replicating data correctly. |
Wait 10-15 minutes for the database cluster to recover. Pod should auto recover |
|
|
|
70401012 |
|
Postgres instance {{instanceNa me}} is in critical lag state. |
CRITICAL |
A database instance is reporting critical lag and is not replicating data correctly. |
Wait 10-15 minutes for the database cluster to recover. Pod should auto recover |
|
|
|
70401008 |
|
Postgres instance {{instanceNa me}} is not in Running state. {{instanceNa me}} is {{state}}. |
MINOR |
A database instance is not running. |
Wait 10-15 minutes for the database cluster to recover. Pod should auto recover |
|
|