Welcome to the Linux Foundation Forum!

Lab 7: ERRO 041 [allarewelcome] Got error &{FORBIDDEN}

(my encounter and escape from ERRO 041

when I try to get config (genesis block) for peer0.org2 I have above error, on second use, first time it works without error

  1. # fetch genesis block
  2. $ peer channel fetch 0 Org2AddedConfig.block -c allarewelcome -o orderer.example.com:7050
  3. 2019-11-09 18:31:20.732 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
  4. 2019-11-09 18:31:20.735 UTC [cli.common] readBlock -> INFO 002 Got status: &{FORBIDDEN}
  5. Error: can\'t read the block: &{FORBIDDEN}

first time I send update to the network for approval with

  1. $ peer channel update -f org2SubmitReady.pb -c allarewelcome -o orderer.example.com:7050

it works, if I try to do the same, always have above error

  1. $ peer channel update -f org2SubmitReady.pb -c allarewelcome -o orderer.example.com:7050
  2. 2019-11-09 19:09:01.721 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
  3. Error: got unexpected status: BAD_REQUEST -- error authorizing update: error validating ReadSet: readset expected key [Group] /Channel/Application/Org1MSP at version 1, but got version 0

the problem is when I try to join org2 to channel and always have above errors

  1. $ PEER=peer0
  2. $ export CORE_PEER_LOCALMSPID=Org2MSP
  3. $ export CORE_PEER_ADDRESS=$PEER.org2.example.com:7051
  4. $ export CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp
  5. $ peer channel fetch 0 Org2AddedConfig.block -c allarewelcome -o orderer.example.com:7050
  6. 2019-11-09 19:13:27.559 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
  7. 2019-11-09 19:13:27.561 UTC [cli.common] readBlock -> INFO 002 Got status: &{FORBIDDEN}
  8. Error: can't read the block: &{FORBIDDEN}

I can see in peer0.org2.example.com logs

  1. peer0.org2.example.com | 2019-11-09 19:06:54.126 UTC [ConnProducer] DisableEndpoint -> WARN 04a Only 1 endpoint remained, will not black-list it
  2. peer0.org2.example.com | 2019-11-09 19:06:54.137 UTC [blocksProvider] DeliverBlocks -> ERRO 04b [allarewelcome] Got error &{FORBIDDEN}
  3. peer0.org2.example.com | 2019-11-09 19:06:56.344 UTC [gossip.gossip] Gossip -> WARN 04c Failed obtaining gossipChannel of [97 108 108 97 114 101 119 101 108 99 111 109 101] aborting
  4. peer0.org2.example.com | 2019-11-09 19:07:01.347 UTC [gossip.gossip] Gossip -> WARN 04d Failed obtaining gossipChannel of [97 108 108 97 114 101 119 101 108 99 111 109 101] aborting
  5. peer0.org2.example.com | 2019-11-09 19:07:04.138 UTC [ConnProducer] DisableEndpoint -> WARN 04e Only 1 endpoint remained, will not black-list it
  6. peer0.org2.example.com | 2019-11-09 19:07:04.150 UTC [blocksProvider] DeliverBlocks -> ERRO 04f [allarewelcome] Got error &{FORBIDDEN}
  7. peer0.org2.example.com | 2019-11-09 19:07:06.349 UTC [gossip.gossip] Gossip -> WARN 050 Failed obtaining gossipChannel of [97 108 108 97 114 101 119 101 108 99 111 109 101] aborting
  8. peer0.org2.example.com | 2019-11-09 19:07:11.352 UTC [gossip.gossip] Gossip -> WARN 051 Failed obtaining gossipChannel of [97 108 108 97 114 101 119 101 108 99 111 109 101] aborting
  9. peer0.org2.example.com | 2019-11-09 19:07:14.151 UTC [ConnProducer] DisableEndpoint -> WARN 052 Only 1 endpoint remained, will not black-list it
  10. peer0.org2.example.com | 2019-11-09 19:07:14.165 UTC [blocksProvider] DeliverBlocks -> ERRO 053 [allarewelcome] Got error &{FORBIDDEN}
  11. peer0.org2.example.com | 2019-11-09 19:07:14.165 UTC [blocksProvider] DeliverBlocks -> ERRO 054 [allarewelcome] Wrong statuses threshold passed, stopping block provider
  12. peer0.org2.example.com | 2019-11-09 19:07:14.165 UTC [gossip.election] stopBeingLeader -> INFO 055 faee1653f635f823d0735d4a03f133f4d3142dd2a5f9a4b63e030c3c8b335dab Stopped being a leader
  13. peer0.org2.example.com | 2019-11-09 19:07:14.166 UTC [gossip.service] func1 -> INFO 056 Renounced leadership, stopping delivery service for channel allarewelcome

in orderer.example.com logs

  1. orderer.example.com | 2019-11-09 19:14:24.240 UTC [comm.grpc.server] 1 -> INFO 0ea streaming call completed {"grpc.start_time": "2019-11-09T19:14:24.24Z", "grpc.service": "orderer.AtomicBroadcast", "grpc.method": "Deliver", "grpc.peer_address": "172.20.0.10:37290", "grpc.code": "OK", "grpc.call_duration": "713.077µs"}
  2. orderer.example.com | 2019-11-09 19:14:34.248 UTC [cauthdsl] deduplicate -> ERRO 0eb Principal deserialization failure (MSP Org2MSP is unknown) for identity 0
  3. orderer.example.com | 2019-11-09 19:14:34.249 UTC [cauthdsl] deduplicate -> ERRO 0ec Principal deserialization failure (MSP Org2MSP is unknown) for identity 0
  4. orderer.example.com | 2019-11-09 19:14:34.249 UTC [common.deliver] deliverBlocks -> WARN 0ed [channel: allarewelcome] Client authorization revoked for deliver request from 172.20.0.10:37292: Failed to reach implicit threshold of 1 sub-policies, required 1 remaining: permission denied
  5. orderer.example.com | 2019-11-09 19:14:34.249 UTC [comm.grpc.server] 1 -> INFO 0ee streaming call completed {"grpc.start_time": "2019-11-09T19:14:34.248Z", "grpc.service": "orderer.AtomicBroadcast", "grpc.method": "Deliver", "grpc.peer_address": "172.20.0.10:37292", "grpc.code": "OK", "grpc.call_duration": "1.669571ms"}

seems related with Principal deserialization failure (MSP Org2MSP is unknown) for identity 0

FINAL FIX: after some debug, I re-start generate ALL files to add org2 to network, start in section Adding a New Organization to Our Channel

  1. # inside cli container, grab latest configuration definition from the network
  2. $ peer channel fetch config blockFetchedConfig.pb -o orderer.example.com:7050 -c allarewelcome
  3. .....follow docs, creating files until we have reach line
  4. # send update to the network for approval
  5. $ peer channel update -f org2SubmitReady.pb -c allarewelcome -o orderer.example.com:7050

now after re-send the send update to the network for approval, with

  1. $ peer channel update -f org2SubmitReady.pb -c allarewelcome -o orderer.example.com:7050

the running peer0.org2.example.com container crash, and stop, I delete it, and re-start it, and it start to work :)

