cello v0.9.0-h3c, error log: TLS handshake failed with error EOF server=Orderer remoteaddress=172.24.0.1:59598 #587
Assignees
Comments
|
My cello configuration is like this: |
|
Hello! After yesterday's exploration, I also did the following steps:
大家好，经过昨天的探索，我还做了以下步骤：
After completing the above steps, I created the channel, installed the chaincode, instantiated the chaincode, and on the last attempt at cello, the button would keep spinning around after clicking on the instantiate chaincode. This time, instantiating the chaincode worked, and the invoke and query operations can be performed, but the node logs will always show a TLS handshake failure: 完成以上步骤后，我创建通道，安装链码，实例化链码，在上次尝试cello时，点击实例化链码后按钮会一直转圈。这次实例化链码成功了，可以进行invoke和query操作，但节点日志中始终会显示TLS握手失败： This error has always bothered me, and I can't tell if this represents a failed TLS handshake between nodes, or a failed TLS handshake between cello and the blockchain network. |
|
可以确定这个是节点之间的握手失败，可能是gossip的握手，曾经优化过这个问题，具体记不清了。应该不会影响正常交易。 |
你好！感谢回复。请问目前有解决方案吗？我看了Fabric官方有关gossip的文档。gossip握手失败的话难道不会导致区块链网络不安全不可信吗？已知peer，orderer，ca节点日志全部都会报这个TLS握手失败。网络部署的docker-compose文件的环境变量是这样的： 这里面跟gossip相关的环境变量的配置： |
|
I encountered a similar issue with TLS handshake failures when deploying a Hyperledger Fabric network using Cello. The failed requests were originating from the Docker gateway. After some attempts, I found that the issue seemed resolved when I manually deployed the network using the crypto-config.yaml, configtx.yaml, and docker-compose.yaml files generated by Cello. Here’s what I did: Updated the container_name in docker-compose.yaml to match the SANS names in crypto-config.yaml. Is this a viable solution? What potential issues could this cause? networks: { celloNet: null }
services:
ca.org2.example.com:
command:
sh -c 'fabric-ca-server start -b admin:adminpw -d --config
/etc/hyperledger/fabric-ca-server-config/fabric-ca-server-config.yaml'
container_name: ca.org2.example.com
environment:
[
FABRIC_CA_HOME=/etc/hyperledger/fabric-ca-server,
FABRIC_CA_SERVER_CA_NAME=ca-org2,
FABRIC_CA_SERVER_CA_CERTFILE=/etc/hyperledger/fabric-ca-server-config/ca.org2.example.com-cert.pem,
FABRIC_CA_SERVER_CA_KEYFILE=/etc/hyperledger/fabric-ca-server-config/a6c2302214d375db89d9a66d6cfb888a6b351692d4f14a927ea1c2e155b08c9b_sk,
FABRIC_CA_SERVER_TLS_ENABLED=true,
FABRIC_CA_SERVER_TLS_CERTFILE=/etc/hyperledger/fabric-ca-server-config/ca.org2.example.com-cert.pem,
FABRIC_CA_SERVER_TLS_KEYFILE=/etc/hyperledger/fabric-ca-server-config/a6c2302214d375db89d9a66d6cfb888a6b351692d4f14a927ea1c2e155b08c9b_sk,
]
image: hyperledger/fabric-ca:1.4.9
networks: [celloNet]
ports: ["30003:7054"]
volumes:
[
"../crypto-config/peerOrganizations/org2.example.com/ca/:/etc/hyperledger/fabric-ca-server-config",
]
ca.org3.example.com:
command:
sh -c 'fabric-ca-server start -b admin:adminpw -d --config
/etc/hyperledger/fabric-ca-server-config/fabric-ca-server-config.yaml'
container_name: ca.org3.example.com
environment:
[
FABRIC_CA_HOME=/etc/hyperledger/fabric-ca-server,
FABRIC_CA_SERVER_CA_NAME=ca-org3,
FABRIC_CA_SERVER_CA_CERTFILE=/etc/hyperledger/fabric-ca-server-config/ca.org3.example.com-cert.pem,
FABRIC_CA_SERVER_CA_KEYFILE=/etc/hyperledger/fabric-ca-server-config/f65c26ee7c778d9c70058fd4fadd10a3676caa3c47d47bdc4f3e31574f96ac64_sk,
FABRIC_CA_SERVER_TLS_ENABLED=true,
FABRIC_CA_SERVER_TLS_CERTFILE=/etc/hyperledger/fabric-ca-server-config/ca.org3.example.com-cert.pem,
FABRIC_CA_SERVER_TLS_KEYFILE=/etc/hyperledger/fabric-ca-server-config/f65c26ee7c778d9c70058fd4fadd10a3676caa3c47d47bdc4f3e31574f96ac64_sk,
]
image: hyperledger/fabric-ca:1.4.9
networks: [celloNet]
ports: ["30006:7054"]
volumes:
[
"../crypto-config/peerOrganizations/org3.example.com/ca/:/etc/hyperledger/fabric-ca-server-config",
]
orderer-orderer:
command: orderer
container_name: orderer-orderer
environment:
[
ORDERER_GENERAL_LOGLEVEL=DEBUG,
ORDERER_GENERAL_LISTENADDRESS=0.0.0.0,
ORDERER_GENERAL_LISTENPORT=30000,
ORDERER_GENERAL_GENESISMETHOD=file,
ORDERER_GENERAL_GENESISFILE=/var/hyperledger/orderer/orderer.genesis.block,
ORDERER_GENERAL_LOCALMSPID=OrdererMSP,
ORDERER_GENERAL_LOCALMSPDIR=/var/hyperledger/orderer/msp,
ORDERER_GENERAL_TLS_ENABLED=true,
ORDERER_GENERAL_TLS_PRIVATEKEY=/var/hyperledger/orderer/tls/server.key,
ORDERER_GENERAL_TLS_CERTIFICATE=/var/hyperledger/orderer/tls/server.crt,
"ORDERER_GENERAL_TLS_ROOTCAS=[/var/hyperledger/orderer/tls/ca.crt]",
ORDERER_GENERAL_CLUSTER_CLIENTCERTIFICATE=/var/hyperledger/orderer/tls/server.crt,
ORDERER_GENERAL_CLUSTER_CLIENTPRIVATEKEY=/var/hyperledger/orderer/tls/server.key,
"ORDERER_GENERAL_CLUSTER_ROOTCAS=[/var/hyperledger/orderer/tls/ca.crt]",
]
image: hyperledger/fabric-orderer:1.4.12
networks: [celloNet]
ports: ["30000:30000"]
volumes:
[
"../crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/msp:/var/hyperledger/orderer/msp",
"../crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/tls:/var/hyperledger/orderer/tls",
"../channel-artifacts/genesis.block:/var/hyperledger/orderer/orderer.genesis.block",
]
peer0.org2.example.com:
command: peer node start
container_name: peer0-org2
environment:
[
CORE_PEER_ID=peer0.org2.example.com,
CORE_PEER_LOCALMSPID=Org2MSP,
"CORE_PEER_ADDRESS=peer0.org2.example.com:7051",
CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=deploy_celloNet,
CORE_LOGGING_LEVEL=DEBUG,
CORE_PEER_GOSSIP_USELEADERELECTION=true,
CORE_PEER_GOSSIP_ORGLEADER=false,
CORE_PEER_GOSSIP_SKIPHANDSHAKE=true,
CORE_PEER_TLS_ENABLED=true,
CORE_PEER_TLS_CERT_FILE=/etc/hyperledger/fabric/tls/server.crt,
CORE_PEER_TLS_KEY_FILE=/etc/hyperledger/fabric/tls/server.key,
CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/tls/ca.crt,
GODEBUG=netdns=go,
]
image: hyperledger/fabric-peer:1.4.12
networks: [celloNet]
ports: ["30001:7051", "30002:7052"]
volumes:
[
"/var/run/:/var/run/",
"../crypto-config/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/msp:/etc/hyperledger/fabric/msp",
"../crypto-config/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls:/etc/hyperledger/fabric/tls",
]
peer0.org3.example.com:
command: peer node start
container_name: peer0-org3
environment:
[
CORE_PEER_ID=peer0.org3.example.com,
CORE_PEER_LOCALMSPID=Org3MSP,
"CORE_PEER_ADDRESS=peer0.org3.example.com:7051",
CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=deploy_celloNet,
CORE_LOGGING_LEVEL=DEBUG,
CORE_PEER_GOSSIP_USELEADERELECTION=true,
CORE_PEER_GOSSIP_ORGLEADER=false,
CORE_PEER_GOSSIP_SKIPHANDSHAKE=true,
CORE_PEER_TLS_ENABLED=true,
CORE_PEER_TLS_CERT_FILE=/etc/hyperledger/fabric/tls/server.crt,
CORE_PEER_TLS_KEY_FILE=/etc/hyperledger/fabric/tls/server.key,
CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/tls/ca.crt,
GODEBUG=netdns=go,
]
image: hyperledger/fabric-peer:1.4.12
networks: [celloNet]
ports: ["30004:7051", "30005:7052"]
volumes:
[
"/var/run/:/var/run/",
"../crypto-config/peerOrganizations/org3.example.com/peers/peer0.org3.example.com/msp:/etc/hyperledger/fabric/msp",
"../crypto-config/peerOrganizations/org3.example.com/peers/peer0.org3.example.com/tls:/etc/hyperledger/fabric/tls",
]
version: "3.2" |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sorry, my English is very bad so I translate my word to English using DeepL and put Chinese word below.
Hyperledger Fabric v1.4, cello v0.9.0-h3c, AlmaLinux 8.7
Hello, When I follow this tutorial and cello's docs and get to the step of creating the network, the node starts successfully, but the logs always show a TLS handshake failure. This is the error log for the orderer node:
大家好，当我按照这份教程和cello官方的文档，到创建网络这一步节点启动成功了，但是日志里总是会显示TLS握手失败。这是orderer节点的报错日志：
This is the error log for the peer node:
这是peer节点的报错日志：
Where 172.24.0.1 is the gateway address in the celloNet network created by docker(or cello perhaps).
其中，172.24.0.1是docker创建的celloNet网络中网关地址。
My question is, why is it that if I follow the tutorial step by step, it still reports a TLS handshake failure? Is this "TLS Handshake Failure" a failure to connect between nodes or a failure to connect to cello? What should I do about it? Does this affect the secure communication of the blockchain network?
我的疑问是，为什么完全按照教程一步步走还是会报TLS握手失败？这个“TLS握手失败”是节点之间连接失败还是与cello连接失败？我应该如何处理？这会影响到区块链网络的安全通信吗？
My guess is that if it's a connection failure between nodes, the logs of each node should show a peer's ip, but all the logs of all the nodes show 172.24.0.1, which is the gateway address of celloNet network, so what does it mean?
我的猜想是，如果是节点之间连接失败，应该各节点的日志报错会显示节点的ip，但所有节点的日志报错都显示的是172.24.0.1，这是celloNet网络的网关地址，它意味着什么？
The text was updated successfully, but these errors were encountered: