oasisprotocol / oasisprotocol/oasis-core

Error report after service restart

Open
#3,924 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
369
Forks
151
Avg merge
1d 3h
Merged PRs (30d)
6

Description

SUMMARY

Error report after service restart

ISSUE TYPE
  • Bug Report
COMPONENT NAME

oasis rosetta-gateway

OASIS NODE VERSION

20.12.2

OS / ENVIRONMENT
version: '2'
services:
  oasis: 
    image: oasis:20.12.2
    container_name: oasis
    volumes:
      #- /bsn/oasis/node:/node
      - /bsn/oasis/node/data/:/data
      - /bsn/oasis/node/etc:/node/etc
    environment:
      - OASIS_ROSETTA_GATEWAY_PORT=8080
    ports:
      - 8080:8080
      - 26656:26656
    restart: always
STEPS TO REPRODUCE
ACTUAL RESULTS
{"Version":"20.12.2","caller":"node.go:560","level":"info","module":"oasis-node","msg":"Starting oasis-node","ts":"2021-05-10T03:21:43.547380526Z"}
{"caller":"node.go:576","err":"failed to open persistence database: Cannot acquire directory lock on \"/data/persistent-store.badger.db\".  Another process is using this Badger database.: resource temporarily unavailable","level":"error","module":"oasis-node","msg":"failed to open common node store","ts":"2021-05-10T03:21:43.55416213Z"}

EXPECTED RESULTS

Normal data synchronization

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the restart using the provided oasis:20.12.2 container configuration and inspect the persistence-store.badger.db lock error. No source file or test is named; the issue is complete when the service restarts without the lock failure and resumes normal data synchronization.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, go
Domain
backend, databases, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.