Reminder: Hyperledger Fabric Documentation Workgroup call - Western hemisphere When: Friday, 19 June 2020, 4:00pm to 5:00pm, (GMT+01:00) Europe/London Where:https://zoom.us/j/6223336701 View

The second scenario failed due to: 2020-06-19 12:45:35.053 UTC [policies] SignatureSetToValidIdentities -> WARN 0ef signature for identity 0 is invalid: The signature is invalid How many peers are

For v1.4.x, there is no metric to check the set of active nodes. Usually, it's adequate to simply ensure that all OSNs are alive and have been online for a reasonable period of time to ensure that

I have attached the screenshots of the logs from Org1 peer container for your reference, for better readability. Logs when it worked: 2020-06-19 12:49:09.580 UTC [comm.grpc.server] 1 -> INFO 122

Curious about this policy, "endorsementPolicy": { "signaturePolicy": "OR('Org1MSP.member'), OR('Org2MSP.member')" } was it accepted as a valid policy? if it was accepted, should this be a bug? what

The endorsement policy check only checks which peers have endorsed, not which clients have submitted the transaction. The peer validation logic is deterministic in this regard. Could you share the

If couchdb returned an error status code while processing the index, we do log the error but chaincode upgrade would succeed irrespective of that. I would suggest to search for the term index to see

What should I search for in the peer logs? Some sort of error? Because I can't see the index on the couchdb entries

I ran the network again, to double check. The inconsistency issue still exists. The issue occurs even when I pass OR("Org1MSP.Member") as the EP and try to update the key via Org1 client (which is an

Do you have the peer logs? Regards, Senthil

the above error seems to match your old definition -- "endorsementPolicy": { "signaturePolicy": "OR('Org1MSP.member'), OR('Org2MSP.member')" } Anyway, I do not have expertise in this. If Yacov looks

Hi, I currently trying to add a new index to my 1.4 network. I have the folders correctly set too. When I update the chaincode with the new index folder I can see that my peers have the package

Sorry for typing it wrong. The endorsement policy in my collections config is as follows: "endorsementPolicy": { "signaturePolicy": "OR('Org1MSP.member', 'Org2MSP.member')" } Setting

As the memberOnlyWrite is set to false by default (not configured in the collection config as well), all peers are authorized to write if it can satisfy the endorsement policy. Is the endorsement

Wouldn't the doc https://hyperledger-fabric.readthedocs.io/en/release-2.0/operations_service.html help? Regards, Senthil

Hi all, I have a fabric 2.0 network with 2 orgs having 1 peer each (similar to test-network). I implemented a private data collection that persists in the off-chain DB of the peer of one of the orgs

Hyperledger Fabric Documentation Workgroup call - Eastern hemisphere When: Friday, 19 June 2020 6:00am to 7:00am (GMT+01:00)

Hi, Would really appreciate if anybody has any thought/suggestion regarding my query. Thanks, Shruti

Hi All, We will hold thedocumentation workgroup calls this Friday -- with both an Eastern hemisphereand Western hemisphere call. Please feel free to come along, you're alwaysvery welcome. You can

If you need to expose all features of a database, changes are needed at the database as well as peer code. if you need to plugin a database that is compatible with what currently Fabric offers, then