search

IBM / blockchain-network-on-kubernetes

Demonstrates the steps involved in setting up your business network on Hyperledger Fabric using Kubernetes APIs on IBM Cloud Kubernetes Service.
https://developer.ibm.com/patterns/deploy-hyperledger-fabric-network-on-ibm-cloud/
Apache License 2.0
316 stars 182 forks source link

peer channel create job just hangs forever for fabric 1.0.4 and gives error on 1.1.0 and later... #7

Closed prabhatsharma closed 6 years ago

prabhatsharma commented 6 years ago

peer channel create just hangs forever for fabric 1.0.4 and gives error on 1.1.0 and later...

2018-05-23 19:18:52.118 UTC [msp] GetLocalMSP -> DEBU 001 Returning existing local MSP 2018-05-23 19:18:52.118 UTC [msp] GetDefaultSigningIdentity -> DEBU 002 Obtaining default signing identity 2018-05-23 19:18:52.120 UTC [channelCmd] InitCmdFactory -> INFO 003 Endorser and orderer connections initialized 2018-05-23 19:18:52.121 UTC [msp] GetLocalMSP -> DEBU 004 Returning existing local MSP 2018-05-23 19:18:52.121 UTC [msp] GetDefaultSigningIdentity -> DEBU 005 Obtaining default signing identity 2018-05-23 19:18:52.122 UTC [msp] GetLocalMSP -> DEBU 006 Returning existing local MSP 2018-05-23 19:18:52.122 UTC [msp] GetDefaultSigningIdentity -> DEBU 007 Obtaining default signing identity 2018-05-23 19:18:52.122 UTC [msp/identity] Sign -> DEBU 008 Sign: plaintext: 0A9E060A074F7267314D53501292062D...53616D706C65436F6E736F727469756D 2018-05-23 19:18:52.122 UTC [msp/identity] Sign -> DEBU 009 Sign: digest: 70ABD09EB62D294FEDB727E4DBBFF9837F5ECC5A0D6180340931908C91536084 2018-05-23 19:18:52.122 UTC [msp] GetLocalMSP -> DEBU 00a Returning existing local MSP 2018-05-23 19:18:52.122 UTC [msp] GetDefaultSigningIdentity -> DEBU 00b Obtaining default signing identity 2018-05-23 19:18:52.122 UTC [msp] GetLocalMSP -> DEBU 00c Returning existing local MSP 2018-05-23 19:18:52.122 UTC [msp] GetDefaultSigningIdentity -> DEBU 00d Obtaining default signing identity 2018-05-23 19:18:52.122 UTC [msp/identity] Sign -> DEBU 00e Sign: plaintext: 0AD4060A1408021A06089CFD96D80522...4B9F7EAB5AB343105BEAD649C93DF0C1 2018-05-23 19:18:52.122 UTC [msp/identity] Sign -> DEBU 00f Sign: digest: 076AC02346FBC2BAE90236DBBEDF4607FB1A12F7FB8CC433F683CE1E53790126 Error: rpc error: code = Unavailable desc = transport is closing 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

alejandrolr commented 6 years ago

I have a similar issue, I've tried to update all images to v1.1.0 and it doesn't work (v1.0.4 worked for me). My problem is caused after joining the peer to the created channel. This is my log:


2018-05-28 18:17:31.561 UTC [msp] GetDefaultSigningIdentity -> DEBU 002 Obtaining default signing identity
2018-05-28 18:17:31.564 UTC [channelCmd] InitCmdFactory -> INFO 003 Endorser and orderer connections initialized
2018-05-28 18:17:31.565 UTC [msp/identity] Sign -> DEBU 004 Sign: plaintext: 0A9C070A5C08011A0C08BB8FB1D80510...BC3C01D4E2FA1A080A000A000A000A00
2018-05-28 18:17:31.565 UTC [msp/identity] Sign -> DEBU 005 Sign: digest: 5ADD54DDD3B3FF34DC14810296180CB2B08F5C2D6E6F2EE5BD9D84D9ABD32F36
2018-05-28 18:17:31.643 UTC [grpc] Printf -> DEBU 006 transport: http2Client.notifyError got notified that the client transport was broken EOF.
Error: proposal failed (err: rpc error: code = Unavailable desc = transport is closing)
Usage:
  peer channel join [flags]

Flags:
  -b, --blockpath string   Path to file containing genesis block

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

root@blockchain-org1peer1-7c84c7d78f-gcxds:/# command terminated with exit code 137```

And the pod dies...
maheshwarishikha commented 6 years ago

Yes, I also faced issue while upgrading to 1.1. Will check it out.

shyrazkhan commented 6 years ago

I also faced issue while upgrading to 1.1.0 ... JoinChannel doesn't work.

maheshwarishikha commented 6 years ago

I modified the following parameter in peersDeployment.yaml for all peers.

You can also check once if its the same with you as well. Or luckily we find any solution...:)

shyrazkhan commented 6 years ago

Yes, I also faced same chaincode instantiation issue after changed the parameter value.

maheshwarishikha commented 6 years ago

Finally it is working. :) Check it out -- git clone --branch branch-1.1 https://github.com/IBM/blockchain-network-on-kubernetes.git

Let me know if any issue. Accordingly will merge this in master branch.

alejandrolr commented 6 years ago

Hi! @maheshwarishikha, I've seen that you have removed the CAs.yamls and configured it by default. Was that the problem?

maheshwarishikha commented 6 years ago

@alejandrolr No, that was not the problem. I realized that org's CA I was not using so need to delete that. Then I just changed the CA to the command line instead of yaml. Did this code work for you?

maheshwarishikha commented 6 years ago

@prabhatsharma , @shyrazkhan - As you have faced issue while setting 1.1 fabric network on Kubernetes, please check once with branch-1.1 code - git clone --branch branch-1.1 https://github.com/IBM/blockchain-network-on-kubernetes.git

Let me know if it works or if any issue. Accordingly I'll merge it to master branch.

maheshwarishikha commented 6 years ago

I will upgrade master repo for the same. Closing the issue now. Thanks.