i have ubuntu 16 and hyperledger fabric 1.4.
I am have problems with the order when starting a command on the peer.
Error reading from 10.2.11.77:52640: rpc error: code = Canceled desc = context canceled
Also, have problems with the order when run chaincode through my app.
Error reading from 10.2.11.77:52640: rpc error: code = Canceled desc = context canceled
Error sending to 10.2.11.77:52640: rpc error: code = Internal desc = transport: transport: the stream is done or WriteHeader was already called
link to logs http://papajon12345.asuscomm.com/nextcloud/index.php/s/BTj4JAHmR29XSC3
Related
I am trying to implement the Raft orderer to my HLF network which is implement on aws EKS cluster(Kubernetes). I have create the 3 orderer in Raft orderer and 2 orgs which have 2 peer each which is running fine however when I trying to create the channel its give error from orderer side. as " [orderer.common.cluster.puller] func1 -> WARN 15fce Received error of type 'failed to create new connection: connection error: desc = "transport: error while dialing: dial tcp: lookup orderer2.dfarmadmin.com on 10.100.0.10:53: no such host"' from {orderer2.dfarmadmin.com:7050 " and " [orderer.consensus.etcdraft] confirmSuspicion -> ERRO 225cb Failed pulling the last config block: retry attempts exhausted channel=testchainid node=3"
I am confused how to solve it as all file and other stuff in right folder. Please see the attached screenshot of error
Please let me know what I am doing wrong also if need more information let me know.
Thanks in Advance
I am trying to perform performance testing on Hyperledger Fabric v1.2. Network is setup, using fabcar chaincode. Transactions arrival rate in 50 RPS. Using Node JS application to accept transaction requests. Transactions perform putState operation, by adding new variable in the ledger, using this code.
Consensus Used: Solo
Number of Nodes: 4 (orderer and all peers are on
different virtual machines)
Ledger: CouchDB
At lower RPS (0-20), all the transactions are successfully passing. On increasing the transaction arrival rate to 50, around 50% of total transactions fail with the error
Transaction proposal was good
Successfully sent Proposal and received ProposalResponse: Status - 200, message - ""
error: [Remote.js]: Error: Failed to connect before the deadline
error: [Orderer.js]: Orderer grpc://x.x.x.x:7050 has an error Error: Failed to connect before the deadline
error: [client-utils.js]: sendPeersProposal - Promise is rejected: Error:
Failed to connect before the deadline
What does this error mean actually? Why is the client unable to send endorsed transaction to the orderer?
And around 20% of them failed with the following error
Send transaction promise and event listener promise have completed in 30086 ms
Successfully sent transaction to the orderer.
Transaction failed to be committed to the ledger due to ::TIMEOUT
As per different research papers, Hyperledger Fabric must be able to process requests at rates as high as 2000, why is it giving such results?
I had faced the same problem by using the invoke code from fabric-samples repository. I fixed the issue by changing the order of promise chaining.
What I did was as follows:
return checkUser(this.user)
.then(() => return channel.sendTransactionProposal(request))
.then((results) => checkPrposal(results))
.then((results) => submitTrasaction(results))
.then(() => connectEventHub())
I am getting the below error while trying to deploy any nodejs based chaincode on hyperledger 1.4 network :
Error: could not assemble transaction, err proposal response was not
successful, error code 500, msg timeout expired while starting
chaincode
I have even tried the base example chaincode_example02, that is also giving the same error.
Please help.
I have created successfully a multi-org, multi-vm native (without docker) setup.
1VM = Peer1Org1
2VM = Peer1Org2
3VM = OrdererOrdererOrg
I successfully create, join the channel and install, instantiate, invoke and query an example chaincode, from both vms and all results are the same, query and invoke works fine. However, in orderer logs an error about deliver and broadcast appears.
2019-02-21 17:52:00.022 UTC [common/deliver] Handle -> WARN 01a Error reading from 192.168.50.30:34506: rpc error: code = Canceled
desc = context canceled
2019-02-21 18:21:17.899 UTC [orderer/common/broadcast] Handle -> WARN 01c Error reading from 192.168.50.30:45054: rpc error: code =
Canceled desc = context canceled.
What are these errors? And why am I getting an error even the deliver and broadcast services are seem to work (because I get the correct results)?
Peers logs have no errors. I made the certificates using Fabric CA but without TLS.
I am getting the below error when I invoke my smart contract
Error: Error endorsing invoke: rpc error: code = Unknown desc = Error
executing chaincode: Failed to execute transaction (Timeout expired while
executing transaction) - <nil>
I am able to query the chaincode and this chaincode has worked on networks with TLS but now without it Im getting the error.
We removed TLS as we were having troubles with grpc connections when making calls from the node SDK. So possibly we could hit two birds with one stone.
How to deal with this error above?
And how to deal with TLS in the node app when making GRPC calls.