-
Notifications
You must be signed in to change notification settings - Fork 11
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
4b3065e
commit fd8b4e3
Showing
2 changed files
with
8 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -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> |