Closed methuz closed 6 years ago
Thanks @methuz ! I will updated it very soon!
Updated :+1: and thanks again:)
hello I am still getting the same error
Error: got unexpected status: SERVICE_UNAVAILABLE -- will not enqueue, consenter for this channel hasn't started yet !!!!!!!!!!!!!!! Channel creation failed !!!!!!!!!!!!!!!! ========= ERROR !!! FAILED to execute End-2-End Scenario ===========
@sngvahmed you might want to increase more delay
@keenkit you're welcome
@methuz
I run ./byfn.sh up -t 30 -d 1000
and I am still getting the same error in ubuntu server and also in VirtualBox ubuntu server
@sngvahmed , can you check the logs from kafka / zookeeper or orderer to see if any obvious error?
@keenkit it work with me now thanks
@sngvahmed what did you do to get it working can you please let us know. thanks
@httran13 I increased timeout And delay also I changed the Kafka container name when I revert it to an original name as the example.com it work Check kafka and couchdb logs maybe the problem inside it
i met this question,this the orderer logs:
2018-12-03 13:49:26.710 UTC [orderer/consensus/kafka/sarama] Open -> DEBU 27b ClientID is the default of 'sarama', you should consider setting it to something application-specific. 2018-12-03 13:49:26.710 UTC [orderer/consensus/kafka/sarama] func1 -> DEBU 27c client/metadata fetching metadata for all topics from broker kafka0.example.com:9092 2018-12-03 13:49:26.711 UTC [orderer/consensus/kafka/sarama] withRecover -> DEBU 27d Failed to connect to broker kafka0.example.com:9092: dial tcp 172.21.0.10:9092: connect: connection refused 2018-12-03 13:49:26.711 UTC [orderer/consensus/kafka/sarama] func1 -> DEBU 27e client/metadata got error from broker while fetching metadata: dial tcp 172.21.0.10:9092: connect: connection refused 2018-12-03 13:49:26.711 UTC [orderer/consensus/kafka/sarama] func1 -> DEBU 27f client/metadata no available broker to send metadata request to 2018-12-03 13:49:26.711 UTC [orderer/consensus/kafka/sarama] tryRefreshMetadata -> DEBU 280 client/brokers resurrecting 4 dead seed brokers 2018-12-03 13:49:26.713 UTC [orderer/consensus/kafka/sarama] tryRefreshMetadata -> DEBU 281 client/metadata retrying after 250ms... (2 attempts remaining) 2018-12-03 13:49:26.965 UTC [orderer/consensus/kafka/sarama] Open -> DEBU 282 ClientID is the default of 'sarama', you should consider setting it to something application-specific. 2018-12-03 13:49:26.965 UTC [orderer/consensus/kafka/sarama] func1 -> DEBU 283 client/metadata fetching metadata for all topics from broker kafka2.example.com:9092 2018-12-03 13:49:26.966 UTC [orderer/consensus/kafka/sarama] withRecover -> DEBU 284 Failed to connect to broker kafka2.example.com:9092: dial tcp 172.21.0.11:9092: connect: connection refused 2018-12-03 13:49:26.966 UTC [orderer/consensus/kafka/sarama] func1 -> DEBU 285 client/metadata got error from broker while fetching metadata: dial tcp 172.21.0.11:9092: connect: connection refused 2018-12-03 13:49:26.967 UTC [orderer/consensus/kafka/sarama] Open -> DEBU 286 ClientID is the default of 'sarama', you should consider setting it to something application-specific.
at the same time ,i noticed that errors:
2018-12-03 13:49:33.598 UTC [orderer/common/broadcast] Handle -> WARN 4a4 [channel: mychannel] Rejecting broadcast of message from 172.21.0.15:35802 with SERVICE_UNAVAILABLE: rejected by Consenter: will not enqueue, consenter for this channel hasn't started yet 2018-12-03 13:49:33.598 UTC [orderer/common/server] func1 -> DEBU 4a5 Closing Broadcast stream 2018-12-03 13:49:33.612 UTC [common/deliver] Handle -> WARN 4a6 Error reading from 172.21.0.15:35800: rpc error: code = Canceled desc = context canceled
should i do ?
I had Service_Unavailble error on the first run but after I increase timeout and delay I can run it successfully. So you might want to update Readme.md with this information.
./byfn.sh up -t 30 -d 10