cannot elect raft leader #fabric-orderer


famar
 

Hello everyone, i'm trying to start a network with 3 orderers running on 3 different orgs. Orderer's containers start but the leader is not elected.
I have this type of messages in orderer's containers:

orderer1
2022-05-10 07:33:28.112 UTC 00ba INFO [orderer.consensus.etcdraft] campaign -> 1 [logterm: 1, index: 3] sent MsgPreVote request to 3 at term 1 channel=mychannel node=1
orderer2
2022-05-10 07:33:35.630 UTC 066a INFO [orderer.consensus.etcdraft] campaign -> 2 [logterm: 1, index: 3] sent MsgPreVote request to 3 at term 1 channel=mychannel node=2
orderer3
2022-05-10 07:33:38.689 UTC 012d INFO [orderer.consensus.etcdraft] campaign -> 3 [logterm: 1, index: 3] sent MsgPreVote request to 2 at term 1 channel=mychannel node=3

I attach the docker.-compose.yaml and the configtx.yaml.

Can someone help me solve this issue? 
Thanks in advance
 


Yacov
 

Check the logs of the communication infrastructure, by enabling gRPC debug.

From: fabric@... <fabric@...> on behalf of famar <fabrizio.marangio@...>
Sent: Tuesday, May 10, 2022 10:37 AM
To: fabric@... <fabric@...>
Subject: [EXTERNAL] [Hyperledger Fabric] cannot elect raft leader #fabric-orderer
 
Hello everyone, i'm trying to start a network with 3 orderers running on 3 different orgs. Orderer's containers start but the leader is not elected. I have this type of messages in orderer's containers: orderer1 2022-05-10 07:33:28.112 UTC 00ba
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
 
ZjQcmQRYFpfptBannerEnd
Hello everyone, i'm trying to start a network with 3 orderers running on 3 different orgs. Orderer's containers start but the leader is not elected.
I have this type of messages in orderer's containers:

orderer1
2022-05-10 07:33:28.112 UTC 00ba INFO [orderer.consensus.etcdraft] campaign -> 1 [logterm: 1, index: 3] sent MsgPreVote request to 3 at term 1 channel=mychannel node=1
orderer2
2022-05-10 07:33:35.630 UTC 066a INFO [orderer.consensus.etcdraft] campaign -> 2 [logterm: 1, index: 3] sent MsgPreVote request to 3 at term 1 channel=mychannel node=2
orderer3
2022-05-10 07:33:38.689 UTC 012d INFO [orderer.consensus.etcdraft] campaign -> 3 [logterm: 1, index: 3] sent MsgPreVote request to 2 at term 1 channel=mychannel node=3

I attach the docker.-compose.yaml and the configtx.yaml.

Can someone help me solve this issue? 
Thanks in advance
 


famar
 

Thank you very much.
Using the grpc debug i have this log:

