Error when reading core config file: Unsupported Config Type

我们两清 提交于 2019-12-22 05:28:39

问题


I am trying to pass in the channel configuration transaction artifact to the order-er using the command:

peer channel create -o orderer.example.com:7050 -c $CHANNEL_NAME -f ./channel-artifacts/channel.tx --tls --cafile 
/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

But I get an error:

2018-03-17 20:55:21.380 GMT [main] main -> ERRO 001 Fatal error
 when initializing core config : error when reading core 
config file: Unsupported Config Type ""

What does this error mean? and how can I fix it?

Using docker ps -a

CONTAINER ID        IMAGE                                                                                                    COMMAND                  CREATED             STATUS                       PORTS                                              NAMES
5c27fce33911        hyperledger/fabric-tools:latest                                                                          "/bin/bash"              3 minutes ago       Up 3 minutes                                                                    cli
aabf72f81352        hyperledger/fabric-peer:latest                                                                           "peer node start"        3 minutes ago       Up 3 minutes                 0.0.0.0:7051->7051/tcp, 0.0.0.0:7053->7053/tcp     peer0.org1.example.com
73ddcafb5ce6        hyperledger/fabric-orderer:latest                                                                        "orderer"                3 minutes ago       Up 3 minutes                 0.0.0.0:7050->7050/tcp                             orderer.example.com
205448f5479a        hyperledger/fabric-peer:latest                                                                           "peer node start"        3 minutes ago       Up 3 minutes                 0.0.0.0:8051->7051/tcp, 0.0.0.0:8053->7053/tcp     peer1.org1.example.com
4e5ba2999f54        hyperledger/fabric-peer:latest                                                                           "peer node start"        3 minutes ago       Up 3 minutes                 0.0.0.0:9051->7051/tcp, 0.0.0.0:9053->7053/tcp     peer0.org2.example.com
fcc6b25b6422        hyperledger/fabric-peer:latest                                                                           "peer node start"        3 minutes ago       Up 3 minutes                 0.0.0.0:10051->7051/tcp, 0.0.0.0:10053->7053/tcp   peer1.org2.example.com
2f1536ffe265        dev-peer0.org1.example.com-fabcar-1.0-5c906e402ed29f20260ae42283216aa75549c571e2e380f3615826365d8269ba   "chaincode -peer.add…"   24 hours ago        Exited (255) 3 minutes ago                                                      dev-peer0.org1.example.com-fabcar-1.0
6ae48101bc34        hyperledger/fabric-ca                                                                                    "sh -c 'fabric-ca-se…"   24 hours ago        Exited (255) 3 minutes ago   0.0.0.0:7054->7054/tcp                             ca.example.com
dc9e5bb3cc8e        hyperledger/fabric-couchdb                                                                               "tini -- /docker-ent…"   24 hours ago        Exited (255) 3 minutes ago   4369/tcp, 9100/tcp, 0.0.0.0:5984->5984/tcp         couchdb

this is the log of orderer.example.com


回答1:


You should be inside the CLI container to execute the peer channel create command.

You will enter the CLI container using the docker exec command:

docker exec -it cli bash

If successful you should see the following:

root@0d78bb69300d:/opt/gopath/src/github.com/hyperledger/fabric/peer#

Over there, you should run the peer channel create command like this:

root@0d78bb69300d:/opt/gopath/src/github.com/hyperledger/fabric/peer# peer channel create -o orderer.example.com:7050 -c $CHANNEL_NAME -f ./channel-artifacts/channel.tx --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

Before running this command, please note that you should also run commands for creating environment variables for CHANNEL_NAME and other Environment variables for PEER0 within this CLI Container.




回答2:


export FABRIC_CFG_PATH=$PWD. it will resolve this issue.




回答3:


Can you try running this command: echo $FABRIC_CFG_PATH

Whatever value you get, can you navigate to that directory and confirm if you can see the configtx.yaml file in there.

From the docs here, it says the error is as a result of inappropriately setting the value of that variable.




回答4:


This is the error you get when the core.yaml is not found. Like the Mukesh mentioned above, running command within the CLI Container will not throw the Error.

See this link for more detail.



来源:https://stackoverflow.com/questions/49341851/error-when-reading-core-config-file-unsupported-config-type

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!