will-hu-0
commented
6 years ago Hey @anirudhkabi, thanks for raising the issue for it. My assumption is that: (1) Not sure what's your OS? From my end it runs well under Ubuntu (16.04) and Travis CI (Ubuntu as well). (2) Check your local port is being used, check 9092 and 2181 by
netstat -nlp|grep 2181
sudo lsof -i:9092Kill or close them if they are being used.
If all the steps above is okay, check the following debug steps (manually).
I will provide some steps to try to understand your local issue, hopefully you may follow it to provide valuable information. Because we will debug it by manual script, so...
- Mark the code in byfn.sh by
function networkUp () { ......
sleep 12
docker exec cli scripts/script.sh $CHANNEL_NAME $CLI_DELAY $LANGUAGE $CLI_TIMEOUT
....
2.1 Run the following script in one new console (console1):./byfn.sh up
You will see something in the end like:Creating orderer.example.com ... Creating orderer.example.com ... done Creating cli ... Creating cli ... done
Make sure you see orderer.example.com is done.
2.2 Open another console (console2) to run and see the log from orderer (If you have another tool like kitematic, you do not necessarily run by yourself)docker logs -f orderer.example.com
**BE NOTED**: step2.1 and 2.2 should be running in **parallel** because you need to verify the kafka self-checking log during the starting up of orderer service:... [sarama] 2018/03/04 05:54:48.198800 broker.go:146: Connected to broker at kafka2.example.com:9092 (unregistered) [sarama] 2018/03/04 05:54:48.200471 client.go:397: client/brokers registered new broker #0 at 85ad5b5c61e9:9092 [sarama] 2018/03/04 05:54:48.200486 client.go:397: client/brokers registered new broker #1 at 66abc42c12b7:9092 [sarama] 2018/03/04 05:54:48.200493 client.go:397: client/brokers registered new broker #2 at 45f18a960094:9092 [sarama] 2018/03/04 05:54:48.200500 client.go:397: client/brokers registered new broker #3 at 41b8aba2be14:9092 ... 2018-03-04 05:54:48.214 UTC [orderer/kafka] processMessagesToBlocks -> DEBU 108 [channel: testchainid] Successfully unmarshalled consumed message, offset is 0. Inspecting type... 2018-03-04 05:54:48.214 UTC [orderer/kafka] processConnect -> DEBU 109 [channel: testchainid] It's a connect message - ignoring
3. If all the steps above runs well, let's manually create the channel in the CLI :)
Open a third console (console3) to run
docker exec -it cli bash
Execute:export CHANNEL_NAME=mychannel peer channel create -o orderer.example.com:7050 -c $CHANNEL_NAME -f ./channel-artifacts/channel.tx --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
To see if it is successful?
If not running well, please copy more log from orderer (console2) here let me check it.
If it runs well, I don't know, you might need to trigger the cli by some other way, we may discuss it later after your test result on your local. Thanks.
anirudhkabi
Error: Got unexpected status: SERVICE_UNAVAILABLE Even after increasing CLI_TIMEOUT and CLI_DELAY to 100, the error occurs