2022-05-10 13:09:49.879 UTC [grpc] InfoDepth -> DEBU 04b [core]Subchannel Connectivity change to CONNECTING
2022-05-10 13:09:49.879 UTC [grpc] InfoDepth -> DEBU 04c [core]Subchannel picks a new address "ordererCA1:7050" to connect
2022-05-10 13:09:49.879 UTC [grpc] InfoDepth -> DEBU 04d [core]pickfirstBalancer: UpdateSubConnState: 0xc000ae9180, {CONNECTING <nil>}
2022-05-10 13:09:49.879 UTC [grpc] InfoDepth -> DEBU 04e [core]Channel Connectivity change to CONNECTING
2022-05-10 13:09:49.880 UTC [grpc] WarningDepth -> DEBU 04f [core]grpc: addrConn.createTransport failed to connect to {ordererCA1:7050 ordererCA1:7050 <nil> 0 <nil>}. Err: connection error: desc = "transport: Error while dialing dial tcp 172.24.0.5:7050: connect: connection refused". Reconnecting...
2022-05-10 13:09:49.880 UTC [grpc] InfoDepth -> DEBU 050 [core]Subchannel Connectivity change to TRANSIENT_FAILURE
2022-05-10 13:09:49.880 UTC [grpc] InfoDepth -> DEBU 051 [core]pickfirstBalancer: UpdateSubConnState: 0xc000ae9180, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing dial tcp 172.24.0.5:7050: connect: connection refused"}
2022-05-10 13:09:49.880 UTC [grpc] InfoDepth -> DEBU 052 [core]Channel Connectivity change to TRANSIENT_FAILURE
2022-05-10 13:09:50.139 UTC [grpc] InfoDepth -> DEBU 053 [core]Subchannel Connectivity change to CONNECTING
2022-05-10 13:09:50.139 UTC [grpc] InfoDepth -> DEBU 054 [core]Subchannel picks a new address "ordererCA3:9050" to connect
2022-05-10 13:09:50.139 UTC [grpc] InfoDepth -> DEBU 055 [core]pickfirstBalancer: UpdateSubConnState: 0xc000ae9f50, {CONNECTING <nil>}
2022-05-10 13:09:50.139 UTC [grpc] InfoDepth -> DEBU 056 [core]Channel Connectivity change to CONNECTING
2022-05-10 13:09:50.140 UTC [grpc] WarningDepth -> DEBU 057 [core]grpc: addrConn.createTransport failed to connect to {ordererCA3:9050 ordererCA3:9050 <nil> 0 <nil>}. Err: connection error: desc = "transport: Error while dialing dial tcp 172.24.0.7:9050: connect: connection refused". Reconnecting...
2022-05-10 13:09:50.140 UTC [grpc] InfoDepth -> DEBU 058 [core]Subchannel Connectivity change to TRANSIENT_FAILURE
2022-05-10 13:09:50.140 UTC [grpc] InfoDepth -> DEBU 059 [core]pickfirstBalancer: UpdateSubConnState: 0xc000ae9f50, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing dial tcp 172.24.0.7:9050: connect: connection refused"}
2022-05-10 13:09:50.140 UTC [grpc] InfoDepth -> DEBU 05a [core]Channel Connectivity change to TRANSIENT_FAILURE

So orderers can't connect with each other.
Do you have some advice?
Thanks

Il giorno mar 10 mag 2022 alle ore 14:36 Yacov Manevich <YACOVM@...> ha scritto:
Check the logs of the communication infrastructure, by enabling gRPC debug.

From: fabric@... <fabric@...> on behalf of famar <fabrizio.marangio@...>
Sent: Tuesday, May 10, 2022 10:37 AM
To: fabric@... <fabric@...>
Subject: [EXTERNAL] [Hyperledger Fabric] cannot elect raft leader #fabric-orderer
 
Hello everyone, i'm trying to start a network with 3 orderers running on 3 different orgs. Orderer's containers start but the leader is not elected. I have this type of messages in orderer's containers: orderer1 2022-05-10 07:33:28.112 UTC 00ba
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
 
ZjQcmQRYFpfptBannerEnd
Hello everyone, i'm trying to start a network with 3 orderers running on 3 different orgs. Orderer's containers start but the leader is not elected.
I have this type of messages in orderer's containers:

orderer1
2022-05-10 07:33:28.112 UTC 00ba INFO [orderer.consensus.etcdraft] campaign -> 1 [logterm: 1, index: 3] sent MsgPreVote request to 3 at term 1 channel=mychannel node=1
orderer2
2022-05-10 07:33:35.630 UTC 066a INFO [orderer.consensus.etcdraft] campaign -> 2 [logterm: 1, index: 3] sent MsgPreVote request to 3 at term 1 channel=mychannel node=2
orderer3
2022-05-10 07:33:38.689 UTC 012d INFO [orderer.consensus.etcdraft] campaign -> 3 [logterm: 1, index: 3] sent MsgPreVote request to 2 at term 1 channel=mychannel node=3

