You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering whether it'd be possible to update this demo, since it looks quite simple and illustrative.
I am getting this:
~/code/zeebe-demo$ docker-compose exec gateway zbctl status
WARNING: Some services (gateway, grafana, prometheus, starter, worker, zeebe-0, zeebe-1, zeebe-2) use the 'deploy' key, which will be ignored. Compose does not support 'deploy' configuration - use `docker stack deploy` to deploy to a swarm.
Error: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 127.0.0.1:26500: connect: connection refused"
The starter also seems to constantly error in a loop:
11:51:43.519 [main] WARN io.zeebe.Starter - Failed to deploy workflow, retrying
io.zeebe.client.api.command.ClientStatusException: Method not found: gateway_protocol.Gateway/DeployWorkflow
at io.zeebe.client.impl.ZeebeClientFutureImpl.transformExecutionException(ZeebeClientFutureImpl.java:93) ~[starter.jar:?]
at io.zeebe.client.impl.ZeebeClientFutureImpl.join(ZeebeClientFutureImpl.java:50) ~[starter.jar:?]
at io.zeebe.Starter.deployWorkflow(Starter.java:88) [starter.jar:?]
at io.zeebe.Starter.run(Starter.java:46) [starter.jar:?]
at io.zeebe.App.createApp(App.java:36) [starter.jar:?]
at io.zeebe.Starter.main(Starter.java:102) [starter.jar:?]
Caused by: java.util.concurrent.ExecutionException: io.grpc.StatusRuntimeException: UNIMPLEMENTED: Method not found: gateway_protocol.Gateway/DeployWorkflow
at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357) ~[?:1.8.0_212]
at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895) ~[?:1.8.0_212]
at io.zeebe.client.impl.ZeebeClientFutureImpl.join(ZeebeClientFutureImpl.java:48) ~[starter.jar:?]
... 4 more
Caused by: io.grpc.StatusRuntimeException: UNIMPLEMENTED: Method not found: gateway_protocol.Gateway/DeployWorkflow
at io.grpc.Status.asRuntimeException(Status.java:533) ~[starter.jar:?]
at io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:442) ~[starter.jar:?]
at io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39) ~[starter.jar:?]
at io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23) ~[starter.jar:?]
at io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40) ~[starter.jar:?]
at io.grpc.internal.CensusStatsModule$StatsClientInterceptor$1$1.onClose(CensusStatsModule.java:700) ~[starter.jar:?]
at io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39) ~[starter.jar:?]
at io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23) ~[starter.jar:?]
at io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40) ~[starter.jar:?]
at io.grpc.internal.CensusTracingModule$TracingClientInterceptor$1$1.onClose(CensusTracingModule.java:399) ~[starter.jar:?]
at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:507) ~[starter.jar:?]
at io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:66) ~[starter.jar:?]
at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.close(ClientCallImpl.java:627) ~[starter.jar:?]
at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.access$700(ClientCallImpl.java:515) ~[starter.jar:?]
at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInternal(ClientCallImpl.java:686) ~[starter.jar:?]
at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:675) ~[starter.jar:?]
at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37) ~[starter.jar:?]
at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123) ~[starter.jar:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_212]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_212]
at java.lang.Thread.run(Thread.java:748) ~[?:1.8.0_212]
I've compiled with java 11 on linux. I am assuming the zeebe version used is simply too new? What would the last supported version actually be though?
Grafana also shows this, but I guess it is irrelevant:
~/code/zeebe-demo$ docker logs zeebe-demo_grafana_1 | rg lvl=er
logger=provisioning.plugins t=2022-04-12T11:30:20.93+0000 lvl=eror msg="Failed to read plugin provisioning files from directory" path=/etc/grafana/provisioning/plugins error="open /etc/grafana/provisioning/plugins: no such file or directory"
logger=provisioning.notifiers t=2022-04-12T11:30:20.93+0000 lvl=eror msg="Can't read alert notification provisioning files from directory" path=/etc/grafana/provisioning/notifiers error="open /etc/grafana/provisioning/notifiers: no such file or directory"
logger=context t=2022-04-12T11:30:21.47+0000 lvl=eror msg="Failed to look up user based on cookie" error="user token not found"
logger=context t=2022-04-12T11:30:21.48+0000 lvl=eror msg="Failed to look up user based on cookie" error="user token not found"
logger=context t=2022-04-12T11:30:22.48+0000 lvl=eror msg="Failed to look up user based on cookie" error="user token not found"
logger=context t=2022-04-12T11:30:26.95+0000 lvl=eror msg="Failed to look up user based on cookie" error="user token not found"
The text was updated successfully, but these errors were encountered:
Bios-Marcel
changed the title
Steps aren't working with zeeebe 1.3+
Steps aren't working with zeebe 1.3+
Apr 12, 2022
Hey,
I was wondering whether it'd be possible to update this demo, since it looks quite simple and illustrative.
I am getting this:
The starter also seems to constantly error in a loop:
I've compiled with java 11 on linux. I am assuming the zeebe version used is simply too new? What would the last supported version actually be though?
Grafana also shows this, but I guess it is irrelevant:
The text was updated successfully, but these errors were encountered: