CHANNEL CREATION FAILED: Error: Error: Failed to create the channel.

[servntire]

Getting error when running node createTradeApp.js

• Docker containers are up and running.
• Dependencies are correct.

[VRamakrishna]

Clearly the client.createChannel(...) failed, but it's hard to say what the problem was without more info. Can you paste the results of docker ps -a, and also attach the network log file (the default should be <root-folder>/network/logs/network.log)?

[servntire]

I'm executing the project as follows.
DIR network
./trade.sh up
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 090492aac76a hyperledger/fabric-ca:latest "sh -c 'fabric-ca-se…" 2 hours ago Up About a minute 0.0.0.0:7054->7054/tcp ca_peerExporterOrg d05185b04ef4 hyperledger/fabric-ca:latest "sh -c 'fabric-ca-se…" 2 hours ago Up About a minute 0.0.0.0:10054->7054/tcp ca_peerRegulatorOrg e429e94a4896 hyperledger/fabric-ca:latest "sh -c 'fabric-ca-se…" 2 hours ago Up About a minute 0.0.0.0:9054->7054/tcp ca_peerCarrierOrg d831241c9d4b hyperledger/fabric-ca:latest "sh -c 'fabric-ca-se…" 2 hours ago Up About a minute 0.0.0.0:8054->7054/tcp ca_peerImporterOrg 2ddcaca2ab34 hyperledger/fabric-peer:latest "peer node start" 2 hours ago Up About a minute 0.0.0.0:10055->6060/tcp, 0.0.0.0:10051->7051/tcp, 0.0.0.0:10053->7053/tcp peer0.regulatororg.trade.com 7caba45fa694 hyperledger/fabric-peer:latest "peer node start" 2 hours ago Up About a minute 0.0.0.0:8055->6060/tcp, 0.0.0.0:8051->7051/tcp, 0.0.0.0:8053->7053/tcp peer0.importerorg.trade.com 7fdfdeb1d0e2 hyperledger/fabric-peer:latest "peer node start" 2 hours ago Up About a minute 0.0.0.0:7051->7051/tcp, 0.0.0.0:7053->7053/tcp, 0.0.0.0:7055->6060/tcp peer0.exporterorg.trade.com b8bf8698862e hyperledger/fabric-orderer:latest "orderer" 2 hours ago Up About a minute 0.0.0.0:7050->7050/tcp orderer.trade.com 44638dff878a hyperledger/fabric-peer:latest "peer node start" 2 hours ago Up About a minute 0.0.0.0:9055->6060/tcp, 0.0.0.0:9051->7051/tcp, 0.0.0.0:9053->7053/tcp peer0.carrierorg.trade.com

DIR middleware
node createTradeApp.js

NetworkLog
network.log

[VRamakrishna]

If you scroll down to the end of the network.log file, you'll see that the signature validations fail, most likely because of certificate/key mismatches. Please retry after starting from a clean slate:

• Clear the contents of the network/client-certs/ folder.
• Regenerate the crypto material and channel artifacts using ./trade.sh generate -c tradechannel in the network folder.
• Restart the network by running ./trade.sh up.
• Run the JS scripts in the middleware folder.

[servntire]

I tried it again. The ca is getting exited. Earlier I solved it by replacing ORG_CA_PRIVATE_KEY manually into the docker-compose-e2e.yaml file

Attaching the network log.
network.log

Looks like something is missing.

[VRamakrishna]

Did you run ./trade.sh generate -c tradechannel? That command is supposed to replace the variable with the generated key file location. Did you observe any errors when you ran the command?

[shalini-kad]

It was not replacing the place holders. OS X requires the extension to be explicitly specified. The So I added an empty string. Now it's properly generating the e2e-compose file.

But still the issue is existing.

From network log, I assume it's related to certificate validation. Principal deserialization failure (the supplied identity is not valid: x509: certificate signed by unknown authority (possibly because of "x509: ECDSA verification failure" or policy.

Networklog
network.log

[servntire]

Resolved the issue by clearing docker volumes and removing docker images.

Error: status: 500, message: is not a valid endorsement system chaincode

Network Log
network.log

[VRamakrishna]

OK, I understand now. I tested the setup and application on Linux (Ubuntu), and in an Ubuntu Box on Windows using Vagrant.

@ldesrosi Do you have any tips to share for setup and runs on a Mac?

[servntire]

@VRamakrishna Can you please check my previous comment also.

[VRamakrishna]

@servntire Yes, you needed to remove the chaincode images (I thought you hadn't crossed the channel creation stage, and the chaincode containers don't get built until the instantiation stage.)

It's hard to make out what the error is from the logs. Did you check whether all the containers are running using docker ps -a? Did some exit?

Your best best at this time is to reset and retry.

Remove the running containers:
docker kill $(docker ps -q)
docker rm $(docker ps -a -f status=exited -q)
Delete the chaincode images (if they exist): docker rmi $(docker images | grep "dev-" | awk '{print $3}')
Clear the contents of the network/client-certs folder.

Then restart the network and run the trade application.

Repeat the procedure a couple of times to ensure you are getting an identical error. If that happens, we can try to investigate.

Also, what's your platform? Looking at the paths, you seem to be running on a Windows machine using a Cygwin shell (or is it Git Bash)? Be warned that the setup was tested on Linux (Ubuntu). Even on Windows, we created VMs using VirtualBox and Vagrant. You can use the Vagrantfile bundled with the Fabric source: check out the devenv folder in your local clone of hyperledger/fabric.

[VRamakrishna]

Still seeing these issues? If not, can we close this out?

[VRamakrishna]

Closing due to inactivity.

[tomorenge]

am getting the same error while running node createTradeApp.js