Re: Kafka orderer on k8s errors when invoke createchannel cmd


jeroiraz
 

Apologies for sending info of the tool again, but I do think the simple tool (https://github.com/ibm-silvergate/netcomposer) is useful in this case too, as it generates configuration files even when kafka is used for the ordering service. You could use the configuration files directly or compare generated files with yours do figure out if there is a mistake there.

Fragment of the configuration specifying kafka based ordering service is as simple as:

orderer:
    type: "kafka"
    consenters:     3
    kafkaBrokers:   3
    zookeeperNodes: 3


Best regards,
Jero

On Fri, Nov 24, 2017 at 10:34 AM, <281165273@...> wrote:
Hi Yacov,

I used hyperledger/fabric-kafka:x86_64-1.0.0 image and I found a similar issue https://jira.hyperledger.org/browse/FAB-6002. But if I don't set KAFKA_ADVERTISED_HOST_NAME, Kafka replica fetch will failed. attached orderer env.



------------------ Original ------------------
From:  "Yacov Manevich";<YACOVM@...>;
Date:  Fri, Nov 24, 2017 08:27 PM
To:  "葡萄爸爸"<281165273@...>;
Cc:  "hyperledger-fabric@lists.hyperl"<hyperledger-fabric@lists.hyperledger.org>;
Subject:  Re: [Hyperledger-fabric] Kafka orderer on k8s errors when invoke createchannel cmd

what is the kafka version and what version is there in the orderer.yaml file or the orderer env vars?



From:       281165273@...
To:       "hyperledger-fabric@lists.hyperl" <hyperledger-fabric@lists.hyperledger.org>
Date:       24/11/2017 01:35 PM
Subject:        [Hyperledger-fabric] Kafka orderer on k8s errors when invoke create        channel cmd
Sent by:        hyperledger-fabric-bounces@lists.hyperledger.org




Hi guys,

I deployed a 1org 3 orderers kafka based orderer service, when i run create channel cmd in cli pod,
got errors below, I paste one orderer whole log as well. Can anyone help point me out what cause this issue?

cli pod logs:
root@cli-5459fcd8c6-h8585:/opt/gopath/src/github.com/hyperledger/fabric/peer# peer channel create -o orderer2.orgorderer1:7050 -c mychannel -f ./channel-artifacts/channel.tx --tls true --cafile /etc/hyperledger/fabric/orderertls/tlsca.orgorderer1-cert.pem
2017-11-24 11:17:47.891 UTC [msp] GetLocalMSP -> DEBU 001Returning existing local MSP
2017-11-24 11:17:47.891 UTC [msp] GetDefaultSigningIdentity -> DEBU 002Obtaining default signing identity
2017-11-24 11:17:47.901 UTC [channelCmd] InitCmdFactory -> INFO 003 Endorser and orderer connections initialized
2017-11-24 11:17:47.905 UTC [msp] GetLocalMSP -> DEBU 004Returning existing local MSP
2017-11-24 11:17:47.905 UTC [msp] GetDefaultSigningIdentity -> DEBU 005Obtaining default signing identity
2017-11-24 11:17:47.905 UTC [msp] GetLocalMSP -> DEBU 006Returning existing local MSP
2017-11-24 11:17:47.905 UTC [msp] GetDefaultSigningIdentity -> DEBU 007Obtaining default signing identity
2017-11-24 11:17:47.905 UTC [msp/identity] Sign -> DEBU 008Sign: plaintext: 0ADB050A074F7267314D535012CF052D...53616D706C65436F6E736F727469756D
2017-11-24 11:17:47.905 UTC [msp/identity] Sign -> DEBU 009Sign: digest: 263F5B3CB8017EB542049975EE4ACE7CEA86E1C1BC5F2E8789188F80F2C830BC
2017-11-24 11:17:47.906 UTC [msp] GetLocalMSP -> DEBU 00aReturning existing local MSP
2017-11-24 11:17:47.906 UTC [msp] GetDefaultSigningIdentity -> DEBU 00bObtaining default signing identity
2017-11-24 11:17:47.906 UTC [msp] GetLocalMSP -> DEBU 00cReturning existing local MSP
2017-11-24 11:17:47.906 UTC [msp] GetDefaultSigningIdentity -> DEBU 00dObtaining default signing identity
2017-11-24 11:17:47.906 UTC [msp/identity] Sign -> DEBU 00eSign: plaintext: 0A92060A1508021A0608DBFFDFD00522...5E656DF3C6FFCD00B2BD9C70C5F0960E
2017-11-24 11:17:47.906 UTC [msp/identity] Sign -> DEBU 00fSign: digest: CF2EA927A9E33F694D22AC3B05E37F23F64E6617A5FFE90C382088DA0486F788
Error: Got unexpected status: SERVICE_UNAVAILABLE
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
      --logging-level string       Default logging level and overrides, see core.yaml for full syntax
  -o, --orderer string             Ordering service endpoint
      --test.coverprofile string   Done (default "coverage.cov")
      --tls                        Use TLS when communicating with the orderer endpoint
  -v, --version                    Display current version of fabric peer server



orderer logs:

[[36m2017-11-24 11:17:47.956 UTC [orderer/kafka] Enqueue -> DEBU 4c4^[[0m [channel: testchainid] Enqueueing envelope...
^[[33m2017-11-24 11:17:47.956 UTC [orderer/kafka] Enqueue -> WARN 4c5^[[0m [channel: testchainid] Will not enqueue, consenter for this channel hasn't started yet
^[[36m2017-11-24 11:17:47.956 UTC [orderer/main] func1 -> DEBU 4c6^[[0m Closing Broadcast stream
^[[33m2017-11-24 11:17:47.958 UTC [orderer/common/deliver] Handle -> WARN 4c7^[[0m Error reading from stream: rpc error: code = Canceled desc = context canceled[attachment "log.txt" deleted by Yacov Manevich/Haifa/IBM] _______________________________________________
Hyperledger-fabric mailing list
Hyperledger-fabric@lists.hyperledger.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.hyperledger.org_mailman_listinfo_hyperledger-2Dfabric&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=IUHCXpRg0Ta0HOuOwvu5BufWYJnhYZ2e6aZxCsJEf2E&m=zpnvOZ4caMOlsgUsvFnoefm2geR38KVcN0A48KxTlKM&s=BuhYpe8mU9mvm06muQrVYC-d582-PjNTQudg5xsENT0&e=




_______________________________________________
Hyperledger-fabric mailing list
Hyperledger-fabric@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-fabric


Join fabric@lists.hyperledger.org to automatically receive all group messages.