Oh, my bad. I had downloaded fabric samples binaries, images, etc a few months back and also downloaded a new one last week only via git clone (so I think only the sample codes changed?). That probabl

#couchdb #docker #fabric

How did you download all the components for fabric samples? Did you use the convenience script we provide? If so what parameters did you use on it. If you downloaded everything late last week, it's po

#couchdb #docker #fabric

I am trying to bring up the latest fabric-samples/test-network with this script: ./network.sh up createChannel -ca -s couchdb But I kept coming up with this error: Error: error getting endorser client

#couchdb #docker #fabric

Hello, I would like to know what is the fastest way of developing chaincode and fabric-node-sdk with fabric v2 at the same time? For now we are using `fabric-samples/test-network` but it's starting ov

#fabric #docker

Hi David, thanks for the reply, I've recreated the network and now it seems to work, I'll save save your hint for possible future problems. Mattia IFIN SISTEMI S.R.L. a socio unico Via G. Medici 9/a 3

#couchdb #docker #fabric #fabric-questions

Some additional peer logging would help to troubleshoot it: FABRIC_LOGGING_SPEC=info:statecouchdb,couchdb=debug Dave Enyeart "Mattia Bolzonella" ---06/11/2020 05:37:49 AM---Hi, i'm trying to start a p

#couchdb #docker #fabric #fabric-questions

Hi, i'm trying to start a peer but I get the error reportet in the below log dump. I can't figure out how to solve it. 2020-06-05 08:41:17.126 UTC [peer] getLocalAddress -> INFO 002 Auto-detected peer

#couchdb #docker #fabric #fabric-questions

Is there anyway to increase the wait time on a chaincode instantiation? The default seems to be about 10 minutes but I have a peer with low bandwidth and the docker image download combined with the co

#fabric #docker #fabric-chaincode #fabric-questions #hyperledger-fabric

I have installed hyperledger fabric 2.0.0. When I try to run the fabcar example, I am getting an error like this "Error: error getting endorser client for channel: endorser client failed to connect to

#fabric-questions #hyperledger-fabric #docker #fabric-chaincode #couchdb

BatchSize actually falls under the Orderer group and not the Application group. Therefore, you need a majority of the orderer admins to sign the config update. Given you state this is a simple network

#fabric #docker #fabric-ca

Hi all, I have the most simple fabric-network, and wanted to make a simple channel-config update of the batchsize (https://hyperledger-fabric.readthedocs.io/en/release-1.4/config_update.html) Everythi

#fabric #docker #fabric-ca

We are not using CLI. We are creating channel using Node SDK and creating infrastructure using shell script. We are using Raft consensus with 5 orderer and Raft cluster is working fine. Orderers elect

#fabric-sdk-node #docker #raft #consensus #cal-notice

Hi Team, While pulling the orderer image i am getting the below issue . Any idea ? Environment - Azure - Ubuntu VM - 16.04 LTS ``` Pulling orderer3 (hyperledger/fabric-orderer:1.4.3)... ERROR: Get htt

#fabric #docker