Created
September 3, 2021 11:01
-
-
Save ZulianTiger/45ff5e7eb63f801e95f2bd878c8d3e12 to your computer and use it in GitHub Desktop.
ubuntu-postgres-diagnostics
This file contains hidden or 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
Certify that postgresql service is running, using sudo service postgresql start | |
Run pg_lsclusters from your terminal | |
Check what is the cluster you are running, the output should be something like: | |
Version - Cluster Port Status Owner Data directory | |
9.6 ------- main -- 5432 online postgres /var/lib/postgresql/9.6/main | |
Disregard the '---' signs, as they are being used there only for alignment. The important information are the version and the cluster. You can also check whether the server is running or not in the status column. | |
Copy the info from the version and the cluster, and use like so: pg_ctlcluster <version> <cluster> start, so in my case, using version 9.6 and cluster 'main', it would be pg_ctlcluster 9.6 main start | |
If something is wrong, then postgresql will generate a log, that can be accessed on /var/log/postgresql/postgresql-<version>-main.log, so in my case, the full command would be sudo nano /var/log/postgresql/postgresql-9.6-main.log. | |
The output should show what is the error. | |
2017-07-13 16:53:04 BRT [32176-1] LOG: invalid authentication method "all" | |
2017-07-13 16:53:04 BRT [32176-2] CONTEXT: line 90 of configuration file "/etc/postgresql/9.5/main/pg_hba.conf" | |
2017-07-13 16:53:04 BRT [32176-3] FATAL: could not load pg_hba.conf | |
Fix the errors and restart postgresql service through sudo service postgresql restart and it should be fine. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment