Channel creation failed. Problem with key group channel application - hyperledger-fabric

Couldn't create my channel and got following error:
2021-01-27 10:32:42.643 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
Error: got unexpected status: BAD_REQUEST -- error applying config update to existing channel 'mychannel': error authorizing update: error validating ReadSet: proposed update requires that key [Group] /Channel/Application be at version 0, but it is currently at version 1
!!!!!!!!!!!!!!! Channel creation failed !!!!!!!!!!!!!!!!
========= ERROR !!! FAILED to execute End-2-End Scenario ===========
Any idea how to solve this error?
How can I change this key [Group] /Channel/Application version?

Make sure you are inside the test-network directory and run the following commands
source scriptUtils.sh
. scripts/envVar.sh
export FABRIC_CFG_PATH=$PWD/../config/
Now try to run the create channel command
Make sure you have configtx.yaml present inside config directory

Related

After running ./byfn.sh up got this Error. ERROR !!! FAILED to execute End-2-End Scenario

I'm trying to install Hyperledger in my Ubuntu Stand Alone system, After running sudo ./byfn.sh up i got this Error please help..!
Error: failed to create deliver client for orderer: orderer client
failed to connect to orderer.example.com:7050: failed to create new
connection: connection error: desc = "transport: error while dialing:
dial tcp: lookup orderer.example.com: no such host" !!!!!!!!!!!!!!!
Channel creation failed !!!!!!!!!!!!!!!!
========= ERROR !!! FAILED to execute End-2-End Scenario ===========
ERROR !!!! Test failed
byfn.sh script was used with older fabric versions and is no longer supported. The latest fabric-samples is having a network.sh script to setup fabric network. Detailed tutorial is available in official docs.

Hyperledger cannot update channel

I am trying to update an existing channel to enable lifecyle.
Official link:
https://hyperledger-fabric.readthedocs.io/en/release-2.2/enable_cc_lifecycle.html
Launching this command on my peer:
peer channel update -f config_update_in_envelope.pb -c channelid -o orderer.domain.com:7050 --cafile /opt/gopath/s
rc/github.com/hyperledger/fabric/crypto-config/peerOrganizations/*******/ca
Error
got unexpected status: BAD_REQUEST -- initializing channelconfig failed: could
not create channel Consortiums sub-group config: setting up the MSP
managerfailed: expected at least one CA certificate
I tried all existing ca certs available on my network and It's not working,
Please help
Thanks
This error was "probably" due to a version mismatch ... one orderer used on my network was still using an 1.4 version, since this orderer has been upgraded it's not possible to reproduce this error again. Even if I do not understand why the error msg is talking about a CA file ...

Anchor Peer updation fails, after updating channel configurarion in Hyperledger Fabric

Initially I had one organization in the channel, I have added one more organization to the channel by following the link https://hyperledger-fabric.readthedocs.io/en/release-1.4/channel_update_tutorial.html. After adding the new organization to the channel, when I try to update anchor peer it's throwing an error an error saying
"Error: got unexpected status: BAD_REQUEST -- error authorizing update: error validating ReadSet: readset expected key [Group] /Channel/Application at version 1, but got version 2"
Cannot update anchor peer using peer channel update.
peer channel update -o orderer.example.com:7050 -c mychannel -f Org1MSPanchors.tx
Error: got unexpected status: BAD_REQUEST -- error authorizing update: error validating ReadSet: readset expected key [Group] /Channel/Application at version 1, but got version 2
Had been lost in this for too long.
Any kind of help is appreciated..

HyperLeder Fabric: Failed to invoke chaincode name:"lscc" , error: timeout expired while starting chaincode

I have started to get time out error while installing my chaincode. The chaincode is pretty basic, in fact, I am just extending the fabcar node.js sample. Please see the error I receive:
Error: could not assemble transaction, err Proposal response was not successful, error code 500, msg failed to execute transaction e865662f96312f27ee8a221faba6893633498693408f95e57e5e404e58731afd: timeout expired while starting chaincode aar:1.0 for transaction e865662f96312f27ee8a221faba6893633498693408f95e57e5e404e58731afd
Error from the Peer node container logs:
2018-10-16 09:44:13.640 UTC [endorser] SimulateProposal -> ERRO 038 [mychannel][e865662f] failed to invoke chaincode name:"lscc" , error: timeout expired while starting chaincode aar:1.0 for transaction e865662f96312f27ee8a221faba6893633498693408f95e57e5e404e58731afd
I have already increased the values of the following two environment variables but to no avail:
CORE_CHAINCODE_DEPLOYTIMEOUT=1000s
CORE_CHAINCODE_STARTUPTIMEOUT=1000s
For me there was a compilation error in a JS class inside the chaincode folder. So, ensure that everything inside your chaincode folder is fine, otherwise you'll get lscc timeout error while chaincode installs on the peer

Hyperledger Fabric Errror : Query - Error: chaincode error (status: 500, message: Failed to get block number 1, error Entry not found in index

I am trying to execute balance-transfer application that ship in fabric-samples of hyperledger. Source code path git clone https://github.com/hyperledger/fabric-samples.git
All steps executed as below
Channel created Joined channel on Org1
Joined channel on Org2
Successfully Installed chaincode on organization org1
Successfully Installed chaincode on organization org2
but instantiate of chaincode operation is failing on peers.
Can anyone please help me to solve this issue. I am struggling from last one week. I am using docker container on ubuntu v16.
Error Log:
[2017-10-02 05:11:11.374] [DEBUG] Helper - [crypto_ecdsa_aes]: ecdsa signature: Signature {<br/>
r: <BN: 4824699f0a1d1a0fc696df545fb3379dffc6b46124619f53672359a6755bc7ff>,<br/>
s: <BN: 49fc91b2a7800eff5396053d4d8ff2683167a9e3f52ccc43228143f9b5741168>,<br/>
recoveryParam: 0 }
error: [client-utils.js]: sendPeersProposal - Promise is rejected: Error: chaincode error (status: 500, message: Failed to get block number 1, error Entry not found in index)<br/>
at /home/02102017/fabric-samples/balance-transfer/node_modules/grpc/src/node/src/client.js:554:15<br/>
error: [Channel.js]: Failed Query block. Error: Error: chaincode error (status: 500, message: Failed to get block number 1, error Entry not found in index)<br/>
at /home/02102017/fabric-samples/balance-transfer/node_modules/grpc/src/node/src/client.js:554:15<br/>
[2017-10-02 05:11:11.472] [ERROR] Query - Error: chaincode error (status: 500, message: Failed to get block number 1, error Entry not found in index)<br/>
at /home/02102017/fabric-samples/balance-transfer/node_modules/grpc/src/node/src/client.js:554:15<br/>
Isssue resolve after increasing request-timeout in file fabric-samples-master/balance-transfer/node_modules/fabric-client/config/default.json
There is no need to overwrite fabric-samples-master/balance-transfer/node_modules/fabric-client/config/default.json. There is a open issue on JIRA https://jira.hyperledger.org/browse/FABN-884 regarding request timeout.
and For now as a workaround you could set it globally before making the call.
const temp = client.getConfigSetting('request-timeout');
client.setConfigSetting('request-timeout', 60000);
... make your call ...
client.setConfigSetting('request-timeout', temp);
Hope it will work for you.

Resources