Creating domain with cli is giving error

Community Support
,
1

Hi team, Is something changed regarding domain registration from cli? I am getting error using this command:

docker run --net host --rm ubercadence/cli:master --domain test-domain-2 domain register --global_domain false

Cadence frontend service error logs:

{"level":"error","ts":"2020-07-13T17:30:46.234Z","msg":"Uncategorized error","service":"cadence-frontend","error":"BadRequest: Bad Request\n\tstatus code: 400, request id: CFF14888DC5901E5, host id: QELJXOA7o9VXsFCcf2W0L7W/Jv8JuDrBhWIfAQYcBVgRgMnDGE2JyC5iA443cjwauxZgKmj/yBQ=","logging-call-at":"workflowHandler.go:3497","stacktrace":"github.com/uber/cadence/common/log/loggerimpl.(*loggerImpl).Error\n\t/cadence/common/log/loggerimpl/logger.go:134\ngithub.com/uber/cadence/service/frontend.(*WorkflowHandler).error\n\t/cadence/service/frontend/workflowHandler.go:3497\ngithub.com/uber/cadence/service/frontend.(*WorkflowHandler).RegisterDomain\n\t/cadence/service/frontend/workflowHandler.go:279\ngithub.com/uber/cadence/service/frontend.(*DCRedirectionHandlerImpl).RegisterDomain\n\t/cadence/service/frontend/dcRedirectionHandler.go:177\ngithub.com/uber/cadence/service/frontend.(*AccessControlledWorkflowHandler).RegisterDomain\n\t/cadence/service/frontend/accessControlledHandler.go:467\ngithub.com/uber/cadence/.gen/go/cadence/workflowserviceserver.handler.RegisterDomain\n\t/cadence/.gen/go/cadence/workflowserviceserver/server.go:1033\ngo.uber.org/yarpc/encoding/thrift.thriftUnaryHandler.Handle\n\t/go/pkg/mod/go.uber.org/yarpc@v1.42.0/encoding/thrift/inbound.go:61\ngo.uber.org/yarpc/internal/observability.(*Middleware).Handle\n\t/go/pkg/mod/go.uber.org/yarpc@v1.42.0/internal/observability/middleware.go:141\ngo.uber.org/yarpc/api/middleware.unaryHandlerWithMiddleware.Handle\n\t/go/pkg/mod/go.uber.org/yarpc@v1.42.0/api/middleware/inbound.go:71\ngo.uber.org/yarpc/api/transport.InvokeUnaryHandler\n\t/go/pkg/mod/go.uber.org/yarpc@v1.42.0/api/transport/handler_invoker.go:70\ngo.uber.org/yarpc/transport/tchannel.handler.callHandler\n\t/go/pkg/mod/go.uber.org/yarpc@v1.42.0/transport/tchannel/handler.go:215\ngo.uber.org/yarpc/transport/tchannel.handler.handle\n\t/go/pkg/mod/go.uber.org/yarpc@v1.42.0/transport/tchannel/handler.go:118\ngo.uber.org/yarpc/transport/tchannel.handler.Handle\n\t/go/pkg/mod/go.uber.org/yarpc@v1.42.0/transport/tchannel/handler.go:107\ngithub.com/uber/tchannel-go.channelHandler.Handle\n\t/go/pkg/mod/github.com/uber/tchannel-go@v1.16.0/handlers.go:126\ngithub.com/uber/tchannel-go.(*Connection).dispatchInbound\n\t/go/pkg/mod/github.com/uber/tchannel-go@v1.16.0/inbound.go:203"}

1 Like
3

Please don’t use master as we are constantly doing backwards incompatible changes.

Make sure to use v0.26.0 (or whatever the latest release at the time you read this) of both service docker and the tctl docker.

4

Hi Maxim, I am using ubercadence in that only master is available. So there might be some bug in the master version?

5

Are you running the master version of the service as well using docker-compose?

6

No, I m using latest release 0.13.0 for server and running using kubernetes

7

Then I would recommend using the same version of the CLI docker instead of the master one.

8

Hi Maxim, figure the issue. My config archival settings are not correct due to this it’s failing. I verified this by removing archival settings and it worked and also after I corrected archival settings it worked again. The strange thing is logs are not very helpful to tell me that the archival section is creating a problem.