From fd8b4e378b99b93338b8c0e0b202c2ab9714378b Mon Sep 17 00:00:00 2001
From: Suseela S <suseela@openg2p.org>
Date: Fri, 2 Aug 2024 16:08:45 +0000
Subject: [PATCH] GITBOOK-940: Pramod's Aug 2 changes

---
 SUMMARY.md                            | 1 +
 deployment/troubleshooting-section.md | 7 +++++++
 2 files changed, 8 insertions(+)
 create mode 100644 deployment/troubleshooting-section.md

diff --git a/SUMMARY.md b/SUMMARY.md
index 55b8eb21..4b20ad59 100644
--- a/SUMMARY.md
+++ b/SUMMARY.md
@@ -432,6 +432,7 @@
     * [Debezium](deployment/common-components/debezium.md)
     * [Keymanager](deployment/common-components/keymanager.md)
     * [eSignet](deployment/common-components/esignet.md)
+  * [Troubleshooting Section](deployment/troubleshooting-section.md)
 * [Use Cases](use-cases/README.md)
   * [Technology for Inclusion](use-cases/technology-for-inclusion/README.md)
     * [Registration in Low Connectivity Areas](use-cases/technology-for-inclusion/registration-in-low-connectivity-areas.md)
diff --git a/deployment/troubleshooting-section.md b/deployment/troubleshooting-section.md
new file mode 100644
index 00000000..fdfb7080
--- /dev/null
+++ b/deployment/troubleshooting-section.md
@@ -0,0 +1,7 @@
+---
+description: This guide gives you solutions for the issues faced in the environment.
+---
+
+# Troubleshooting Section
+
+<table><thead><tr><th width="106">Issue ID</th><th width="201">Issue Description	</th><th width="235">Root Cause</th><th>Solution</th></tr></thead><tbody><tr><td>001</td><td>Sometimes PostgreSQL databases might fail due to this error.<br><code>could not write lock file "postmaster.pid": No space left on the device</code> </td><td>This is due to <code>Disk space full on NFS node</code> or <code>PVC is full.</code></td><td>Login to the NFS node and clear the logs using below commands to clear the storage.<br>*<strong>sudo rm -f /var/log/</strong><em><strong>.gz /var/log/</strong></em><strong>.1 /var/log/</strong><em><strong>.old</strong></em> <br><em><strong>*sudo rm -f /var/log/</strong></em><strong>/</strong><em><strong>gz /var/log/</strong></em><strong>/</strong><em><strong>.1 /var/log/</strong></em><strong>/*.old</strong><br><strong>*sudo truncate -s 0 /var/log/syslog</strong></td></tr><tr><td>002</td><td><p>PostgreSQL database not starting due to replication checkpoint error.</p><p><code>PANIC: replication checkpoint has wrong magic 1865248117 instead of 307747550</code><br></p></td><td>Some times database files might corrupt and shows the error and it will fail to connect with the services.<br></td><td>Rename or take backup of this file <code>pg_logical/replorigin_checkpoint</code> from postgres PVC, and restarting postgres server will work. </td></tr></tbody></table>