fabric@lists.hyperledger.org

Home Messages Hashtags Subgroups

Tools

Collapse Topics

Exclude Signatures

Clear

Date 1 - 10 of 10

Between

and

Error While Upgrading Network (Edit Channel ACLs) #hyperledger-fabric #fabric

Hi Everyone, I was attempting to upgrade the network from 1.4.2 --> 2.0. I have completed all steps except the step where one has to Edit the Channel ACLs. The error and details are given below can an

By Faisal · #8175 ·

#hyperledger-fabric #fabric

Signature Byte Isn't Valid Warning On Gossip After Addition of a New Org #hyperledger-fabric #configtxgen #raft

Is this fixed in the 1.4.4 version LTS as we plan to upgrade the network in the coming weeks?

By Faisal · #7939 ·

#hyperledger-fabric #configtxgen #raft

Signature Byte Isn't Valid Warning On Gossip After Addition of a New Org #hyperledger-fabric #configtxgen #raft

Environment HLF (1.4.2) Orderer (RAFT 3 Node) 2 Orgs (adding 3rd Org) Running on multiple hosts (Docker Swarm Cluster) Steps Followed Configtx.yaml file contents # Copyright IBM Corp. All Rights Reser

By Faisal · #7937 ·

#hyperledger-fabric #configtxgen #raft

Error: failed to create deliver client

all the path to the file after the --cafile parameter your command should be include the tlsca.pem file export TLS_PARAMETERS = --tls true --cafile /PATH/tlsca.phone.com-cert.pem

By Faisal · #7736 ·

Peer crash due to error during block commit #fabric #couchdb

Error: Got error while committing(read tcp 10.0.9.49:37944->10.0.9.15:5984: read: connection reset by peer error reading response body We have the following environment setup and configurations for an

By Faisal · #7645 ·

#fabric #couchdb

Got Error While Committing Block Connection Reset by Peer #fabric #couchdb #network

This is the 2nd time the peer has crashed due to this error. Nework is on HLF 1.4.2 and the logs are attached in the file. Have anyone faced the same issue before or any ideas on resolving it? I have

By Faisal · #7589 ·

#fabric #couchdb #network

COULD NOT ASSEMBLE TRANSACTION, ERR PROPOSAL RESPONSE WAS NOT SUCCESSFUL, ERROR CODE 500, MSG INSTANTIATION POLICY VIOLATION: SIGNATURE SET DIDNOT SATIFY POLICY #fabric-chaincode

Yes we have tried packaging, signing and then installing on each peer. We also confirmed by listing the chaincodes on both the peers and the IDs matched. The IDs also matched in the previous case as w

By Faisal · #7190 ·

#fabric-chaincode

COULD NOT ASSEMBLE TRANSACTION, ERR PROPOSAL RESPONSE WAS NOT SUCCESSFUL, ERROR CODE 500, MSG INSTANTIATION POLICY VIOLATION: SIGNATURE SET DIDNOT SATIFY POLICY #fabric-chaincode

I can see how that is a problem when we are upgrading the chaincode (Hash might have changed due to the timestamp) but we tried installing and instantiating a chaincode with a different name first on

By Faisal · #7188 ·

#fabric-chaincode

COULD NOT ASSEMBLE TRANSACTION, ERR PROPOSAL RESPONSE WAS NOT SUCCESSFUL, ERROR CODE 500, MSG INSTANTIATION POLICY VIOLATION: SIGNATURE SET DIDNOT SATIFY POLICY #fabric-chaincode

Failure Scenario 1- Started the network with privatechannel_cc v1 chaincode installed 2- Did multiple transactions 3- Ran a script to upgrade the privatechannel_cc v2 ( GOT THE ABOVE ERROR) `COULD NOT

By Faisal · #7168 ·

#fabric-chaincode

Connecting DLT Adapter with an HSM Enabled Network #fabric-questions #hsm #fabric-ca

Hi everyone, I have created a softhsm enabled fabric network. Now that I DON'T have the admin-cert and admin-private-key in a file, how can I connect with the network from a dlt-adapter without them o

By Faisal · #6733 ·

#fabric-questions #hsm #fabric-ca

1 - 10 of 10

Home Hashtags Subgroups Terms