connection refused by the orderer when trying to create peer channel #channel #fabric-ca #fabric-peer #fabric-orderer


famar
 

Hello everyone,
i'm having some problems starting the "peer channel create" command.
I have a network with 1 TLS-CA, 3 ROOT-CA  and 1 INTERMEDIATE-CA.
My peer is running on the intermediate CA.

When i launch this command:

peer channel create -c mychannel -f /tmp/hyperledger/org0/orderer/channel.tx -o orderer1-org0:7055 --outputBlock /tmp/hyperledger/ica1-rca-org0/peer1/assets/mychannel.block --tls --cafile /tmp/hyperledger/ica1-rca-org0/peer1/tls-msp/tlscacerts/tls-tls-ca-7051.pem

i have this error:

Error: failed to create deliver client for orderer: orderer client failed to connect to orderer1-org0:7055: failed to create new connection: connection error: desc = "transport: error while dialing: dial tcp 172.19.0.9:7055: connect: connection refused"

The orderer container is up and i can ping the address (with the specific port) of the orderer.

Can anyone tell me the cause of this error?
Let me know if you need part of the scripts to better help me.

Thanks
 


Mark Lewis
 

It certainly looks like there is some connection error from the client to 172.19.0.9:7055 but hard to know the root cause. Assuming the client really can establish a connection to that host/port, it could be an error establishing the TLS connection. I would look in the orderer container logs to confirm that it received and connection and for clues why that connection was refused.


famar
 

I think my problem is in the configtx.yaml and it depends either on a wrong orderers communication or on the incorrect insertion of the intermediate in the configuration file.
I enclose the configtx.yaml file.
Could you help me to configure it correctly?
Thanks

Il giorno mar 3 mag 2022 alle ore 11:44 Mark Lewis <Mark.S.Lewis@...> ha scritto:
It certainly looks like there is some connection error from the client to 172.19.0.9:7055 but hard to know the root cause. Assuming the client really can establish a connection to that host/port, it could be an error establishing the TLS connection. I would look in the orderer container logs to confirm that it received and connection and for clues why that connection was refused.


famar
 

I did some testing, radically simplifying the system. I tried simply having 1 TLS, 2 Orderers, and 2 Root CAs with a peer on each. If I set one orderer I have no problems but if I add another one on a different CA than the first one, I get this connection problem. If I go into the orderer log I see this string (repeated several times)

sent MsgPreVote request to 1 at term 1 channel=syschannel node=2

Unlike when I have only 1 orderer which is automatically elected as leader.

So the problem depends on the multi-orderer.
Would anyone know how to solve it? Thanks


Il giorno mer 4 mag 2022 alle ore 10:14 famar via lists.hyperledger.org <fabrizio.marangio=gmail.com@...> ha scritto:

I think my problem is in the configtx.yaml and it depends either on a wrong orderers communication or on the incorrect insertion of the intermediate in the configuration file.
I enclose the configtx.yaml file.
Could you help me to configure it correctly?
Thanks

Il giorno mar 3 mag 2022 alle ore 11:44 Mark Lewis <Mark.S.Lewis@...> ha scritto:
It certainly looks like there is some connection error from the client to 172.19.0.9:7055 but hard to know the root cause. Assuming the client really can establish a connection to that host/port, it could be an error establishing the TLS connection. I would look in the orderer container logs to confirm that it received and connection and for clues why that connection was refused.


Hi I wanted to check if java sdk is deprecated for Fabric 2.2
 



HI Everyone

I need your help with one issue. I am trying to hit my grpc server running in a docker container with a grpc client. The client is able to successfully call the server running on a VM machine 10.210.52.10 and the client is running on Localhost. Now the server is trying to call the chaincode running on the same vm 10.210.52.10 its giving me error attached

 

Regards,

       Upma 
_._,_._,_