Blockchain createchannel container never completed

[thecreighton]

Hey!

I've tried multiple times to get my sample Blockchain network setup, but I never get through all of the steps successfully. I've tried to do this locally and onto Bluemix, but I am still not having much luck. The stage I'm currently stuck at is as follows:

• export Kubernetes config
• run the create_all.sh script
• 'Waiting for createchannel container to be Completed' is repeated over and over again. I've left this for half an hour and it just keeps printing the same log to my terminal.

How do I get past this step?

Thanks,

Steve

[mrshah-at-ibm]

Looks like the createchannel pod is erroring out.

Can you please provide the logs for the containers in createchannel pod?
kubectl logs createchannel createchanneltx
kubectl logs createchannel createchannel

[thecreighton]

It's coming back with:

The connection to the server localhost:8080 was refused - did you specify the right host or port?

[mrshah-at-ibm]

@thecreighton it is because you might have opened a new terminal or lost the exported KUBECONFIG.

Can you run bx cs cluster-config blockchain and execute the export command that it returns?

[thecreighton]

Thanks, here's the output:

2017-10-12 13:33:41.693 UTC [msp] GetLocalMSP -> DEBU 001 Returning existing local MSP
2017-10-12 13:33:41.693 UTC [msp] GetDefaultSigningIdentity -> DEBU 002 Obtaining default signing identity
2017-10-12 13:33:41.696 UTC [channelCmd] InitCmdFactory -> INFO 003 Endorser and orderer connections initialized
2017-10-12 13:33:41.697 UTC [msp] GetLocalMSP -> DEBU 004 Returning existing local MSP
2017-10-12 13:33:41.697 UTC [msp] GetDefaultSigningIdentity -> DEBU 005 Obtaining default signing identity
2017-10-12 13:33:41.697 UTC [msp] GetLocalMSP -> DEBU 006 Returning existing local MSP
2017-10-12 13:33:41.697 UTC [msp] GetDefaultSigningIdentity -> DEBU 007 Obtaining default signing identity
2017-10-12 13:33:41.697 UTC [msp/identity] Sign -> DEBU 008 Sign: plaintext: 0A8C060A074F7267314D53501280062D...53616D706C65436F6E736F727469756D
2017-10-12 13:33:41.697 UTC [msp/identity] Sign -> DEBU 009 Sign: digest: 16F97E51F39B1A903F5095E3B483CF9E80077F4B9A17CBFF17915852C428A669
2017-10-12 13:33:41.697 UTC [msp] GetLocalMSP -> DEBU 00a Returning existing local MSP
2017-10-12 13:33:41.697 UTC [msp] GetDefaultSigningIdentity -> DEBU 00b Obtaining default signing identity
2017-10-12 13:33:41.697 UTC [msp] GetLocalMSP -> DEBU 00c Returning existing local MSP
2017-10-12 13:33:41.697 UTC [msp] GetDefaultSigningIdentity -> DEBU 00d Obtaining default signing identity
2017-10-12 13:33:41.697 UTC [msp/identity] Sign -> DEBU 00e Sign: plaintext: 0AC2060A1408021A0608B5DEFDCE0522...6C8678F99F0DAF269A50EB7DB5E241D2
2017-10-12 13:33:41.697 UTC [msp/identity] Sign -> DEBU 00f Sign: digest: 1C77A65D6ABAA3E610C5D6FBBD6926965BC7F33CFF6994DA1E7CD68E50E1E59A
Error: Got unexpected status: BAD_REQUEST

[mrshah-at-ibm]

So something went wrong, maybe the shared folder was not wiped clean before starting?
./delete_all.sh followed by ./create_all.sh should help.

But, before you do that, we might want to look at the orderer logs which will tell you why the request was bad..

1. Get the name of the orderer pod - kubectl get pods -a
2. Get the logs of the orderer pod - kubectl logs <pod name>

*. Single command:
kubectl get pods -a | grep orderer | awk '{print $1}' | xargs kubectl logs

I suspect it is because of a bad certificate (ie. certificate generated in the previous run).

[thecreighton]

Quite a lot logged out this time, I trimmed it to logs from this afternoon:

