After Recon Denied Chase Csr Can You Call Again

Blockchain Hyperledger Fabric — Errors & Solutions

Source: Google(iStock)

READ More from — " https://blockchaindreamlab.com/ " —

How-do-you-do, In this article I wanted to share some of the errors you might confront & the possible solutions.

please note that, I accept faced "n" number of errors while I was working in Blockchain project, I have spent endless hours reading out articles, reaching out experts to fix the aforementioned. This commodity is to just help the people who are beginners & struggling to solve the errors that are quite often pop up during your evolution phase. If you have any errors that are not listed here, please feel gratis to comments, volition get information technology added .

Error No 1:

Fault: Error trying to ping. Error: 2 UNKNOWN: make sure the chaincode test-registry has been successfully instantiated and effort again: could non find chaincode with name 'test-registry'

Solutions: Make certain that you have installed the network earlier you beginning. Utilise beneath commands to starting time the network

- composer network install — card PeerAdmin@hlfv1 — archiveFile network-proper noun@0.0.1.bna

- composer network start — networkName networkname — networkVersion 0.0.1 — networkAdmin admin — networkAdminEnrollSecret adminpw — card PeerAdmin@hlfv1 — file networkadmin.card

Error No 2:

Mistake:
docker: Error response from daemon: Conflict. The container name "/composer-playground" is already in utilize by container "9f224b04663a4fa65f50843e5f7e28f7e7df662507a9b42ae5dfc72fd3433405". You have to remove (or rename) that container to be able to reuse that name.
See 'docker run — help'.

Solutions: Kill the dockers by running following command & re-execute the composer-playground command ("docker run — name composer-playground — publish 8080:8080 hyperledger/composer-playground")

docker rm -f $(docker ps -a -q)

docker impale $(docker ps -q)

docker rm $(docker ps -aq)

docker rmi $(docker images dq-* -q)

Error No 3:

Error: Chaincode already exists error

Solutions: Kill docker images, stop fabric & outset textile over again. Once it runs fine, then start deploying the business organisation network card again.

./stopFabric.sh

./startFabric.sh

Error No iv:

Fault: NG Serve Error

Solutions: Use npm instead of ng serve.

npm start

Error No 5:

Error: Authorisation error Balance-API

Solutions: Setup COMPOSER_PROVIDERS in environment variable, and restart the composer-balance-server

Follow this link https://github.com/hyperledger/composer/hulk/master/packages/composer-website/jekylldocs/integrating/enabling-residue-authentication.medico

Fault No 6:

Discovering types from business organisation network definition …
Connection fails: Mistake: Fault trying to ping. Error: 2 UNKNOWN: make sure the chaincode 'network-proper noun' has been successfully instantiated and attempt again: could not find chaincode with name 'network-name'

Solutions: Make certain to install & start the business network earlier you run composer-balance-server command.

1)composer network install — carte PeerAdmin@hlfv1 — archiveFile network-name@0.0.ane.bna

two)composer network outset — networkName 'network-name' — networkVersion 0.0.1 — networkAdmin admin — networkAdminEnrollSecret adminpw — bill of fare PeerAdmin@hlfv1 — file networkadmin.carte

Mistake No 7:

ERROR: for couchdb Cannot create container for service couchdb: Conflict. The container proper name "/couchdb" is already in apply by container "de8ceaf8f21b53bb4c9883eb618448f6f07c7690bea8ab122ef3b689e846eab4". You have to remove (or rename) that Creating orderer.example.com … error

Solutions: Kill the dockers past running post-obit control

docker rm -f $(docker ps -aq)

Mistake No : 8

Error: Cannot notice module 'fabric-customer'

Solution: Perform npm update, this volition install necessary plug-in's & modules.

npm update

Mistake No : 9

Error: npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm WARN Local parcel.json exists, simply node_modules missing, did you mean to install?

Solution: perform npm install, this will install necessary node_modules.

npm install

Error No: x

Error: Angular2 app generated by "yo fabric-composer" does not take UI for Transactions

Solutions: We take issue open in Github — please follow the event for more updates

Solution Update :

Go to <transaction>.component.html file in src/app/<transaction> binder and bank check for line
<button type="button" class="btn btn-primary invokeTransactionBtn" information-toggle="modal">Invoke</button>

Just add information-target attribute to it as below:
<button type="push button" class="btn btn-main invokeTransactionBtn" data-toggle="modal" data-target="#addTransactionModal">Invoke</button>

#addTransactionModal is the id for the modal which has the grade.

LInk : https://github.com/hyperledger/composer/issues/4121

Error No: 11

Error: Connection fails: Fault: Error trying to ping. Error: Composer runtime (0.19.8) is not compatible with customer (0.xix.5)
Information technology will exist retried for the next asking.

Solutions:

./stopFabric.sh

npm install -g composer-playground@0.19.8

composer-rest-server

Error No 12:

Error: ringlet: (7) Failed to connect to localhost port 49160: Connection refused

Solution: docker run — rm -i -t -p 49160:8080 <your username>/node-app

Annotation: This kind of error will only shoot up, when you build your own docker container & trying to execute it.

Mistake No 13:

ERROR: network composer_default id b1067bdec4ca1800510fc9cc1f5d3500736e48920693b03831df0d8d8472ffac has active endpoints

Y'all might hit this error, when you lot trying to execute new fabric-server(only the onetime one still in running land)

Solutions : Finish the already running fabric server, using .stopFabric.sh or .cease.sh(whatever the script you has in your network), and so apply the following command to remove the running docker containers, and re-execute the material

docker rm -f $(docker ps -a -q)

Fault No xiv:

Error: Node.JS Error: ENOSPC

Solution : https://stackoverflow.com/questions/22475849/node-js-error-enospc .

Error NO 15:

Error: failed to create evangelize client: orderer client failed to connect to orderer.example.com:7050: failed to create new connection: context deadline exceeded

Solution : You need to review the Orderer logs first to ensure what's happening under the hood.

Step one: docker logs orderer.example.com

Stride 2: go to configtx.yaml file and bank check the capabilities

ensure you accept correct versions downloaded

Error No xvi:

Error: Failed to import the business network card

Failed to import the business network card
keyword: required
dataPath: .peers['peer0.org1.case.com']
schemaPath: #/required
params:
missingProperty: eventUrl
message: should have required belongings 'eventUrl'

Mistake: Errors found in the connection profile in the bill of fare
Command failed

Solution: You are trying to run fabric v1.1, just it pulls out fabric v1.ii createpeeradmin.sh

Error No : 17

Error: container is marked for removal and cannot exist started

Sometimes, when you kill / remove containers, information technology would sit up in "Removal Queue" or in "Expressionless Status", that would be mounted forever and will not allow y'all to run your next steps.. So you have to remove the containers using below command. this kills all the containers that are marked in Expressionless state.

Solution: docker rm $(docker ps — all -q -f status=dead)

Error No : 18

Fault: sendPeersProposal — Promise is rejected: Error: chaincode with name 'chain-code-proper name' already exists

Situtation — Occurred while instantiating chaincode

Solutions: This error mostly would occur due to the fact that, chaincode would have already instantiated on peers. And then get rid of this, remove the node_modules & practise npm install in one case it finishes fine, restart the "install chaincode" and and then "instantitaet chaincode".

Or

Utilize different chain_node id

Error No : nineteen

CRIT 008 Error on outputBlock: Error writing genesis cake: open ./channel-artifacts/genesis.cake: no such file or directory

Solution : Create aqueduct-artifacts folder before you run the control

./configtxgen -profile FourOrgsOrdererGenesis -outputBlock ./aqueduct-artifacts/genesis.block

Error No : xx

Error: readBlock -> DEBU 00a Got status: &{FORBIDDEN} Error: tin can't read the block: &{FORBIDDEN}

Solution : Make sure, before you get-go your network no other containers are running behind. This error occurs due to permission issues, that containers are in conflict with existing containers. Goahead, kill the containers using docker rm -f $(docker ps -a -q) command & restart your network.

Error No : 21

grpc: addrConn.createTransport failed to connect to {peer0.org1.case.com:7051 0 <nil>}. Err :connectedness mistake: desc = "transport: Error while dialing dial tcp: lookup peer0.org1.example.com on 127.0.0.11:53: no such host". Reconnecting…

Solution: .. to be identified…

Error No : 22

Error: Network Not found issue