I don't know if the solution is deleting the container or re-create the files and send the network update to approval?
maybe some expert can clarify me.....or next time I try first drop container, but I don't want to drop containers, in this case I dont any choice it crash

  1. # start and check it all works well
  2. $ docker-compose up -d peer0.org2.example.com
  3. $ docker-compose logs -f peer0.org2.example.com

now I can get config/genesis block again and join channel with peer0.org2

  1. # fetch genesis block
  2. $ peer channel fetch 0 Org2AddedConfig.block -c allarewelcome -o orderer.example.com:7050
  3. 2019-11-09 19:29:56.112 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
  4. 2019-11-09 19:29:56.114 UTC [cli.common] readBlock -> INFO 002 Received block: 0
  5. # join channel
  6. $ peer channel join -b Org2AddedConfig.block
  7. # list channel
  8. $ peer channel list
  9. Channels peers has joined:
  10. allarewelcome
  11. # do the same for peer1.org2
  12. $ PEER=peer0
  13. $ export CORE_PEER_ADDRESS=$PEER.org2.example.com:7051
  14. $ peer channel join -b Org2AddedConfig.block
  15. Channels peers has joined:
  16. allarewelcome
  17. # list channel
  18. $ peer channel list

done problem solved, I can continue my HL adventure

Comments

  • Are the CORE_PEER_LOCALMSPID and CORE_PEER_MSPCONFIGPATH environment variables set correctly?

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Categories

Upcoming Training