Problems communicating with Zeebe and initialization

I booted my camunda with the following chart helm. `

global:
  ingress:
    enabled: true
    className: nginx
    host: "bpms.mizu.com.br"
    tls:
      enabled: true
      secretName: "tls-secret"
  identity:
    auth:
      publicIssuerUrl: "https://bpms.mizu.com.br/auth/realms/camunda-platform"
      operate:
        redirectUrl: "https://bpms.mizu.com.br/operate"
      tasklist:
        redirectUrl: "https://bpms.mizu.com.br/tasklist"
      optimize:
        redirectUrl: "https://bpms.mizu.com.br/optimize"
      webModeler:
        redirectUrl: "https://bpms.mizu.com.br/modeler"
      console:
        redirectUrl: "https://bpms.mizu.com.br/console"
      identity:
        redirectUrl: "https://bpms.mizu.com.br/identity"

identity:
  contextPath: "/identity"
  fullURL: "https://bpms.mizu.com.br/identity"


keycloak:
  logging:
    level: "TRACE"

operate:
  contextPath: "/operate"

optimize:
  contextPath: "/optimize"

tasklist:
  contextPath: "/tasklist"

webModeler:
  contextPath: "/modeler"

console:
  contextPath: "/console"

zeebeGateway:
  contextPath: "/zeebe"
  ingress:
    grpc:
      enabled: true
      className: nginx
      host: "zeebe.mizu.com.br"

# Reduce resource usage for Zeebe and Zeebe-Gateway
zeebe:
  clusterSize: 1
  partitionCount: 1
  replicationFactor: 1
  pvcSize: 10Gi
  resources: {}
  initResources: {}

zeebe-gateway:
  replicas: 1
  ingress:
    enabled: true
    className: nginx
    host: "zeebe.mizu.com.br"
    tls:
      enabled: true
      secretName: "tls-secret-zeebe"


# Enable Outbound Connectors only
connectors:
  enabled: true
  inbound:
    mode: "disabled"

# Configure Elasticsearch to make it running for local development
elasticsearch:
  resources: {}
  initResources: {}
  replicas: 1
  minimumMasterNodes: 1
  # Allow no backup for single node setups
  clusterHealthCheckParams: "wait_for_status=yellow&timeout=1s"

  # Request smaller persistent volumes.
  volumeClaimTemplate:
    accessModes: [ "ReadWriteOnce" ]
    storageClassName: "standard"
    resources:
      requests:
        storage: 15Gi

all items work, but zeebe I’m having some problems when using the modeler and there’s an error in the gateway and in zeebe.

erro 1 gateway

2024-06-04 20:59:38.132 [] [netty-messaging-event-epoll-client-1] [] WARN 
      io.atomix.cluster.messaging.impl.NettyMessagingService - Unexpected error while handling message stream-recreate from camunda-platform-zeebe-0.camunda-platform-zeebe.default.svc:26502
io.atomix.cluster.messaging.MessagingException$NoSuchMemberException: Failed to handle message, host camunda-platform-zeebe-0.camunda-platform-zeebe.default.svc:26502 is not a known cluster member
        at io.atomix.cluster.messaging.impl.DefaultClusterCommunicationService$InternalMessageBiResponder.handleRequest(DefaultClusterCommunicationService.java:371) ~[zeebe-atomix-cluster-8.5.1.jar:8.5.1]
        at io.atomix.cluster.messaging.impl.DefaultClusterCommunicationService$InternalMessageBiResponder.lambda$apply$0(DefaultClusterCommunicationService.java:357) ~[zeebe-atomix-cluster-8.5.1.jar:8.5.1]
        at io.camunda.zeebe.scheduler.ActorJob.invoke(ActorJob.java:94) ~[zeebe-scheduler-8.5.1.jar:8.5.1]
        at io.camunda.zeebe.scheduler.ActorJob.execute(ActorJob.java:47) ~[zeebe-scheduler-8.5.1.jar:8.5.1]
        at io.camunda.zeebe.scheduler.ActorTask.execute(ActorTask.java:122) ~[zeebe-scheduler-8.5.1.jar:8.5.1]
        at io.camunda.zeebe.scheduler.ActorThread.executeCurrentTask(ActorThread.java:130) ~[zeebe-scheduler-8.5.1.jar:8.5.1]
        at io.camunda.zeebe.scheduler.ActorThread.doWork(ActorThread.java:108) ~[zeebe-scheduler-8.5.1.jar:8.5.1]
        at io.camunda.zeebe.scheduler.ActorThread.run(ActorThread.java:227) ~[zeebe-scheduler-8.5.1.jar:8.5.1]
2024-06-04 20:59:38.132 [] [netty-messaging-event-epoll-client-0] [] WARN 
      io.atomix.cluster.messaging.impl.NettyMessagingService - Unexpected error while handling message cluster-topology-sync from camunda-platform-zeebe-0.camunda-platform-zeebe.default.svc:26502
io.atomix.cluster.messaging.MessagingException$NoSuchMemberException: Failed to handle message, host camunda-platform-zeebe-0.camunda-platform-zeebe.default.svc:26502 is not a known cluster member
        at io.atomix.cluster.messaging.impl.DefaultClusterCommunicationService$InternalMessageBiResponder.handleRequest(DefaultClusterCommunicationService.java:371) ~[zeebe-atomix-cluster-8.5.1.jar:8.5.1]
        at io.atomix.cluster.messaging.impl.DefaultClusterCommunicationService$InternalMessageBiResponder.lambda$apply$0(DefaultClusterCommunicationService.java:357) ~[zeebe-atomix-cluster-8.5.1.jar:8.5.1]
        at io.camunda.zeebe.scheduler.ActorJob.invoke(ActorJob.java:94) ~[zeebe-scheduler-8.5.1.jar:8.5.1]
        at io.camunda.zeebe.scheduler.ActorJob.execute(ActorJob.java:47) ~[zeebe-scheduler-8.5.1.jar:8.5.1]
        at io.camunda.zeebe.scheduler.ActorTask.execute(ActorTask.java:122) ~[zeebe-scheduler-8.5.1.jar:8.5.1]
        at io.camunda.zeebe.scheduler.ActorThread.executeCurrentTask(ActorThread.java:130) ~[zeebe-scheduler-8.5.1.jar:8.5.1]
        at io.camunda.zeebe.scheduler.ActorThread.doWork(ActorThread.java:108) ~[zeebe-scheduler-8.5.1.jar:8.5.1]
        at io.camunda.zeebe.scheduler.ActorThread.run(ActorThread.java:227) ~[zeebe-scheduler-8.5.1.jar:8.5.1]
2024-06-04 20:59:38.822 [] [atomix-cluster-heartbeat-sender] [] INFO

erro 2 camunda-platform-zeebe-0 I’m not sure if it’s relevant.

     io.camunda.zeebe.topology.gossip.ClusterTopologyGossiper - Failed to sync with camunda-platform-zeebe-gateway-66474f9847-s2bvh
java.util.concurrent.CompletionException: io.atomix.cluster.messaging.MessagingException$RemoteHandlerFailure: Remote handler failed to handle message, cause: Failed to handle message, host camunda-platform-zeebe-0.camunda-platform-zeebe.default.svc:26502 is not a known cluster member
       at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(Unknown Source) ~[?:?]
       at java.base/java.util.concurrent.CompletableFuture.completeThrowable(Unknown Source) ~[?:?]
       at java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(Unknown Source) ~[?:?]
       at java.base/java.util.concurrent.CompletableFuture.postComplete(Unknown Source) ~[?:?]
       at java.base/java.util.concurrent.CompletableFuture.completeExceptionally(Unknown Source) ~[?:?]
       at io.atomix.cluster.messaging.impl.NettyMessagingService.lambda$executeOnPooledConnection$25(NettyMessagingService.java:626) ~[zeebe-atomix-cluster-8.5.1.jar:8.5.1]
       at com.google.common.util.concurrent.DirectExecutor.execute(DirectExecutor.java:31) ~[guava-33.1.0-jre.jar:?]
       at io.atomix.cluster.messaging.impl.NettyMessagingService.lambda$executeOnPooledConnection$26(NettyMessagingService.java:624) ~[zeebe-atomix-cluster-8.5.1.jar:8.5.1]
       at java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(Unknown Source) ~[?:?]
       at java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(Unknown Source) ~[?:?]
       at java.base/java.util.concurrent.CompletableFuture.postComplete(Unknown Source) ~[?:?]
       at java.base/java.util.concurrent.CompletableFuture.completeExceptionally(Unknown Source) ~[?:?]
       at io.atomix.cluster.messaging.impl.AbstractClientConnection.dispatch(AbstractClientConnection.java:48) ~[zeebe-atomix-cluster-8.5.1.jar:8.5.1]
       at io.atomix.cluster.messaging.impl.AbstractClientConnection.dispatch(AbstractClientConnection.java:29) ~[zeebe-atomix-cluster-8.5.1.jar:8.5.1]
       at io.atomix.cluster.messaging.impl.NettyMessagingService$MessageDispatcher.channelRead0(NettyMessagingService.java:1109) ~[zeebe-atomix-cluster-8.5.1.jar:8.5.1]
       at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:99) ~[netty-transport-4.1.109.Final.jar:4.1.109.Final]
       at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444) ~[netty-transport-4.1.109.Final.jar:4.1.109.Final]
       at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420) ~[netty-transport-4.1.109.Final.jar:4.1.109.Final]
       at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412) ~[netty-transport-4.1.109.Final.jar:4.1.109.Final]
       at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:346) ~[netty-codec-4.1.109.Final.jar:4.1.109.Final]
       at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:318) ~[netty-codec-4.1.109.Final.jar:4.1.109.Final]
       at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444) ~[netty-transport-4.1.109.Final.jar:4.1.109.Final]
       at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420) ~[netty-transport-4.1.109.Final.jar:4.1.109.Final]
       at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412) ~[netty-transport-4.1.109.Final.jar:4.1.109.Final]
       at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410) ~[netty-transport-4.1.109.Final.jar:4.1.109.Final]
       at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:440) ~[netty-transport-4.1.109.Final.jar:4.1.109.Final]
       at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420) ~[netty-transport-4.1.109.Final.jar:4.1.109.Final]
       at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919) ~[netty-transport-4.1.109.Final.jar:4.1.109.Final]
       at io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:801) ~[netty-transport-classes-epoll-4.1.109.Final.jar:4.1.109.Final]
       at io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:501) ~[netty-transport-classes-epoll-4.1.109.Final.jar:4.1.109.Final]
       at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:399) ~[netty-transport-classes-epoll-4.1.109.Final.jar:4.1.109.Final]
       at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) ~[netty-common-4.1.109.Final.jar:4.1.109.Final]
       at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[netty-common-4.1.109.Final.jar:4.1.109.Final]
       at java.base/java.lang.Thread.run(Unknown Source) ~[?:?]
Caused by: io.atomix.cluster.messaging.MessagingException$RemoteHandlerFailure: Remote handler failed to handle message, cause: Failed to handle message, host camunda-platform-zeebe-0.camunda-platform-zeebe.default.svc:26502 is not a known cluster member
       ... 22 more

finally my problem with the modeler

Hi @Axcel_Kuhn, welcome to the forums! Your Helm chart has zeebe-gateway as one of the items, but it should be zeebeGateway, which you also have. I would first combine those sections and make sure it is configured how you want, then redeploy. If your cluster doesn’t have any data I would recommend fully deleting it, including the PVCs, before deploying. I admit, I don’t know if this will resolve the issue, but having a clean values.yaml file is a good first step.