fabric sdk : org.hyperledger.fabric.sdk.exception.ProposalException
docker logs -f peer0.org1.xxx.com
2019-01-18 02:05:56.121 UTC [gossip/discovery] periodicalSendAlive -> DEBU a639 Sleeping 5s
2019-01-18 02:05:56.533 UTC [core/comm] ServerHandshake -> ERRO a63a TLS handshake failed with error tls: first record does not look like a TLS handshake {"server": "PeerServer", "remote address": "172.19.68.252:50515"}
2019-01-18 02:05:56.580 UTC [core/comm] ServerHandshake -> ERRO a63b TLS handshake failed with error tls: first record does not look like a TLS handshake {"server": "PeerServer", "remote address": "172.19.68.252:50516"}
error output below:
org.hyperledger.fabric.sdk.exception.ProposalException:
org.hyperledger.fabric.sdk.exception.ProposalException: Channel yzchannel1 failed proposal on peer peer0 org.hyperledger.fabric.sdk.exception.TransactionException: org.hyperledger.fabric.sdk.exception.ProposalException: getConfigBlock for channel yzchannel1 failed with peer peer0. Status FAILURE, details: Channel Channel{id: 1, name: yzchannel1} Sending proposal with transaction:
f446b7e44307a9283f57c666f23ba2948030190a5628fb6378413d63f3f482ad to Peer{ id: 3, name: peer0, channelName: yzchannel1, url: grpc://172.19.101.52:7051} failed because of: gRPC failure=Status{code=UNKNOWN, description=access denied: channel [yzchannel1] creator org [Org1MSP], cause=null}
cause analysis:
the peer node setup TLS,like this:
/opt/gopath/src/github.com/hyperledger/fabric/examples/e2e_cli/base/peer-base.yaml
version: '2'
services:
peer-base:
image: hyperledger/fabric-peer
environment:
- CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
# the following setting starts chaincode containers on the same
# bridge network as the peers
# https://docs.docker.com/compose/networking/
- CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=e2e_cli_default
#- CORE_LOGGING_LEVEL=ERROR
- CORE_LOGGING_LEVEL=DEBUG
- CORE_PEER_TLS_ENABLED=true
- CORE_PEER_GOSSIP_USELEADERELECTION=true
- CORE_PEER_GOSSIP_ORGLEADER=false
- CORE_PEER_PROFILE_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
working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
command: peer node start
problem is here,now,we just modify it to false.
- CORE_PEER_TLS_ENABLED=false
for other files,so did this.
相關文章
- Hyperledger Fabric 智慧合約開發及 fabric-sdk-go/fabric-gateway 使用示例GoGateway
- HyperLedger/Fabric SDK使用Docker容器映象快Docker
- Fabric進階(三)—— 使用SDK動態增加組織
- 【乾貨乾貨】hyperledger fabric 之動態新增組織/修改配置 (Fabric-java-sdk) 下Java
- Hyperledger fabric-SDK-GO客戶端開發篇(六)Go客戶端
- DHorse改用fabric8的SDK與k8s叢集互動K8S
- Hyperledger Fabric(Hyperledger Fabric模型)模型
- fabric MSP 和 fabric-ca
- 【Hyperledger Fabric】Fabric 2.2 手動安裝
- fabric案例
- Hyperledger Fabric 部署
- linux搭建FabricLinux
- Fabric 1.0原始碼分析(14) flogging(Fabric日誌系統)原始碼
- Hyperledger Fabric 核心概念
- 2.01 hyperledger fabric概念
- js fabric 學習JS
- IBM-fabric chaincodeIBMAI
- 【Azure微服務 Service Fabric 】使用az命令建立Service Fabric叢集微服務
- Fabric開發(三) Ubuntu20.04.1快速搭建Fabric1.4.3 (排雷版)Ubuntu
- Fabric 1.0原始碼分析(45)gRPC(Fabric中註冊的gRPC Service)原始碼RPC
- Fabric 1.0原始碼分析(47)Fabric 1.0.4 go程式碼量統計原始碼Go
- fabric執行記錄
- Kubernetes fabric8 JavaAPIJavaAPI
- Service Fabric是什麼?
- 2.02 hyperledger fabric入門
- 2.08 hyperledger fabric完整案例
- fabric資料持久化持久化
- Hyperledger Fabric(分類賬)
- fabric 目錄結構
- Hyperledger Fabric on SAP Cloud PlatformCloudPlatform
- 【Android SDK】在命令列管理Android SDKAndroid命令列
- Python Fabric ssh 配置解讀Python
- 2.04 hyperledger fabric共識排序排序
- 2.06 hyperledger fabric智慧合約
- 2.07 hyperledger fabric鏈碼案例
- Hyperledger Fabric 2.0 Alpha釋出了!
- Fabric架構演變之路架構
- Fabric CA 配置與應用