hyperledger-fabric

问题 i get an error for hyperledger fabric. I followed the documentation and I came across his error when I ran the below command peer channel create -o orderer.example.com:7050 -c $CHANNEL_NAME -f ./channel-artifacts/channel.tx --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem the error being BAD_REQUEST -- error validating channel creation transaction for new channel

问题 We set up a fabric server, and put some transaction into it. And we have some applications those will cooperate with the fabric server. Here is a situation. Application send a transaction with fabric-sdk-java or fabric-sdk-node The fabric excute the chaincode The fabric notify the application about the result / The application listen to the event of the transaction (commit transaction, generate blockchain, append the blockchain, update the world state, etc.) Application notify the custom

问题 what are the steps to troubleshoot below error when trying to invoke a chaincode? Error: could not assemble transaction: ProposalResponsePayloads do not match - proposal response: version:1 response:<status:200 payload:"[\"00000\"]" > ... we get this error when trying to invoke a chaincode using peer chaincode invoke 回答1: Check that you have installed the chaincode on all the peers your peer chaincode invoke command is targetting. That is the most likely cause of this error. Other ways this

问题 npm start > server@1.0.0 start C:\Users\07\OneDrive\Desktop\Final Try\fabcar-blockchain-sample\web-app\server > ./node_modules/nodemon/bin/nodemon.js src/app.js '.' is not recognized as an internal or external command, operable program or batch file. npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! server@1.0.0 start: `./node_modules/nodemon/bin/nodemon.js src/app.js` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the server@1.0.0 start script. npm ERR! This is probably not a problem

问题 :~/Documents/test/education/LFS171x/fabric-material/tuna-app/$ node query.js Store path:/home/*******/Documents/test/education/LFS171x/fabric-material/tuna-app/hfc-key-store Successfully loaded user1 from persistence 2020-02-11T05:56:10.423Z - error: [Remote.js]: Error: Failed to connect before the deadline URL:grpc://localhost:7051 Query has completed, checking results error from query = Error: Failed to connect before the deadline URL:grpc://localhost:7051 at checkState (/home/******

问题 :~/Documents/test/education/LFS171x/fabric-material/tuna-app/$ node query.js Store path:/home/*******/Documents/test/education/LFS171x/fabric-material/tuna-app/hfc-key-store Successfully loaded user1 from persistence 2020-02-11T05:56:10.423Z - error: [Remote.js]: Error: Failed to connect before the deadline URL:grpc://localhost:7051 Query has completed, checking results error from query = Error: Failed to connect before the deadline URL:grpc://localhost:7051 at checkState (/home/******

问题 I am trying to run the byfn network in Hyperledger Fabric for version 1.4. I have started the containers, the crypto materials are setup, configuration is setup and the channel is created. However when it comes to the peer joining step i get the following error + peer channel join -b mychannel.block + res=1 + set +x 2020-02-12 07:53:23.356 UTC [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2020-02-12 07:53:23.395

问题 I am trying to run the byfn network in Hyperledger Fabric for version 1.4. I have started the containers, the crypto materials are setup, configuration is setup and the channel is created. However when it comes to the peer joining step i get the following error + peer channel join -b mychannel.block + res=1 + set +x 2020-02-12 07:53:23.356 UTC [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2020-02-12 07:53:23.395

问题 I am trying to run the byfn network in Hyperledger Fabric for version 1.4. I have started the containers, the crypto materials are setup, configuration is setup and the channel is created. However when it comes to the peer joining step i get the following error + peer channel join -b mychannel.block + res=1 + set +x 2020-02-12 07:53:23.356 UTC [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2020-02-12 07:53:23.395

问题 I use composer deployed to the fabric network with five peers. Today when i try to update the fabric chaincode with composer bna file. but one peer return error: Error: Peer localhost:13051 has rejected transaction '39ae7b9cf735ca56a7b9a20c60745206d94852a0a4f73d14cd6fd8813ef57566' with code MVCC_READ_CONFLICT althrough the new dev* chaincode docker of this peer is generated an up. but,all the transaction will return: EXPIRED CHAINCODE so i check this peer's log, found it still use the older