I attach the docker.-compose.yaml and the configtx.yaml.

Can someone help me solve this issue? 
Thanks in advance
 


Yacov
 

It's  a connection problem... you need to solve it on your own as it's your environment.

From: Fabrizio Marangio <fabrizio.marangio@...>
Sent: Tuesday, May 10, 2022 4:16 PM
To: Yacov Manevich <YACOVM@...>
Cc: fabric@... <fabric@...>
Subject: [EXTERNAL] Re: [Hyperledger Fabric] cannot elect raft leader #fabric-orderer
 
Thank you very much. Using the grpc debug i have this log: 2022-05-10 13:09:49.879 UTC [grpc] InfoDepth -> DEBU 04b [core]Subchannel Connectivity change to CONNECTING 2022-05-10 13:09:49.879 UTC [grpc] InfoDepth -> DEBU 04c [core]Subchannel
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
 
ZjQcmQRYFpfptBannerEnd
Thank you very much.
Using the grpc debug i have this log:

2022-05-10 13:09:49.879 UTC [grpc] InfoDepth -> DEBU 04b [core]Subchannel Connectivity change to CONNECTING
2022-05-10 13:09:49.879 UTC [grpc] InfoDepth -> DEBU 04c [core]Subchannel picks a new address "ordererCA1:7050" to connect
2022-05-10 13:09:49.879 UTC [grpc] InfoDepth -> DEBU 04d [core]pickfirstBalancer: UpdateSubConnState: 0xc000ae9180, {CONNECTING <nil>}
2022-05-10 13:09:49.879 UTC [grpc] InfoDepth -> DEBU 04e [core]Channel Connectivity change to CONNECTING
2022-05-10 13:09:49.880 UTC [grpc] WarningDepth -> DEBU 04f [core]grpc: addrConn.createTransport failed to connect to {ordererCA1:7050 ordererCA1:7050 <nil> 0 <nil>}. Err: connection error: desc = "transport: Error while dialing dial tcp 172.24.0.5:7050: connect: connection refused". Reconnecting...
2022-05-10 13:09:49.880 UTC [grpc] InfoDepth -> DEBU 050 [core]Subchannel Connectivity change to TRANSIENT_FAILURE
2022-05-10 13:09:49.880 UTC [grpc] InfoDepth -> DEBU 051 [core]pickfirstBalancer: UpdateSubConnState: 0xc000ae9180, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing dial tcp 172.24.0.5:7050: connect: connection refused"}
2022-05-10 13:09:49.880 UTC [grpc] InfoDepth -> DEBU 052 [core]Channel Connectivity change to TRANSIENT_FAILURE
2022-05-10 13:09:50.139 UTC [grpc] InfoDepth -> DEBU 053 [core]Subchannel Connectivity change to CONNECTING
2022-05-10 13:09:50.139 UTC [grpc] InfoDepth -> DEBU 054 [core]Subchannel picks a new address "ordererCA3:9050" to connect
2022-05-10 13:09:50.139 UTC [grpc] InfoDepth -> DEBU 055 [core]pickfirstBalancer: UpdateSubConnState: 0xc000ae9f50, {CONNECTING <nil>}
2022-05-10 13:09:50.139 UTC [grpc] InfoDepth -> DEBU 056 [core]Channel Connectivity change to CONNECTING
2022-05-10 13:09:50.140 UTC [grpc] WarningDepth -> DEBU 057 [core]grpc: addrConn.createTransport failed to connect to {ordererCA3:9050 ordererCA3:9050 <nil> 0 <nil>}. Err: connection error: desc = "transport: Error while dialing dial tcp 172.24.0.7:9050: connect: connection refused". Reconnecting...
2022-05-10 13:09:50.140 UTC [grpc] InfoDepth -> DEBU 058 [core]Subchannel Connectivity change to TRANSIENT_FAILURE
2022-05-10 13:09:50.140 UTC [grpc] InfoDepth -> DEBU 059 [core]pickfirstBalancer: UpdateSubConnState: 0xc000ae9f50, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing dial tcp 172.24.0.7:9050: connect: connection refused"}
2022-05-10 13:09:50.140 UTC [grpc] InfoDepth -> DEBU 05a [core]Channel Connectivity change to TRANSIENT_FAILURE

So orderers can't connect with each other.
Do you have some advice?
Thanks

Il giorno mar 10 mag 2022 alle ore 14:36 Yacov Manevich <YACOVM@...> ha scritto:

Check the logs of the communication infrastructure, by enabling gRPC debug.

From: fabric@... <fabric@...> on behalf of famar <fabrizio.marangio@...>
Sent: Tuesday, May 10, 2022 10:37 AM
To: fabric@... <fabric@...>
Subject: [EXTERNAL] [Hyperledger Fabric] cannot elect raft leader #fabric-orderer
 
Hello everyone, i'm trying to start a network with 3 orderers running on 3 different orgs. Orderer's containers start but the leader is not elected. I have this type of messages in orderer's containers: orderer1 2022-05-10 07:33:28.112 UTC 00ba
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
 
ZjQcmQRYFpfptBannerEnd
Hello everyone, i'm trying to start a network with 3 orderers running on 3 different orgs. Orderer's containers start but the leader is not elected.
I have this type of messages in orderer's containers:

orderer1
2022-05-10 07:33:28.112 UTC 00ba INFO [orderer.consensus.etcdraft] campaign -> 1 [logterm: 1, index: 3] sent MsgPreVote request to 3 at term 1 channel=mychannel node=1
orderer2
2022-05-10 07:33:35.630 UTC 066a INFO [orderer.consensus.etcdraft] campaign -> 2 [logterm: 1, index: 3] sent MsgPreVote request to 3 at term 1 channel=mychannel node=2
orderer3
2022-05-10 07:33:38.689 UTC 012d INFO [orderer.consensus.etcdraft] campaign -> 3 [logterm: 1, index: 3] sent MsgPreVote request to 2 at term 1 channel=mychannel node=3

I attach the docker.-compose.yaml and the configtx.yaml.

Can someone help me solve this issue? 
Thanks in advance
 


famar
 

I understand that it's a connection problem but I can't figure out the source. It's like the ports are closed or there is an active firewall but I'm on a virtual machine and there are no such settings.
Can you give me any advice on how to try to figure out the origin of this connection failure?
Thanks

Il giorno mar 10 mag 2022 alle ore 16:01 Yacov Manevich <YACOVM@...> ha scritto:
It's  a connection problem... you need to solve it on your own as it's your environment.

From: Fabrizio Marangio <fabrizio.marangio@...>
Sent: Tuesday, May 10, 2022 4:16 PM
To: Yacov Manevich <YACOVM@...>
Cc: fabric@... <fabric@...>
Subject: [EXTERNAL] Re: [Hyperledger Fabric] cannot elect raft leader #fabric-orderer
 
Thank you very much. Using the grpc debug i have this log: 2022-05-10 13:09:49.879 UTC [grpc] InfoDepth -> DEBU 04b [core]Subchannel Connectivity change to CONNECTING 2022-05-10 13:09:49.879 UTC [grpc] InfoDepth -> DEBU 04c [core]Subchannel
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
 
ZjQcmQRYFpfptBannerEnd
Thank you very much.
Using the grpc debug i have this log:

2022-05-10 13:09:49.879 UTC [grpc] InfoDepth -> DEBU 04b [core]Subchannel Connectivity change to CONNECTING
2022-05-10 13:09:49.879 UTC [grpc] InfoDepth -> DEBU 04c [core]Subchannel picks a new address "ordererCA1:7050" to connect
2022-05-10 13:09:49.879 UTC [grpc] InfoDepth -> DEBU 04d [core]pickfirstBalancer: UpdateSubConnState: 0xc000ae9180, {CONNECTING <nil>}
2022-05-10 13:09:49.879 UTC [grpc] InfoDepth -> DEBU 04e [core]Channel Connectivity change to CONNECTING
2022-05-10 13:09:49.880 UTC [grpc] WarningDepth -> DEBU 04f [core]grpc: addrConn.createTransport failed to connect to {ordererCA1:7050 ordererCA1:7050 <nil> 0 <nil>}. Err: connection error: desc = "transport: Error while dialing dial tcp 172.24.0.5:7050: connect: connection refused". Reconnecting...
2022-05-10 13:09:49.880 UTC [grpc] InfoDepth -> DEBU 050 [core]Subchannel Connectivity change to TRANSIENT_FAILURE
2022-05-10 13:09:49.880 UTC [grpc] InfoDepth -> DEBU 051 [core]pickfirstBalancer: UpdateSubConnState: 0xc000ae9180, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing dial tcp 172.24.0.5:7050: connect: connection refused"}
2022-05-10 13:09:49.880 UTC [grpc] InfoDepth -> DEBU 052 [core]Channel Connectivity change to TRANSIENT_FAILURE
2022-05-10 13:09:50.139 UTC [grpc] InfoDepth -> DEBU 053 [core]Subchannel Connectivity change to CONNECTING
2022-05-10 13:09:50.139 UTC [grpc] InfoDepth -> DEBU 054 [core]Subchannel picks a new address "ordererCA3:9050" to connect
2022-05-10 13:09:50.139 UTC [grpc] InfoDepth -> DEBU 055 [core]pickfirstBalancer: UpdateSubConnState: 0xc000ae9f50, {CONNECTING <nil>}
2022-05-10 13:09:50.139 UTC [grpc] InfoDepth -> DEBU 056 [core]Channel Connectivity change to CONNECTING
2022-05-10 13:09:50.140 UTC [grpc] WarningDepth -> DEBU 057 [core]grpc: addrConn.createTransport failed to connect to {ordererCA3:9050 ordererCA3:9050 <nil> 0 <nil>}. Err: connection error: desc = "transport: Error while dialing dial tcp 172.24.0.7:9050: connect: connection refused". Reconnecting...
2022-05-10 13:09:50.140 UTC [grpc] InfoDepth -> DEBU 058 [core]Subchannel Connectivity change to TRANSIENT_FAILURE
2022-05-10 13:09:50.140 UTC [grpc] InfoDepth -> DEBU 059 [core]pickfirstBalancer: UpdateSubConnState: 0xc000ae9f50, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing dial tcp 172.24.0.7:9050: connect: connection refused"}
2022-05-10 13:09:50.140 UTC [grpc] InfoDepth -> DEBU 05a [core]Channel Connectivity change to TRANSIENT_FAILURE

So orderers can't connect with each other.
Do you have some advice?
Thanks

Il giorno mar 10 mag 2022 alle ore 14:36 Yacov Manevich <YACOVM@...> ha scritto:
Check the logs of the communication infrastructure, by enabling gRPC debug.

From: fabric@... <fabric@...> on behalf of famar <fabrizio.marangio@...>
Sent: Tuesday, May 10, 2022 10:37 AM
To: fabric@... <fabric@...>
Subject: [EXTERNAL] [Hyperledger Fabric] cannot elect raft leader #fabric-orderer
 
Hello everyone, i'm trying to start a network with 3 orderers running on 3 different orgs. Orderer's containers start but the leader is not elected. I have this type of messages in orderer's containers: orderer1 2022-05-10 07:33:28.112 UTC 00ba
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
 
ZjQcmQRYFpfptBannerEnd
Hello everyone, i'm trying to start a network with 3 orderers running on 3 different orgs. Orderer's containers start but the leader is not elected.
I have this type of messages in orderer's containers:

orderer1
2022-05-10 07:33:28.112 UTC 00ba INFO [orderer.consensus.etcdraft] campaign -> 1 [logterm: 1, index: 3] sent MsgPreVote request to 3 at term 1 channel=mychannel node=1
orderer2
2022-05-10 07:33:35.630 UTC 066a INFO [orderer.consensus.etcdraft] campaign -> 2 [logterm: 1, index: 3] sent MsgPreVote request to 3 at term 1 channel=mychannel node=2
orderer3
2022-05-10 07:33:38.689 UTC 012d INFO [orderer.consensus.etcdraft] campaign -> 3 [logterm: 1, index: 3] sent MsgPreVote request to 2 at term 1 channel=mychannel node=3

I attach the docker.-compose.yaml and the configtx.yaml.

Can someone help me solve this issue? 
Thanks in advance
 


Yacov
 

You can try to telnet to the host:port, either from outside or from within the container.


From: Fabrizio Marangio <fabrizio.marangio@...>
Sent: Wednesday, May 11, 2022 11:44 AM
To: Yacov Manevich <YACOVM@...>
Cc: fabric@... <fabric@...>
Subject: [EXTERNAL] Re: [Hyperledger Fabric] cannot elect raft leader #fabric-orderer
 
I understand that it's a connection problem but I can't figure out the source. It's like the ports are closed or there is an active firewall but I'm on a virtual machine and there are no such settings. Can you give me any advice
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
 
ZjQcmQRYFpfptBannerEnd
I understand that it's a connection problem but I can't figure out the source. It's like the ports are closed or there is an active firewall but I'm on a virtual machine and there are no such settings.
Can you give me any advice on how to try to figure out the origin of this connection failure?
Thanks

Il giorno mar 10 mag 2022 alle ore 16:01 Yacov Manevich <YACOVM@...> ha scritto:

It's  a connection problem... you need to solve it on your own as it's your environment.

From: Fabrizio Marangio <fabrizio.marangio@...>
Sent: Tuesday, May 10, 2022 4:16 PM
To: Yacov Manevich <YACOVM@...>
Cc: fabric@... <fabric@...>
Subject: [EXTERNAL] Re: [Hyperledger Fabric] cannot elect raft leader #fabric-orderer
 
Thank you very much. Using the grpc debug i have this log: 2022-05-10 13:09:49.879 UTC [grpc] InfoDepth -> DEBU 04b [core]Subchannel Connectivity change to CONNECTING 2022-05-10 13:09:49.879 UTC [grpc] InfoDepth -> DEBU 04c [core]Subchannel
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
 
ZjQcmQRYFpfptBannerEnd
Thank you very much.
Using the grpc debug i have this log:

2022-05-10 13:09:49.879 UTC [grpc] InfoDepth -> DEBU 04b [core]Subchannel Connectivity change to CONNECTING
2022-05-10 13:09:49.879 UTC [grpc] InfoDepth -> DEBU 04c [core]Subchannel picks a new address "ordererCA1:7050" to connect
2022-05-10 13:09:49.879 UTC [grpc] InfoDepth -> DEBU 04d [core]pickfirstBalancer: UpdateSubConnState: 0xc000ae9180, {CONNECTING <nil>}
2022-05-10 13:09:49.879 UTC [grpc] InfoDepth -> DEBU 04e [core]Channel Connectivity change to CONNECTING
2022-05-10 13:09:49.880 UTC [grpc] WarningDepth -> DEBU 04f [core]grpc: addrConn.createTransport failed to connect to {ordererCA1:7050 ordererCA1:7050 <nil> 0 <nil>}. Err: connection error: desc = "transport: Error while dialing dial tcp 172.24.0.5:7050: connect: connection refused". Reconnecting...
2022-05-10 13:09:49.880 UTC [grpc] InfoDepth -> DEBU 050 [core]Subchannel Connectivity change to TRANSIENT_FAILURE
2022-05-10 13:09:49.880 UTC [grpc] InfoDepth -> DEBU 051 [core]pickfirstBalancer: UpdateSubConnState: 0xc000ae9180, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing dial tcp 172.24.0.5:7050: connect: connection refused"}
2022-05-10 13:09:49.880 UTC [grpc] InfoDepth -> DEBU 052 [core]Channel Connectivity change to TRANSIENT_FAILURE
2022-05-10 13:09:50.139 UTC [grpc] InfoDepth -> DEBU 053 [core]Subchannel Connectivity change to CONNECTING
2022-05-10 13:09:50.139 UTC [grpc] InfoDepth -> DEBU 054 [core]Subchannel picks a new address "ordererCA3:9050" to connect
2022-05-10 13:09:50.139 UTC [grpc] InfoDepth -> DEBU 055 [core]pickfirstBalancer: UpdateSubConnState: 0xc000ae9f50, {CONNECTING <nil>}
2022-05-10 13:09:50.139 UTC [grpc] InfoDepth -> DEBU 056 [core]Channel Connectivity change to CONNECTING
2022-05-10 13:09:50.140 UTC [grpc] WarningDepth -> DEBU 057 [core]grpc: addrConn.createTransport failed to connect to {ordererCA3:9050 ordererCA3:9050 <nil> 0 <nil>}. Err: connection error: desc = "transport: Error while dialing dial tcp 172.24.0.7:9050: connect: connection refused". Reconnecting...
2022-05-10 13:09:50.140 UTC [grpc] InfoDepth -> DEBU 058 [core]Subchannel Connectivity change to TRANSIENT_FAILURE
2022-05-10 13:09:50.140 UTC [grpc] InfoDepth -> DEBU 059 [core]pickfirstBalancer: UpdateSubConnState: 0xc000ae9f50, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing dial tcp 172.24.0.7:9050: connect: connection refused"}
2022-05-10 13:09:50.140 UTC [grpc] InfoDepth -> DEBU 05a [core]Channel Connectivity change to TRANSIENT_FAILURE

So orderers can't connect with each other.
Do you have some advice?
Thanks

Il giorno mar 10 mag 2022 alle ore 14:36 Yacov Manevich <YACOVM@...> ha scritto:
Check the logs of the communication infrastructure, by enabling gRPC debug.

From: fabric@... <fabric@...> on behalf of famar <fabrizio.marangio@...>
Sent: Tuesday, May 10, 2022 10:37 AM
To: fabric@... <fabric@...>
Subject: [EXTERNAL] [Hyperledger Fabric] cannot elect raft leader #fabric-orderer
 
Hello everyone, i'm trying to start a network with 3 orderers running on 3 different orgs. Orderer's containers start but the leader is not elected. I have this type of messages in orderer's containers: orderer1 2022-05-10 07:33:28.112 UTC 00ba
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
 
ZjQcmQRYFpfptBannerEnd
Hello everyone, i'm trying to start a network with 3 orderers running on 3 different orgs. Orderer's containers start but the leader is not elected.
I have this type of messages in orderer's containers:

orderer1
2022-05-10 07:33:28.112 UTC 00ba INFO [orderer.consensus.etcdraft] campaign -> 1 [logterm: 1, index: 3] sent MsgPreVote request to 3 at term 1 channel=mychannel node=1
orderer2
2022-05-10 07:33:35.630 UTC 066a INFO [orderer.consensus.etcdraft] campaign -> 2 [logterm: 1, index: 3] sent MsgPreVote request to 3 at term 1 channel=mychannel node=2
orderer3
2022-05-10 07:33:38.689 UTC 012d INFO [orderer.consensus.etcdraft] campaign -> 3 [logterm: 1, index: 3] sent MsgPreVote request to 2 at term 1 channel=mychannel node=3

I attach the docker.-compose.yaml and the configtx.yaml.

Can someone help me solve this issue? 
Thanks in advance