Running a Timekeeper

Support
1

Issue Report

Environment

  • Operating System: Ubuntu
  • Pulsar/Advanced CLI/Docker: Docker

Problem

I am unsure if I am running my time keeper correctly as my CPU usage is almost 0%. My node is fully synced. Below is the command I used.

version: "3.7"
services:
  node:
    container_name: subspace_node
    image: ghcr.io/subspace/node:gemini-3h-2024-feb-05
    volumes:
      - node-data:/var/subspace:rw
    ports:
      - "0.0.0.0:30333:30333/udp"
      - "0.0.0.0:30333:30333/tcp"
      - "0.0.0.0:30433:30433/udp"
      - "0.0.0.0:30433:30433/tcp"
    restart: unless-stopped
    command:
      [
        "run",
        "--chain", "gemini-3h",
        "--base-path", "/var/subspace",
        "--blocks-pruning", "256",
        "--state-pruning", "archive-canonical",
        "--listen-on", "/ip4/0.0.0.0/tcp/30333",
        "--dsn-listen-on", "/ip4/0.0.0.0/udp/30433/quic-v1",
        "--dsn-listen-on", "/ip4/0.0.0.0/tcp/30433",
        "--timekeeper-cpu-cores", "0,1",
        "--name", "hhw-zulu-timekeeper"
      ]
    healthcheck:
      timeout: 5s
      interval: 30s
      retries: 60
    networks:
      spacenet:
        ipv4_address: 172.18.0.201

volumes:
  node-data:   

networks:
  spacenet:
    external: true
    name: base-stack_spacenet
2

Almost, you need to use --timekeeper or else timekeeper is not actually running, this is documented in Timekeeping | Farm from Anywhere

3

Ah okay - I read that link but I had assumed running --timekeeper-cpu-cores was just a more specific version of --timekeeper. Thanks!

4

Is there anything that would indicate the timekeeper is working as expected? I have added the new flag in docker, the node is fully synced, but I’m not sure if it is working.

Okay it appears to be working just going off the CPU usage which is at exactly 100% (so 1 core)