This article covers the key initial information that EDB Technical Support needs for each Product, saving time so that the issue can be diagnosed and resolved faster.
According to the Product, please attach it to the new ticket:
- Lasso report.
- Database logs.
- Lasso report.
- Output of the backup command.
- Exact command used.
- Lasso report from all nodes.
- Database logs from all nodes.
- Barman Lasso report.
- Barman logs.
-
pgbackrest.conf
file. - PgBackRest logs.
- Lasso report from all nodes.
- EFM logs from all nodes.
- Database logs from all nodes.
- Lasso report from all nodes.
- Repmgr logs from all nodes.
- Database logs from all nodes.
- Patroni logs from all nodes.
- Database logs from all nodes.
- Patroni cluster status - Output of
patronictl -c /etc/patroni/patroni.yaml list <clustername>
. - Patroni configuration - Output of
patronictl -c /etc/patroni/patroni.yaml show-config <clustername>
. - If the issue is related to an abnormal/unexpected failover or switchover - Output of
patronictl -c /etc/patroni/patroni.yaml history <cluster-name>
.
- Lasso report.
- PGBouncer logs.
- Lasso report from the database backend.
- Database logs from the database backend.
- PgPool logs.
-
pgpool.conf
file. - Output of
SHOW POOL_POOLS
. - Lasso report from the database backend.
- Database logs from the database backend.
- Lasso from all xDB data nodes.
- Lasso from all xDB service nodes.
- MTK logs.
- If there is a connection error,
toolkit.properties
file.
- Lasso report from the PEM server.
- Screenshot of the
Help -> About Postgres Enterprise Manager
in the PEM GUI. -
worker.log
file from the PEM server. - Database logs.
- Web browser used.
- PGAdmin logs.
- Lasso report from the database backend.
- Database logs from the database backend.
- Lasso report from all nodes.
- Database logs from all nodes.
- Lasso report from all nodes.
- Database logs from all nodes.
- Lasso report from all nodes.
- Database logs from all nodes.
- OS logs from all nodes.
- LiveCompare
.ini
file. - LiveCompare session logs.
-
config.yml
file. - All
*.yml
files from the<cluster_dir>/hooks/
directory. -
ansible.log
file. - Output of
tpaexec info
.
The output of the following commands:
-
kubectl get events -n <namespace>
. -
kubectl logs cluster <Cluster_name> -n <namespace>
. -
kubectl logs pod <POD_1_NAME> -n <namespace>
. -
kubectl logs pod <POD_2_NAME> -n <namespace>
. -
kubectl get pvc -n <namespace>
. -
kubectl describe pvc <node_1_name>
. -
kubectl describe pvc <node_2_name>
.