Camunda 8 | Partition-1 failed, marking it as unhealthy - message=Services not installed

Camunda 8 Topics Discussion & Questions
1

Hi everyone,
Camunda 8
I’m encountering an issue with my Zeebe setup where Partition 1 is consistently marked as unhealthy with the error message “Services not installed.” I’ve tried several troubleshooting steps, but the problem persists.

Here’s my Docker Compose configuration:

version: '3.8'

services:
  zeebe:
    image: camunda/zeebe:8.6.5
    container_name: zeebe
    profiles: ["", "opensearch"]
    ports:
      - "26500:26500"
      - "9600:9600"
      - "8088:8080"
    environment:
      - ZEEBE_BROKER_NETWORK_HOST=0.0.0.0
      - ZEEBE_BROKER_GATEWAY_SECURITY_ENABLED=true
      - ZEEBE_BROKER_GATEWAY_SECURITY_CERTIFICATECHAINPATH=/usr/local/zeebe/cert.pem
      - ZEEBE_BROKER_GATEWAY_SECURITY_PRIVATEKEYPATH=/usr/local/zeebe/key.pem
      - ZEEBE_BROKER_CLUSTER_PARTITIONSCOUNT=1
      - ZEEBE_BROKER_CLUSTER_REPLICATIONFACTOR=1
      - ZEEBE_BROKER_CLUSTER_CLUSTERSIZE=1
    restart: always
    healthcheck:
      test: [ "CMD-SHELL", "timeout 10s bash -c ':> /dev/tcp/127.0.0.1/9600' || exit 1" ]
      interval: 30s
      timeout: 5s
      retries: 5
      start_period: 30s
    volumes:
      - zeebe:/usr/local/zeebe/data
      - ./cert.pem:/usr/local/zeebe/cert.pem
      - ./key.pem:/usr/local/zeebe/key.pem
    networks:
      - camunda-platform

volumes:
  zeebe:

networks:
  camunda-platform:
  identity-network:

And here’s a relevant excerpt from my Zeebe logs:

zeebe  | 2024-11-23 13:18:11.768 [Broker-0] [zb-actors-0] [ZeebePartition-1] INFO 
zeebe  |       io.camunda.zeebe.broker.system - Transition to LEADER on term 1 requested.
zeebe  | 2024-11-23 13:18:11.769 [Broker-0] [zb-actors-0] [ZeebePartition-1] DEBUG
zeebe  |       io.camunda.zeebe.broker.system - Partition role transitioning from null to LEADER in term 1
zeebe  | 2024-11-23 13:18:11.771 [Broker-0] [zb-actors-0] [ZeebePartition-1] INFO 
zeebe  |       io.camunda.zeebe.broker.system - Transition to LEADER on term 1 starting
zeebe  | 2024-11-23 13:18:11.771 [Broker-0] [zb-actors-0] [ZeebePartition-1] INFO 
zeebe  |       io.camunda.zeebe.broker.system - Transition to LEADER on term 1 - transitioning LogStorage
zeebe  | 2024-11-23 13:18:11.772 [Broker-0] [zb-actors-0] [ZeebePartition-1] INFO 
zeebe  |       io.camunda.zeebe.broker.system - Transition to LEADER on term 1 - transitioning LogStream
zeebe  | 2024-11-23 13:18:11.774 [Broker-0] [zb-actors-0] [HealthCheckService] DEBUG
zeebe  |       io.camunda.zeebe.broker.system - Detected 'UNHEALTHY' components. The current health status of components: [Partition-1{status=UNHEALTHY, issue=HealthIssue[message=null, throwable=null, cause=ZeebePartition-1{status=UNHEALTHY, issue=HealthIssue[message=Services not installed, throwable=null, cause=null]}]}]
zeebe  | 2024-11-23 13:18:11.775 [Broker-0] [zb-actors-0] [HealthCheckService] INFO 
zeebe  |       io.camunda.zeebe.broker.system - All partitions are installed. Broker is ready!
zeebe  | 2024-11-23 13:18:11.775 [Broker-0] [zb-actors-0] [ZeebePartition-1] INFO 
zeebe  |       io.camunda.zeebe.broker.system - Transition to LEADER on term 1 - transitioning ZeebeDb
zeebe  | 2024-11-23 13:18:11.776 [Broker-0] [zb-actors-0] [HealthCheckService] WARN 
zeebe  |       io.camunda.zeebe.broker.system - Partition-1 failed, marking it as unhealthy: Partition-1{status=UNHEALTHY, issue=HealthIssue[message=null, throwable=null, cause=ZeebePartition-1{status=UNHEALTHY, issue=HealthIssue[message=Services not installed, throwable=null, cause=null]}]}
zeebe  | 2024-11-23 13:18:11.818 [Broker-0] [zb-fs-workers-1] [SnapshotStore-1] DEBUG
zeebe  |       io.camunda.zeebe.logstreams.snapshot - Opened database from '/usr/local/zeebe/data/raft-partition/partitions/1/runtime'.
zeebe  | 2024-11-23 13:18:11.818 [Broker-0] [zb-actors-0] [ZeebePartition-1] INFO 
zeebe  |       io.camunda.zeebe.broker.system - Transition to LEADER on term 1 - transitioning Migration
zeebe  | 2024-11-23 13:18:11.905 [Broker-0] [zb-actors-0] [ZeebePartition-1] INFO 
zeebe  |       org.camunda.feel.FeelEngine - Engine created. [value-mapper: CompositeValueMapper(List(io.camunda.zeebe.feel.impl.MessagePackValueMapper@19e7e44a)), function-provider: io.camunda.zeebe.feel.impl.FeelFunctionProvider@3c049df7, clock: io.camunda.zeebe.engine.processing.bpmn.clock.ZeebeFeelEngineClock@230b89da, configuration: {externalFunctionsEnabled: false}]
zeebe  | 2024-11-23 13:18:11.913 [] [atomix-cluster-events] [] DEBUG
zeebe  |       io.camunda.zeebe.gateway - Received metadata change from Broker 0, partitions {}, terms {} and health {1=UNHEALTHY}.
zeebe  | 2024-11-23 13:18:11.947 [Broker-0] [zb-actors-0] [ZeebePartition-1] INFO 
zeebe  |       org.camunda.dmn.DmnEngine - DMN-Engine created. [value-mapper: CompositeValueMapper(List(io.camunda.zeebe.feel.impl.MessagePackValueMapper@1da79ac0)), function-provider: org.camunda.feel.context.FunctionProvider$EmptyFunctionProvider$@18332011, audit-loggers: List(), configuration: Configuration(false,false,false)]
zeebe  | 2024-11-23 13:18:11.948 [Broker-0] [zb-actors-0] [ZeebePartition-1] INFO

Can you please help me?

2

You are not installing dependent services for Zeebe Engine. I would suggest try to use the full template docker compose file first, then play around removing one component at a time in the beginning.

If you read the docker-compose.yaml for zeebe it states “depends on” after networks, which you missed out.

3

I see it depends on elasticsearch.
I added that too.
The error still exists.

In Docker

 io.camunda.zeebe.broker.system - Partition-1 failed, marking it as unhealthy: Partition-1{status=UNHEALTHY, issue=HealthIssue[message=null, throwable=null, cause=ZeebePartition-1{status=UNHEALTHY, issue=HealthIssue[message=Services not installed, throwable=null, cause=null]}]}

In Client

Expected to execute command on partition 0, but either it does not exist, or the gateway is not yet aware of it

Is there a docker compose example that only starts Zeebe?

4

As I mentioned we cannot launch Zeebe alone, please read the documents before you get started.

If you would like to try out, download C8Run which will help you to onboard quickly.

5

I did.
Document:

Components
Zeebe Broker and Gateway
Operate
Tasklist
Connectors
Optimize
Identity
Web Modeler
Console
All components except Web Modeler and Console are single Java applications. Depending on your needs, you might not need all of the above components to successfully use Camunda 8.

I need to prepare zeebe along with non-commercial tools.
Not Zeebe alone.
So I don’t find dependencies and requirements clearly in the documentation.