dozer icon indicating copy to clipboard operation
dozer copied to clipboard

When gRPC (50051) port is taken, Dozer boots up silently without reporting any error but Live won't work

Open snork-alt opened this issue 1 year ago • 6 comments

In cases when gRPC port 50051 is already taken, Dozer boots up without reporting any error even if it cannot bind to that port. As a result, many functionalities of Live are broken.

When starting locally we should always find the next available port and bind to that.

snork-alt avatar Sep 05 '23 11:09 snork-alt

Allocate random ports and pass those parts in the query string for live.

v3g42 avatar Sep 05 '23 11:09 v3g42

I don't think we should allocate random ports. It'll make live behaviour and running behaviour inconsistent.

chubei avatar Sep 05 '23 13:09 chubei

Actually you are right. Random ports won't work. But I guess we should just pick different ports for grpc and rest and not use 8080 and 50051

v3g42 avatar Sep 05 '23 13:09 v3g42

Changing default makes sense. Any suggestions?

chubei avatar Sep 05 '23 13:09 chubei

Let's start with high unreserved port. If that post is taken, we try the next one and so on until we find the first available one

snork-alt avatar Sep 06 '23 04:09 snork-alt

Let's start with high unreserved port. If that post is taken, we try the next one and so on until we find the first available one

We also do this on dozer run?

chubei avatar Sep 06 '23 04:09 chubei