From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Marco Ippolito <ippolito(dot)marco(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: "Failed to connect to Postgres database" |
Date: | 2019-09-27 19:52:39 |
Message-ID: | 59045d2d-d014-12b4-10ec-1dd5aae8436a@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 9/27/19 11:19 AM, Marco Ippolito wrote:
> Sorry again,
> I was cheering up too quickly.
> With this configuration in fabric-ca-server-config.yaml :
> db:
> type: postgres
> datasource: host=localhost port=5433 user=postgres password=1234
> dbname=fabmnet_ca sslmode=disable
> tls:
> enabled: false
> certfiles:
> client:
> certfile:
> keyfile:
>
> the output of starting fabric-ca-server at first glance seems ok:
>
> 2019/09/27 20:11:44 [INFO] Operation Server Listening on 127.0.0.1:9443
> <http://127.0.0.1:9443>
> 2019/09/27 20:11:44 [INFO] Listening on http://0.0.0.0:7054
So the server is up and running.
>
> but the /var/log/postgresql/postgresql-11-fabmnet.log gives us a
> different, not so bright, perspective:
>
> What do these continuous attempts to duplicate key value mean? It
> doesn't look so good this fabric-ca-server connection with postgresql-11
> 's db ...
Looks to me like the fabric server is trying reinitialize the database
again with values that already exist. I do not pretend to know what the
fabric-ca server is up to. You might have better luck with that part of
it here:
https://lists.hyperledger.org/g/main
>
> Marco
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | PegoraroF10 | 2019-09-27 21:43:04 | steps of a sql |
Previous Message | Adrian Klaver | 2019-09-27 19:39:51 | Re: "Failed to connect to Postgres database" |