I made a typo, at the end of the sentence I meant peer1

#fabric #fabric-questions

Hi all. I'm working on a Fabric network (2.2.2) on docker swarm. Yesterday I updated the certificates of my organizations and everything was good except for a peer. The organization (Org2) which the p

#fabric #fabric-questions

Hi Ramesh, 1: In my situation I had all the certs expired, both admin (peer and orderers), TLS and MSP certs. 2: You need to sign with old certs in orderer tu run the update, if I recall correctly the

#fabric-questions #fabric-orderer #signcerts #fabric

Hi Ramesh, Doubt 1: If i have understood correctly, for every update I followed the usual procces for channel update which is: fetch the latest config block decode to json copy the decoded json modifi

#fabric-questions #fabric-orderer #signcerts #fabric

Hi Ramesh, I've managed to restore my production network but without adding new org. I think it's better if you first restore the network and then add the new organization (having an extra org involve

#fabric-questions #fabric-orderer #signcerts #fabric

Hi Chris, Thanks for the advice, the certs are correct. I will explain better the situation: Currently I have 2 channels, 3 orderers with the TLS certs expired. the system channel an application chann

#fabric-questions #fabric-orderer #signcerts #fabric

Hi Chris, I updated one orderer TLS certs in the system channel but it's not included in the raft consensus. If i try to fecth the channel confing block from the updated orderer i get SERVICE UNAVAILA

#fabric-questions #fabric-orderer #signcerts #fabric

Hi, I'm working on the solution proposed, now I'm using a cli peer to do my channel update operations, before doing that I set the following variables in the peer cli: CORE_PEER_LOCALMSPID=MyOrderersM

#fabric-questions #fabric-orderer #signcerts #fabric

Just to be clear about what you told me to replace in my system channel configuration, sorry but I want to be 100% sure about what I'm doing: My json looks like this: "channel_group": { "groups": { "A

#fabric-questions #fabric-orderer #signcerts #fabric

Hi Chris, Thank you again for the reply, I'm going to try what you suggested, for the replacement of the admin certs in the various sections of the config, I do that in one whole update, right? After

#fabric-questions #fabric-orderer #signcerts #fabric

Hi Chris, Thank you for the quick reply. I will illustrate my situation, it's the worst possible scenario (production environment). So I'm on Fabric 2.2.2 with all my components except Fabric CAs whic

#fabric-questions #fabric-orderer #signcerts #fabric

Hi, i need to update the orderer org admin of the system channel, it's expired but i managed to start the orderer and peer following FAB-18384. Now i need to update the channel configuration but I hav

#fabric-questions #fabric-orderer #signcerts #fabric

Hi all, I have question about adding an org to a channel. I'm not sure if the vanilla procedure for adding a new organization involves that the latter organization will be an admin of the channel. In

#fabric-questions #fabric

Hi, I'm trying to register a user via Fabric Java SDK but I get the error: "Registration of 'UserToRegister' failed: Error adding identity 'UserToRegister' to the database: attempt to write a readonly

#fabricca #fabric-ca #fabric-questions #fabric

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

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

Hi, I have a running network with Fabric 1.4 and I need to upgrade it to Fabric 2.1.1. I've generated the crypto material using cryptogen and now I want to use Fabric CA. If I regenerate the crypto ma

#fabric-questions #fabric #hyperledger-fabric

Thanks for the reply. I've modified the policy accordingly to your response and now it's working fine, thank you.

#fabric-questions

I've specified a policy for the LifecycleEndorsement in my configtx.yaml and it is: LifecycleEndorsement: Type: Signature Rule: "OR('MyOrgMSP.admin')" But when I try to commit the chaincode I get ENDO

#fabric-questions

Update: I've delayed the generation of the peer certs and now it starts correctly. Thanks for the help!

#fabric #fabric-questions