cannot obtain database lock, database may be in use by another process

[Duanraudon]

💎 Issue

Background

centos7

prysmaticlabs/prysm-beacon-chain v5.0.3

Description

version: "3.9"
services:
prysm:
image: prysmaticlabs/prysm-beacon-chain@v5.0.3
container_name: consensus1.eth-holesky-1114.xudong1111.bsnbase.com
network_mode: bridge
restart: always
command: --datadir=/prysm-data --holesky --rpc-host=0.0.0.0 --monitoring-host=0.0.0.0 --rpc-port=4000 --execution-endpoint=http://192.168.1.175:8551 --accept-terms-of-use --enable-experimental-state --jwt-secret=/cert/jwtsecretexecution513007492389666817 --suggested-fee-recipient=0x8cc65660b73B595A9979438bB1A6D844E1846305 --genesis-beacon-api-url=https://holesky.beaconstate.info --checkpoint-sync-url=https://holesky.beaconstate.info
ports:
- "4000:4000"
- "13000:13000"
- "12000:12000/udp"
volumes:
- ./cert:/cert
- ./prysm-data:/prysm-data

time="2024-05-10 03:24:08" level=info msg="Default fee recipient is set to 0x8cc65660b73B595A9979438bB1A6D844E1846305, recipient may be overwritten from validator client and persist in db. Default fee recipient will be used as a fall back" prefix=node
time="2024-05-10 03:24:08" level=info msg="Checking DB" database-path="/prysm-data/beaconchaindata" prefix=node
time="2024-05-10 03:24:08" level=info msg="Opening Bolt DB at /prysm-data/beaconchaindata/beaconchain.db" prefix=db
unable to start beacon node: cannot obtain database lock, database may be in use by another process

cannot obtain database lock, database may be in use by another process

After a period of time after the container was started, the Docker Compose Down command was manually executed, and then the Docker Compose Up - d command was run to start. However, this error was reported shortly after. What is the reason for this?

[prestonvanloon]

Is there another process running? Try rebooting your computer