Re: "Failed to connect to Postgres database"
От | Adrian Klaver |
---|---|
Тема | Re: "Failed to connect to Postgres database" |
Дата | |
Msg-id | 59045d2d-d014-12b4-10ec-1dd5aae8436a@aklaver.com обсуждение исходный текст |
Ответ на | Re: "Failed to connect to Postgres database" (Marco Ippolito <ippolito.marco@gmail.com>) |
Список | 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.klaver@aklaver.com
В списке pgsql-general по дате отправления: