Open bh4rtp2023 opened 12 months ago
If you're able to successfully connect to CouchDB using the curl
command with the provided credentials and URL (http://admin:adminpw@couchdb0:5984/
), then it indicates that CouchDB is reachable and the credentials are correct.
Given this information, it's possible that the issue lies within the Hyperledger Fabric setup or configuration
Ensure that your Hyperledger Fabric configuration is correctly pointing to the CouchDB instance. This includes the settings in your core.yaml
or related configuration files. Double-check the host, port, credentials, and database names.
Sometimes, containers might have cached configurations that are causing issues. Try stopping and removing the existing Hyperledger Fabric containers, and then recreate them. This can help ensure that the containers start with fresh configurations.
you can use this code snippet:
docker stop
Description
I am using fabric-2.5.3 on SUSE Linux Enterprise Server. Couchdb keeps printing
[notice] 2023-07-12T01:57:58.129825Z nonode@nohost <0.829.0> -------- chttpd_auth_cache changes listener died because the _users database does not exist. Create the database to silence this notice. [error] 2023-07-12T01:57:58.130301Z nonode@nohost emulator -------- Error in process <0.3577.0> with exit value: {database_does_not_exist,[{mem3_shards,load_shards_from_db,"_users",[{file,"src/mem3_shards.erl"},{line,430}]},{mem3_shards,load_shards_from_disk,1,[{file,"src/mem3_shards.erl"},{line,405}]},{mem3_shards,load_shards_from_disk,2,[{file,"src/mem3_shards.erl"},{line,434}]},{mem3_shards,for_docid,3,[{file,"src/mem3_shards.erl"},{line,100}]},{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,214}]},{chttpd_auth_cache,listen_for_changes,1,[{file,"src/chttpd_auth_cache.erl"},{line,160}]}]}
To avoid _users not created error, I set
[couchdb] single_node=true
in my local.ini to turn on single node setup and make couchdb create _users, _replicator and _global_changes itself. This time couchdb will not tell any error as above. But peer will panic with following logs:However, I test connect couchdb0 with command:
$ curl http://admin:adminpw@couchdb0:5984/
It does work.Steps to reproduce
No response