Обсуждение: server.crt Missing

I’m getting repetitive errors/warnings:

2021-06-28 08:57:07.127 EDT [44717] FATAL:  could not load server certificate file "server.crt": No such file or
directory
2021-06-28 08:57:07.127 EDT [44717] LOG:  database system is shut down

This is my workstation, so I don’t have a certificate for this.  Is there a way I can get this to not be reported?
I’vechecked nginx.conf and there’s nothing in there that shows me that I can turn this off.   

Any insight appreciated.

Cheers, Bee

On Mon, 28 Jun 2021 09:04:13 -0400
BeeRich Lists <bee.lists@gmail.com> wrote:

> I’m getting repetitive errors/warnings:
>
> 2021-06-28 08:57:07.127 EDT [44717] FATAL:  could not load server
> certificate file "server.crt": No such file or directory 2021-06-28
> 08:57:07.127 EDT [44717] LOG:  database system is shut down

IIRC, by default, Pg starts with SSL activated - so, IF you need it, you
MUST give it's primitives the right path & files (ssl_cert_file,
ssl_key_file, ssl_crl_file, etc, into the 'postgresql.conf' file) or if
you do not need it and the machine is trusted (ie: nginx is reaching
your PG DB on localhost AND this will not change for a looong time)
either uncomment the :
    #ssl = off
line to stop SSL.

HINT: Leave /etc/postgresql/<VER_NUM>/main/postgresql.conf alone, copy
    it into /etc/postgresql/<VER_NUM>/main/conf.d/ and work only on
    this one. As this file will be read as the last one, it will
    supersede any primitive of the original file.
    You can also cut it in pieces if it is easier for you.

Jean-Yves

On Mon, 2021-06-28 at 09:04 -0400, BeeRich Lists wrote:
> I’m getting repetitive errors/warnings:
> 
> 2021-06-28 08:57:07.127 EDT [44717] FATAL:  could not load server certificate file "server.crt": No such file or
directory
> 2021-06-28 08:57:07.127 EDT [44717] LOG:  database system is shut down
> 
> This is my workstation, so I don’t have a certificate for this.  Is there a way I can get this to not be reported?
I’vechecked nginx.conf and there’s nothing in there that shows me that I can turn
 
> this off.  
> 
> Any insight appreciated.

If you want transport encryption with TLS, you have to provide a server key and certificate.

If you don't need that, set "ssl = off", then PostgreSQL won't complain.

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com