Thread: BUG #16537: could not connect to database although database is running

The following bug has been logged on the website:

Bug reference:      16537
Logged by:          William Frezno
Email address:      for.ggame.playing@gmail.com
PostgreSQL version: 12.3
Operating system:   Parrot GNU/Linux 4.10
Description:

here is /var/log/postgresql/postgresql-12-main.log
2020-07-13 18:07:02.049 UTC [1092] FATAL:  could not load server certificate
file "/etc/ssl/certs/ssl-cert-snakeoil.pem": No such file or directory
2020-07-13 18:07:02.050 UTC [1092] LOG:  database system is shut down
pg_ctl: could not start server
Examine the log output.
 #systemctl status postgresql
● postgresql.service - PostgreSQL RDBMS
     Loaded: loaded (/lib/systemd/system/postgresql.service; disabled;
vendor p>
     Active: active (exited) since Mon 2020-07-13 22:07:02 +04; 1h 19min
ago
    Process: 1095 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
   Main PID: 1095 (code=exited, status=0/SUCCESS)

July 13 22:07:02 computer systemd[1]: Starting PostgreSQL RDBMS...
July 13 22:07:02 computer systemd[1]: Finished PostgreSQL RDBMS.

#psql
psql: error: could not connect to server: could not connect to server: No
such file or directory
    Is the server running locally and accepting
    connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?

And I see port 5432 enabled on /etc/postgresql/12/main/postgresql.conf
port = 5432                             # (change requires restart)
max_connections = 100                   # (change requires restart)

What's wrong with postgresql server?

PG Bug reporting form <noreply@postgresql.org> writes:
> here is /var/log/postgresql/postgresql-12-main.log
> 2020-07-13 18:07:02.049 UTC [1092] FATAL:  could not load server certificate
> file "/etc/ssl/certs/ssl-cert-snakeoil.pem": No such file or directory

> What's wrong with postgresql server?

That error message seems reasonably clear from here.
Evidently your postgresql.conf file contains

ssl_cert_file = '/etc/ssl/certs/ssl-cert-snakeoil.pem'

but there isn't actually any such file on your machine.

How you got into this misconfiguration is harder to guess,
especially if this server used to work.  I think it's
normal for Debian-derived systems to have a file like that,
but I have no idea if Parrot is a Debian clone or not.

Anyway, the quickest route to a fix might be to set ssl = off
in postgresql.conf.  If you do want SSL support, you need to
install a valid certificate file and point ssl_cert_file at it.

Personally I wouldn't use ssl-cert-snakeoil.pem even if I had it;
better to generate your own cert.  See

https://www.postgresql.org/docs/current/ssl-tcp.html

            regards, tom lane