Desc = "transport: Error while dialing dial tcp

Dear Team,

We have installed Zeebe on Azure/Linux VM. I have connect the VM though SSH.

Version: zbctl 0.17.0 (commit: 856aca0a)

When I tried:
$ ./zbctl status

I am getting below error:
Error: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = “transport: Error while dialing dial tcp 127.0.0.1:26500: connect: connection refused”

Could anyone tell me what could be the reason? Am I missing some configuration steps?

Thanks for the quick help.

Regards,
Prasad.

Hi @prasadkoribilli, it’s difficult to say if you have missed any configuration steps - you didn’t share what steps you actually took!

When you say “We have installed Zeebe on Azure/Linux VM”, I have no idea what you have done.

To identify missing steps you’d need to provide something like this:

  1. Download and unzip zeebe-distribution-0.18.0.tar.gz
  2. cd zeebe
  3. bin/broker
  4. Wait for broker to start. No errors are observed in the logs.
  5. In another terminal, run: bin/zbctl status
  6. Output: Error: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = “transport: Error while dialing dial tcp 127.0.0.1:26500: connect: connection refused”

In that case, I could make an assessment of missing steps.

So, given the example of steps above: how did you start the broker?

regards,
Josh

Hi @jwulf, Thanks for the reply.

I am now trying locally on my machine. (Windows 7)

  1. I installed zeebe-broker-0.18.0
  2. ran boker command - it ran but I can see below error in the log trace
    ERROR io.zeebe.util.actor - Actor failed in phase ‘STARTED’. Continue with next job.
  3. zbctl status gave me this:
    Cluster size: 1
    Partitions count: 1
    Replication factor: 1
    Brokers:
    Broker 0 - 0.0.0.0:26501

Could you please tell me if I need to do some changes in the configuration?
Thanks a lot for the help.

Regards,
Prasad.

Hi @prasadkoribilli, you haven’t reproduced the same error there. So what is different between what you did on your machine and what you did on the Azure VM?

Hi, I spoke with my Infra team about the issue on VM. They said the broker was not started/crashed. they are still looking into it. I will keep you posted as soon as I have some news from them.

Regards,Prasad.

Yes, the error is consistent with that.

The other thing is that it looks like you are using Zeebe 0.17 on the VM.