Fabric service split to multiple servers
#1
我想分割所有的服务,但我还没有找到合适的教程来请求每个人的帮助。
Reply
#2
I don't speak mandarin but I translated this message and I believe you are asking how to deploy a fabric network among multiple organizations. If that is what you are asking, here is a tutorial.
Reply
#3
Yes, I just understood the fabric. I want to deploy multiple organizations and multiple nodes on multiple machines. There are 5 ABCDE machines. The A machine deploys the orderer, and the rest of the BCDE deploys peer nodes. I now have a problem. At node E, I passed docker-compose -f docker-compose-peer3.yaml up -d. It prompts Error creating GRPC server: listen tcp 192.168.1.5:7052: bind: cannot assign requested address I searched Some information does not solve my problem.

I am not very clear how couchdb is separated. Peer how to call couchdb。 I hope someone could help me ,thanks a lot.
Reply
#4
What OS are you running the nodes on and what version of Fabric/Composer are you using?
Reply
#5
The following is my software version
CentOS Linux release 7.4.1708 (Core) 3.10.0-693.21.1.el7.x86_64
Docker-ce Server Version: 18.03.0-ce
docker-compose version 1.20.0, build ca8d3c6
go1.10.1.linux-amd64
git version 1.8.3.1
node-v8.11.1


The following is my software version. In addition, I encountered the latest problem. I tried to use the docker stop $ (docker ps -aq) && docker rm -f $ (docker ps -aq) to clean up the network, and again try to encounter the error is identical.






+ peer channel create -o orderer.zatgo.net:7050 -c mychannel -f ./channel-artifacts/channel.tx --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/zatgo.net/orderers/orderer.zatgo.net/msp/tlscacerts/tlsca.zatgo.net-cert.pem
+ res=1
+ set +x
2018-05-04 13:34:48.583 CST [msp] GetLocalMSP -> DEBU 001 Returning existing local MSP
2018-05-04 13:34:48.583 CST [msp] GetDefaultSigningIdentity -> DEBU 002 Obtaining default signing identity
2018-05-04 13:34:48.590 CST [channelCmd] InitCmdFactory -> INFO 003 Endorser and orderer connections initialized
2018-05-04 13:34:48.591 CST [msp] GetLocalMSP -> DEBU 004 Returning existing local MSP
2018-05-04 13:34:48.591 CST [msp] GetDefaultSigningIdentity -> DEBU 005 Obtaining default signing identity
2018-05-04 13:34:48.592 CST [msp] GetLocalMSP -> DEBU 006 Returning existing local MSP
2018-05-04 13:34:48.592 CST [msp] GetDefaultSigningIdentity -> DEBU 007 Obtaining default signing identity
2018-05-04 13:34:48.592 CST [msp/identity] Sign -> DEBU 008 Sign: plaintext: 0AAE060A074F7267314D535012A2062D...53616D706C65436F6E736F727469756D
2018-05-04 13:34:48.592 CST [msp/identity] Sign -> DEBU 009 Sign: digest: AD964EEB3FB2E2BDA9C1C2D93A09963AFA0E19C262920F7F1162A326AD37B3B1
2018-05-04 13:34:48.592 CST [msp] GetLocalMSP -> DEBU 00a Returning existing local MSP
2018-05-04 13:34:48.592 CST [msp] GetDefaultSigningIdentity -> DEBU 00b Obtaining default signing identity
2018-05-04 13:34:48.593 CST [msp] GetLocalMSP -> DEBU 00c Returning existing local MSP
2018-05-04 13:34:48.593 CST [msp] GetDefaultSigningIdentity -> DEBU 00d Obtaining default signing identity
2018-05-04 13:34:48.593 CST [msp/identity] Sign -> DEBU 00e Sign: plaintext: 0AE5060A1508021A0608F8E1AFD70522...5B60ECA0DBC59E0DA1F288571D32B3FF
2018-05-04 13:34:48.593 CST [msp/identity] Sign -> DEBU 00f Sign: digest: 5BF150FED861202503D928B3D22111A13D29D31A13C17DAE23E427C6A159230B
Error: got unexpected status: BAD_REQUEST -- error authorizing update: error validating ReadSet: readset expected key [Group] /Channel/Application at version 0, but got version 1
Usage:
peer channel create [flags]

Flags:
-c, --channelID string In case of a newChain command, the channel ID to create.
-f, --file string Configuration transaction file generated by a tool such as configtxgen for submitting to orderer
-t, --timeout int Channel creation timeout (default 5)

Global Flags:
--cafile string Path to file containing PEM-encoded trusted certificate(s) for the ordering endpoint
--certfile string Path to file containing PEM-encoded X509 public key to use for mutual TLS communication with the orderer endpoint
--clientauth Use mutual TLS when communicating with the orderer endpoint
--keyfile string Path to file containing PEM-encoded private key to use for mutual TLS communication with the orderer endpoint
--logging-level string Default logging level and overrides, see core.yaml for full syntax
-o, --orderer string Ordering service endpoint
--ordererTLSHostnameOverride string The hostname override to use when validating the TLS connection to the orderer.
--tls Use TLS when communicating with the orderer endpoint
-v, --version Display current version of fabric peer server

!!!!!!!!!!!!!!! Channel creation failed !!!!!!!!!!!!!!!!
========= ERROR !!! FAILED to execute End-2-End Scenario ===========

Hyperledger Fabric 1.1
Reply
#6
Quote:Error: got unexpected status: BAD_REQUEST -- error authorizing update: error validating ReadSet: readset expected key [Group] /Channel/Application at version 0, but got version 1
Sounds like the channel you are trying to create already exists. Have you already taken a look and given these solutions a try? https://github.com/yeasy/docker-compose-files/issues/51
Reply
#7
It is not the problem of reminent containers, it seems. I have removed all the containers. And still got this message: Error: got unexpected status: BAD_REQUEST -- error authorizing update: error validating ReadSet: readset expected key [Group] /Channel/Application at version 0, but got version 1
Reply
#8
Hmm, strange. Seems to be a common issue. Maybe try this:

Quote:Start with a fresh config and new channel name. Also, try passing the -t intflag in peer channel create command. Might be an issue that the command is timing before generating the channel genesis block.
Reply
#9
-t, --timeout int Channel creation timeout (default 5)


I'm from China. I have no effect with -t intflag. The problem still exists. What should I do next? If it is convenient if you can leave your WeChat for further communication.
Reply
#10
How are you separating the different nodes, with containerization with docker or different machines?

I don't have a WeChat, but I can send you my Skype.
Reply