Welcome to the Linux Foundation Forum!

Lab 3 - CouchDB connection refused

Hi,

within Lab 3 I finally managed to make peer0 with it's CouchDB instance working after using image 1.4.4 for the peer. I did the same for peer1 but it has problems connecting to the CouchDB instance.

These are the logs of peer1.org1.example.com:

  1. 2020-01-10 11:26:41.671 UTC [nodeCmd] serve -> INFO 001 Starting peer:
  2. Version: 1.4.4
  3. Commit SHA: 7917a40
  4. Go version: go1.12.12
  5. OS/Arch: linux/amd64
  6. Chaincode:
  7. Base Image Version: 0.4.18
  8. Base Docker Namespace: hyperledger
  9. Base Docker Label: org.hyperledger.fabric
  10. Docker Namespace: hyperledger
  11. 2020-01-10 11:26:41.672 UTC [ledgermgmt] initialize -> INFO 002 Initializing ledger mgmt
  12. 2020-01-10 11:26:41.672 UTC [kvledger] NewProvider -> INFO 003 Initializing ledger provider
  13. 2020-01-10 11:26:41.734 UTC [kvledger] NewProvider -> INFO 004 ledger provider Initialized
  14. 2020-01-10 11:26:41.819 UTC [couchdb] handleRequest -> WARN 005 Retrying couchdb request in 125ms. Attempt:1 Error:Get http://127.0.0.1:5984/: dial tcp 127.0.0.1:5984: connect: connection refused
  15. 2020-01-10 11:26:41.945 UTC [couchdb] handleRequest -> WARN 006 Retrying couchdb request in 250ms. Attempt:2 Error:Get http://127.0.0.1:5984/: dial tcp 127.0.0.1:5984: connect: connection refused
  16. 2020-01-10 11:26:42.196 UTC [couchdb] handleRequest -> WARN 007 Retrying couchdb request in 500ms. Attempt:3 Error:Get http://127.0.0.1:5984/: dial tcp 127.0.0.1:5984: connect: connection refused
  17. 2020-01-10 11:26:42.697 UTC [couchdb] handleRequest -> WARN 008 Retrying couchdb request in 1s. Attempt:4 Error:Get http://127.0.0.1:5984/: dial tcp 127.0.0.1:5984: connect: connection refused
  18. 2020-01-10 11:26:43.698 UTC [couchdb] handleRequest -> WARN 009 Retrying couchdb request in 2s. Attempt:5 Error:Get http://127.0.0.1:5984/: dial tcp 127.0.0.1:5984: connect: connection refused
  19. 2020-01-10 11:26:45.699 UTC [couchdb] handleRequest -> WARN 00a Retrying couchdb request in 4s. Attempt:6 Error:Get http://127.0.0.1:5984/: dial tcp 127.0.0.1:5984: connect: connection refused

Here is a small part of the couchdbOrg1Peer1 logs:

  1. [error] 2020-01-10T11:26:40.560152Z nonode@nohost emulator -------- Error in process <0.341.0> with exit value:
  2. {database_does_not_exist,[{mem3_shards,load_shards_from_db,"_users",[{file,"src/mem3_shards.erl"},{line,395}]},{mem3_shards,load_shards_from_disk,1,[{file,"src/mem3_shards.erl"},{line,370}]},{mem3_shards,load_shards_from_disk,2,[{file,"src/mem3_shards.erl"},{line,399}]},{mem3_shards,for_docid,3,[{file,"src/mem3_shards.erl"},{line,86}]},{fabric_doc_open,go,3,[{file,"src/fabric_doc_open.erl"},{line,39}]},{chttpd_auth_cache,ensure_auth_ddoc_exists,2,[{file,"src/chttpd_auth_cache.erl"},{line,195}]},{chttpd_auth_cache,listen_for_changes,1,[{file,"src/chttpd_auth_cache.erl"},{line,142}]}]}

There is a bit more of usual configuration logs in the first place and then these errors again and again.

I am not quite sure why this only appears for the second peer and not for the first.

Can anyone please help me or give any suggestions?

Kind regards,
Marvin

Comments

  • Nevermind. I found a typo in my docker-compose.yaml. Is there a way to delete a discussion? :sweat_smile:

  • @marvint said:
    Nevermind. I found a typo in my docker-compose.yaml. Is there a way to delete a discussion? :sweat_smile:

    Hi Marvint, great that the issue was resolved. Typos in the .yaml files are always a difficult to spot.

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Categories

Upcoming Training