NAME READY STATUS RESTARTS AGE
blockchain-ca-3210138908-r11c0 1/1 Running 0 2d
blockchain-orderer-3391730910-t61d0 1/1 Running 0 2d
blockchain-org1peer1-2610843264-b1jrf 1/1 Running 0 2d
blockchain-org2peer1-3238671870-tv0r6 1/1 Running 0 2d
createchannel 0/2 Error 0 45m
utils 0/3 Completed 0 2d

2017-10-12 13:33:41.698 UTC [orderer/main] Deliver -> DEBU 91a Starting new Deliver handler
2017-10-12 13:33:41.699 UTC [orderer/common/deliver] Handle -> DEBU 91b Starting new deliver loop
2017-10-12 13:33:41.699 UTC [orderer/common/deliver] Handle -> DEBU 91c Attempting to read seek info message
2017-10-12 13:33:41.701 UTC [orderer/main] Broadcast -> DEBU 91d Starting new Broadcast handler
2017-10-12 13:33:41.701 UTC [orderer/common/broadcast] Handle -> DEBU 91e Starting new broadcast loop
2017-10-12 13:33:41.701 UTC [orderer/common/broadcast] Handle -> DEBU 91f Preprocessing CONFIG_UPDATE
2017-10-12 13:33:41.701 UTC [orderer/configupdate] Process -> DEBU 920 Processing channel reconfiguration request for channel channel1
2017-10-12 13:33:41.702 UTC [common/configtx] addToMap -> DEBU 921 Adding to config map: [Groups] /Channel
2017-10-12 13:33:41.702 UTC [common/configtx] addToMap -> DEBU 922 Adding to config map: [Groups] /Channel/Application
2017-10-12 13:33:41.702 UTC [common/configtx] addToMap -> DEBU 923 Adding to config map: [Groups] /Channel/Application/Org2MSP
2017-10-12 13:33:41.702 UTC [common/configtx] addToMap -> DEBU 924 Adding to config map: [Groups] /Channel/Application/Org1MSP
2017-10-12 13:33:41.702 UTC [common/configtx] addToMap -> DEBU 925 Adding to config map: [Values] /Channel/Consortium
2017-10-12 13:33:41.702 UTC [orderer/common/broadcast] Handle -> WARN 926 Rejecting CONFIG_UPDATE because: Error authorizing update: Error validating ReadSet: Readset expected key [Groups] /Channel/Application at version 0, but got version 1
2017-10-12 13:33:41.702 UTC [orderer/main] func1 -> DEBU 927 Closing Broadcast stream
2017-10-12 13:33:41.706 UTC [orderer/common/deliver] Handle -> WARN 928 Error reading from stream: rpc error: code = Canceled desc = context canceled
2017-10-12 13:33:41.706 UTC [orderer/main] func1 -> DEBU 929 Closing Deliver stream

Will give delete_all a shot now.

[thecreighton]

All good, thanks for your help!

[dontAskVI]

'Waiting for createchannel container to be Completed' is repeated over and over again. I've left this for half an hour and it just keeps printing the same log to my terminal.

I am having the same issue.
Command kubectl logs createchannel createchanneltx gives me:

/shared
configtx.yaml
crypto-config
status_cryptogen_complete
2019-02-02 16:48:03.085 UTC [common/tools/configtxgen] main -> INFO 001 Loading configuration
2019-02-02 16:48:03.502 UTC [common/tools/configtxgen/localconfig] Load -> PANI 002 Could not find profile:  TwoOrgsChannel
2019-02-02 16:48:03.502 UTC [common/tools/configtxgen] func1 -> ERRO 003 Could not find profile:  TwoOrgsChannel. Please make sure that FABRIC_CFG_PATH or --configPath is set to a path which contains configtx.yaml with the specified profile

How to set FABRIC_CFG_PATH or --configPath so they contain configtx.yaml with the specified profile?

Tried to delete with ./delete_all.sh -i and create again with ./create_all.sh,but nothing really changed.

Command kubectl logs createchannel createchannel returns Waiting for channeltx.

Also command cat fabric-cluster.yml shows that the file is empty.