Solution : Go to ./peer-base.yaml and change CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE to the corresponding network proper name. Clean the docker containers and then rebuild

Error No : 23

Error: Sending the Instantiate Proposal ..
error: [Peer.js]: sendProposal — timed out later:45000

Solution: …

Note: After some time, information technology ran fine. but I volition proceed information technology updated when I face information technology once again.

Error No : 24

Error: could not assemble transaction: ProposalResponsePayloads do not match — proposal response: version:ane response:<status:200 >

Solution: Make certain, yo have installed Chaincode in the peers you are trying to invoke the transactions. Prepare the environment variables for the peers. For instance :

CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/cloth/peer/crypto/peerOrganizations/org2.example.com/users/Admin@org2.instance.com/msp CORE_PEER_ADDRESS=peer0.org2.case.com:7051 CORE_PEER_LOCALMSPID="Org2MSP" CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt peer chaincode install -n mycc -v 1.0 -p github.com/chaincode/chaincode_example02/go/

Mistake No :25

Error: Calling enrollment endpoint failed with mistake [Error: connect ECONNREFUSED 127.0.0.1:7054]

Solution: Regenerate Crypto Files, then point the secretKey in docker-composer-yaml file for ca-material (if 7054 is pointeed to CA-fabric)

Mistake No : 26 instantiate-chaincode-Instantiate proposal was bad

This mistake would mostly occur when you attempt to instantiate the Chaincode.

Solution: you should understand the bones catamenia how it works first?, when you install Chaincode on peers, it would generally be successfull, but after y'all install and instantiate the chaincode it would perform lot of actions such as

• Scanning for Chaincode Syntax, Logical issues, etc.,
• Bundling the code together
• Trying to create a container with chaincodename-chaincode version

So what happen is that, the "Chaincode" instantitation mostly would neglect in "Syntax checking & logical problems in your chaincode".. To identify the same, run the post-obit control in separate final

docker logs -f peer0.org1.example.com

Here, peer should be the one where yous are trying to instantiate. this will give you clear logs behind , what'southward happening and where the errors are being thrown, prepare the errors & re install , instantitate.. YOU SHOULD Exist GOOD TO GO

Error 27: instantiate-chaincode — Error: ChannelEventHub has been shutdown

Solution: Mostly this occurs in "instantiate-chaincode" section, eventhub will get disconnect when it finds more than one chaincode version (when you upgraded with multiple version of same chaincode). Merely impale all the containers, just keep the one that'due south the latest version and so endeavour install & instantitate the chaincode

Error 28: instantiate-chaincode — Error: ChannelEventHub has been shutdown

Solution: Mostly this occurs in "instantiate-chaincode" section, eventhub will become disconnect when it finds more than one chaincode version (when you upgraded with multiple version of same chaincode). Just kill all the containers, merely go on the 1 that'south the latest version then try install & instantitate the chaincode

Error 29: Cannot employ encKey (type string) equally type []byte in argument to entities.NewAES256EncrypterEntity

Error thirty: instantiate Proposal was bad — Chaincode

Solution: When you find this error,

i) Check if yous have right fabric-client & fabric-ca-client by using below command

npm ls cloth-client

npm ls fabric-ca-customer

Ensure, you accept right compatible docker images with respect to fabric-customer version.

Mistake 31: docker: Got permission denied while trying to connect to the Docker daemon socket at unix

Solution: sudo usermod -a -M docker $USER

Perform this operation in your final, close it and re-open up the terminal. if issue nonetheless persists, and then re-boot your organisation.

Fault 32: [Remote.js]: Mistake: Failed to connect before the deadline URL:grpcs://localhost:7051

ERROR 33: response ::{"status":"BAD_REQUEST","info":"mistake authorizing update: error validating ReadSet: readset expected key [Grouping] /Channel/Application at version 0, simply got version 1"}

SOLUTION : More often than not yous will get this fault when yous trying to create a aqueduct where channel would have already got created. And so you lot can ignore this message and proceed with "JOIN Channel"

ERROR 34: response ::{"condition":"FORBIDDEN","info":"Failed to reach implicit threshold of 1 sub-policies, required one remaining: permission denied"}

ERROR 35 : affiliation validation: Failed getting affiliation 'org3.department1

Solutions: the issue is that the cloth-ca being used in the sample does not know virtually the new affiliation. By default, textile-ca only has the following affiliations:

org1.department1 org1.department2 org2.department1

get to app/helper.js and update the logic similar below, replace getRegisteredUser office with beneath logic.

var getRegisteredUser = async office(username, userOrg, isJson) {
try {
var client = await getClientForOrg(userOrg);
logger.debug('Successfully initialized the credential stores');
// client can at present human activity as an amanuensis for organization Org1
// first bank check to see if the user is already enrolled
var user = await client.getUserContext(username, true);
if (user && user.isEnrolled()) {
logger.info('Successfully loaded member from persistence');
var response = {
success: false,
};
return response;
} else {
// user was not enrolled, so we will need an admin user object to register
logger.info('User %s was non enrolled, and then we will need an admin user object to register',username);
var admins = hfc.getConfigSetting('admins');
let adminUserObj = await customer.setUserContext({username: admins[0].username, password: admins[0].secret});

//newly added
if(adminUserObj.getAffiliation() != userOrg.toLowerCase()){
logger.info('Admin affiliation not registered. Registering now.');
adminUserObj.setAffiliation(userOrg.toLowerCase());
adminUserObj.setRoles(['peer','orderer','client','user']);
adminUserObj = await client.setUserContext(adminUserObj);
}

logger.info('Admin User: %s', adminUserObj);
let affiliation = userOrg.toLowerCase() + '.department1';

allow caClient = client.getCertificateAuthority();

//bank check if org exists
const affiliationService = caClient.newAffiliationService();
const registeredAffiliations = look affiliationService.getAll(adminUserObj);
if(!registeredAffiliations.result.affiliations.some(x => x.name == userOrg.toLowerCase())){
logger.info('Register the new affiliation: %southward ', affiliation);
await affiliationService.create({name: affiliation, strength: true}, adminUserObj);
}

permit secret = await caClient.register({
enrollmentID: username,
affiliation: affiliation
}, adminUserObj);
logger.debug('Successfully got the secret for user %southward — %s',username);

user = wait client.setUserContext({username:username, password:hush-hush});
logger.debug('Successfully enrolled username %southward and setUserContext on the customer object', username);

}
if(user && user.isEnrolled) {
if (isJson && isJson === true) {
var response = {
success: true,
secret: user._enrollmentSecret,
message: username + ' enrolled Successfully',
};
return response;
}
} else {
throw new Error('User was non enrolled ');
}
} take hold of(error) {
let bulletin = 'Failed to register the username ' + username + ' for organization ' + userOrg + ' with fault: ' + error.toString();
logger.mistake(message);
var response = {
success: false,
message: message,
};
return response;
}

};

Fault 36 : Failed to get registered user: "user" with error: Fault: Cannot find module './utils.js'

Open up issue : https://jira.hyperledger.org/browse/FABN-1500

Error 37: panic: etcdraft raft configuration missing [recovered]

ERROR 38 : Error: could not assemble transaction, err proposal response was non successful, error lawmaking 500, msg mistake starting container: error starting container: Failed to generate platform-specific docker build: Failed to pull hyperledger/cloth-ccenv:latest: API error (404): manifest for hyperledger/fabric-ccenv:latest not found: manifest unknown: manifest unknown

If you are running earlier version of fabric, you may confront this errror.

Solution: In your instantiate chaincode script, add together these ii lines before you call instantiate

          docker pull hyperledger/fabric-ccenv:one.4.three          docker tag hyperledger/fabric-ccenv:one.iv.3 hyperledger/fabric-ccenv:latest        

Error NO 39 : Cannot connect to http://localhost:5984/_utils

Solution : Endeavour switching from localhost to 127.0.0.ane

ERROR NO forty : Common connection profile missing error while adding user for organization

Solution : getCertificateAuthority() function should exist passed with ca name

=====

Portainer setup:

          # docker volume create portainer_data
# docker run -d -p 9000:9000 -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer        

— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — -

Note: Like this article?, give Logeswaran a thumbs-up(Claps) & follow him on Linkedin / Twitter

Practise you accept an error which is non listed here? pls go ahead and add that in the comment section below.

millergamention.blogspot.com

Source: https://medium.com/coinmonks/hyperledger-fabric-composer-errors-solutions-827112a3fce6

Share this post