hope all of you are doing well!
Got some issues with Fabric peers when starting a network (5Orgs (1Orderer), 3 peers/org, 1 channel for all of them, RAFT & TLS). Basically when executing peer channel create ..., I get the following logs in the bash terminal
============ Creating 'my-channel1' on Inovafil/peer0 ==============
Creating channel with name (TLS): my-channel1
Orderer: orderer0.group1.orderer.example.com:7030
CORE_PEER_LOCALMSPID: InovafilMSP
CORE_PEER_ADDRESS: peer0.inovafil.example.com:7041
CORE_PEER_MSPCONFIGPATH: /var/hyperledger/cli/crypto/users/Admin@inovafil.example.com/msp
TLS_CA_CERT_PATH is: /var/hyperledger/cli/crypto-orderer/tlsca.orderer.example.com-cert.pem
CORE_PEER_TLS_CERT_FILE: /var/hyperledger/cli/crypto/users/Admin@inovafil.example.com/tls/client.crt
CORE_PEER_TLS_KEY_FILE: /var/hyperledger/cli/crypto/users/Admin@inovafil.example.com/tools/client.key
CORE_PEER_TLS_ROOTCERT_FILE: /var/hyperledger/cli/crypto/users/Admin@inovafil.example.com/tls/ca.crt
2022-12-05 13:39:56.585 UTC 0001 INFO [channelCmd] InitCmdFactory -> Endorser and orderer connections initialized
2022-12-05 13:39:56.885 UTC 0002 INFO [cli.common] roadblock -> Expect block, but got status: &{NOT_FOUND}
2022-12-05 13:39:56.903 UTC 0003 INFO [channelCmd] InitCmdFactory -> Endorser and orderer connections initialized
2022-12-05 13:39:57.258 UTC 0004 INFO [cli.common] readBlock -> Expect block, but got status: &{SERVICE_UNAVAILABLE}
...
2022-12-05 13:39:58.155 UTC 000d INFO [channelCmd] InitCmdFactory -> Endorser and orderer connections initialized
2022-12-05 13:39:58.358 UTC 000e INFO [cli.common] readBlock -> Received block: 0
Error: error getting endorser client for channel: endorser client failed to connect to peer0.inovafil.example.com:7041: failed to create new connection: connection error: desc = "transport: error while dialing: dial tcp 172.23.0.18:7041: connect: connection refused"
Went to the specific peer0.inovafil.example.com:7041 container to check the logs and this is the output on that:
2022-12-05 13:40:40.852 UTC 002d WARN [gossip.discovery] func1 -> Could not connect to Endpoint: peer2.inovafil.example.com:7043", InternalEndpoint: peer2.inovafil.example.com:7043", PKI-ID: <nil>, Metadata: : context deadline exceeded
2022-12-05 13:40:40.854 UTC 002e WARN [gossip.discovery] func1 -> Could not connect to Endpoint: "peer0.inovafil.example.com:7041, InternalEndpoint: "peer0.inovafil.example.com:7041, PKI-ID: <nil>, Metadata: : context deadline exceeded
I've tried adding 30s of timeout for the client to connect, with the -connTimeout 30s flag on the peer channel create command, as well as 30s of channel creation timeout with the flag -t 30s but to no avail. Changing the consensus to solo & no TLS appears to do nothing.
Any clues on what this might be? Thanks in advance!
