我在Windows10上设置了4个VM（Ubuntu 18.04）以运行Hyperledger fabric。
网络配置由Orderer，Peer0(Org0)，Peer1(Org1)，Client作为每个VM上的节点。
peer0和peer1节点都已成功运行。但是，Orderer无法运行。 Orderer节点似乎正常工作，但事实并非如此。
我检查了orderer ip。没错。
我使用了“超级账本结构样本配置”中的相同orderer.yaml和core.yaml。
ORDERER_GENERAL_LOGLEVEL=debug \
ORDERER_GENERAL_LISTENADDRESS=orderer \
ORDERER_GENERAL_GENESISMETHOD=file \
ORDERER_GENERAL_GENESISFILE=/home/jk/test/testnet/crypto-config/ordererOrganizations/orderer/orderers/orderer.orderer/genesis.block \
ORDERER_GENERAL_LOCALMSPID=OrdererMSP \
ORDERER_GENERAL_LOCALMSPDIR=/home/jk/test/testnet/crypto-config/ordererOrganizations/orderer/orderers/orderer.orderer/msp \
ORDERER_GENERAL_TLS_ENABLED=false \
ORDERER_GENERAL_TLS_PRIVATEKEY=/home/jk/test/testnet/crypto-config/ordererOrganizations/orderer/orderers/orderer.orderer/tls/server.key \
ORDERER_GENERAL_TLS_CERTIFICATE=/home/jk/test/testnet/crypto-config/ordererOrganizations/orderer/orderers/orderer.orderer/tls/server.crt \
ORDERER_GENERAL_TLS_ROOTCAS=[/home/jk/test/testnet/crypto-config/ordererOrganizations/orderer/orderers/orderer.orderer/tls/ca.crt,/home/jk/test/testnet/crypto-config/peerOrganizations/org0/peers/peer0.org0/tls/ca.crt,/home/jk/test/testnet/crypto-config/peerOrganizations/org1/peers/peer1.org1/tls/ca.crt] \
CONFIGTX_ORDERER_BATCHTIMEOUT=1s \
CONFIGTX_ORDERER_ORDERERTYPE=solo \
orderer
2019-05-09 09:36:47.761 KST [orderer/commmon/multichannel] NewRegistrar -> INFO 0b7 Starting system channel 'test-system-channel-name' with genesis block hash 6e0081b164e2cf4b7850577f0172ec6dc16eec227022f7be08db8f4a82b85888 and orderer type solo
2019-05-09 09:36:47.761 KST [orderer/common/server] Start -> INFO 0b8 Starting orderer:
Version: 1.3.1
Commit SHA: 546697782
Go version: go1.12.5
OS/Arch: linux/amd64
Experimental features: false
2019-05-09 09:36:47.761 KST [orderer/common/server] Start -> INFO 0b9 Beginning to serve requests
这似乎是可行的，但我知道事实并非如此。我认为runOrderer.sh不起作用。