# Revocation DB Invalid **URL:** \ **Category:** troubleshooting\ **Tags:** docker, database\ **Created:** [July 11, 2025, 5:05pm UTC](https://forum.storj.io/t/revocation-db-invalid/30343 "2025-07-11T17:05:49Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![bradkollmyer](https://storj.bcdn.literatehosting.com/letter_avatar/bradkollmyer/32/5_5575768a8748004e209b776fc1b2916d.png) [@bradkollmyer](https://forum.storj.io/u/bradkollmyer)\ **Post date:** [July 11, 2025, 5:05pm UTC](https://forum.storj.io/t/revocation-db-invalid/30343/1 "2025-07-11T17:05:49Z")
I keep having my revocation DB become invalid. I see the following in the logs: Error: Error opening revocation database: revocation database: boltdb: invalid database [storj.io/storj/private/kvstore/boltdb.New:43](http://storj.io/storj/private/kvstore/boltdb.New:43) [storj.io/storj/private/revocation.openDBBolt:52](http://storj.io/storj/private/revocation.openDBBolt:52) [storj.io/storj/private/revocation.OpenDB:35](http://storj.io/storj/private/revocation.OpenDB:35) [storj.io/storj/private/revocation.OpenDBFromCfg:23](http://storj.io/storj/private/revocation.OpenDBFromCfg:23) main.cmdRun:76 main.newRunCmd.func1:33 [storj.io/common/process.cleanup.func1.4:402](http://storj.io/common/process.cleanup.func1.4:402) [storj.io/common/process.cleanup.func1:420](http://storj.io/common/process.cleanup.func1:420) [github.com/spf13/cobra.(\*Command).execute:985](http://github.com/spf13/cobra.(*Command).execute:985) [github.com/spf13/cobra.(\*Command).ExecuteC:1117](http://github.com/spf13/cobra.(*Command).ExecuteC:1117) [github.com/spf13/cobra.(\*Command).Execute:1041](http://github.com/spf13/cobra.(*Command).Execute:1041) [storj.io/common/process.ExecWithCustomOptions:116](http://storj.io/common/process.ExecWithCustomOptions:116) main.main:34 runtime.main:283 I’ve been running this node for a long time, but I’ve been seeing this over the last six months. The fix is to remove the revocations.db file and restart the node. Thanks Brad. ---
**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\ **Post date:** [July 12, 2025, 3:36am UTC](https://forum.storj.io/t/revocation-db-invalid/30343/2 "2025-07-12T03:36:44Z")
Hello @bradkollmyer, Welcome to the forum! > [@bradkollmyer](#): > > I’ve been running this node for a long time, but I’ve been seeing this over the last six months. Do you mean this happens all the time? If yes, then after the what event? > [@bradkollmyer](#): > > The fix is to remove the revocations.db file and restart the node. That’s right. ---
**Author:** ![bradkollmyer](https://storj.bcdn.literatehosting.com/letter_avatar/bradkollmyer/32/5_5575768a8748004e209b776fc1b2916d.png) [@bradkollmyer](https://forum.storj.io/u/bradkollmyer)\ **Post date:** [July 12, 2025, 6:56pm UTC](https://forum.storj.io/t/revocation-db-invalid/30343/3 "2025-07-12T18:56:34Z")
This happens every time the node is rebooted! It’s running under Docker. ---
**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\ **Post date:** [July 13, 2025, 2:10am UTC](https://forum.storj.io/t/revocation-db-invalid/30343/4 "2025-07-13T02:10:06Z")
Then I would suggest to check and fix a disk, where it’s located. ---
**Author:** ![bradkollmyer](https://storj.bcdn.literatehosting.com/letter_avatar/bradkollmyer/32/5_5575768a8748004e209b776fc1b2916d.png) [@bradkollmyer](https://forum.storj.io/u/bradkollmyer)\ **Post date:** [July 15, 2025, 4:20pm UTC](https://forum.storj.io/t/revocation-db-invalid/30343/5 "2025-07-15T16:20:48Z")
It’s not the disk. It’s running CephFS. It’s a cluster of 900+ TB. I use it for a variety of other tasks with no issues. Something changed a few months back. The node had been reliable for many years with this configuration. It never went down before. I checked my old emails and it seemed to start 02/2025. ---
**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\ **Post date:** [July 16, 2025, 5:05am UTC](https://forum.storj.io/t/revocation-db-invalid/30343/6 "2025-07-16T05:05:46Z")
It may indicate that something is changed with your Ceph cluster. But network storage has never been supported anyway, it can work until it stops working, and it looks like you’ve reached that limit. You may try to move this database to the local storage, it has an own parameter `server.revocation-dburl`, you may check the format: bash ```auto docker exec -it storagenode /app/bin/storagenode setup --help | grep "server.revocation-dburl" ``` PowerShell ```auto docker exec -it storagenode /app/bin/storagenode setup --help | sls "server.revocation-dburl" ``` You may add it as a parameter to the `config.yaml` file or as a variable in a format `STORJ_SERVER_REVOCATION_DBURL` or as a command line option `--server.revocation-dburl=bolt:///app/revocations.db` to your `docker run` command after the image name. If you use a `docker-compose.yaml`, then it would be in the command section: ```auto command: - --server.revocation-dburl=bolt:///app/revocations.db ``` of course it would disappear every time when you delete the container, so you may want to add a mapping to a local disk: ```auto docker run ... \ --mount type=bind,src=/usr/local/lib/storagenode/dbs,dst=/app/dbs \ ... storjlabs/storagenode:latest \ --server.revocation-dburl=bolt:///app/dbs/revocations.db ``` or an analogue for `docker-compose.yaml`: ```auto volumes: - type: bind source: /usr/local/lib/storagenode/dbs target: /app/dbs command: - --server.revocation-dburl=bolt:///app/dbs/revocations.db ``` ---
**Author:** ![bradkollmyer](https://storj.bcdn.literatehosting.com/letter_avatar/bradkollmyer/32/5_5575768a8748004e209b776fc1b2916d.png) [@bradkollmyer](https://forum.storj.io/u/bradkollmyer)\ **Post date:** [July 23, 2025, 9:20pm UTC](https://forum.storj.io/t/revocation-db-invalid/30343/7 "2025-07-23T21:20:39Z")
That worked to fixed my problem.