Forger do not forge correctly

Hi guys,

I set up a node forge for the @BCdiploma delegate last night. 1 block was forged and then the status of the node was paused in the explorer.


Last night it started again and 14 more blocks were forged, then paused again, one block has been forged since, and now the status is “not forging”.

I tried to docker-compose down/pull/up, it doesn’t seem to improve the situation. Any ideas? Where can I find the logs?

Context: the machine was used for the sandbox before, without any noticeable problem.

Config file :

version: "2"
services:
  postgres:
    image: "postgres:11-alpine"
    container_name: postgres-livenet
    restart: always
    #ports:
      #- "127.0.0.1:5432:5432" # uncomment this if you want to connect locally on DB
    volumes:
      - "postgres:/var/lib/postgresql/data"
    networks:
      - core
    environment:
      POSTGRES_DB: uns_livenet # Must match with CORE_DB_DATABASE below
      POSTGRES_USER: uns # Must match with CORE_DB_USERNAME below
      POSTGRES_PASSWORD: ******** # Must match with CORE_DB_DATABASE below
    logging:
        driver: "json-file"
        options:
            max-file: "5"
            max-size: "10m"
  uns:
    image: universalnamesystem/core:livenet
    container_name: uns-livenet # Can be anything
    restart: always
    environment:
      UNS_NET: livenet
      FORGER_SECRET: "****************************************************"
      CORE_DB_HOST: postgres
      CORE_DB_PORT: 5432
      CORE_DB_DATABASE: uns_livenet
      CORE_DB_USERNAME: uns
      CORE_DB_PASSWORD: ********
    ports:
      - "4001:4001"
      #- "4003:4003"
    cap_add:
      - SYS_NICE
      - SYS_RESOURCE
      - SYS_TIME
    networks:
      - core
    tty: true
    links:
      - postgres
    depends_on:
      - postgres
    logging:
        driver: "json-file"
        options:
            max-file: "5"
            max-size: "10m"      
volumes:
  postgres:
networks:
  core:

Hi!

The port to open is different between the sandbox version (4002) and the livenet version (4001), so maybe that’s where your problem is coming from.

I use docker-compose logs to see the logs of my node.

Hope that informations will help you.

1 Like

Sounds good after opening the right port :ok_hand:

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.