| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | for(dot)ggame(dot)playing(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #16537: could not connect to database although database is running |
| Date: | 2020-07-13 19:50:17 |
| Message-ID: | CAKFQuwbN1i4OxjdZ4fHL5XncutjPLpQN6J7yTYNxvr_sfskfYA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Jul 13, 2020 at 12:46 PM PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 16537
> Logged by: William Frezno
> Email address: for(dot)ggame(dot)playing(at)gmail(dot)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
>
> [...]
> What's wrong with postgresql server?
>
The log message you supplied seems self-explanatory...
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-07-13 20:01:26 | Re: BUG #16537: could not connect to database although database is running |
| Previous Message | PG Bug reporting form | 2020-07-13 19:29:02 | BUG #16537: could not connect to database although database is running |