# Error: Error creating revocation database: revocation database error: boltdb error: timeout

**URL:** <https://forum.storj.io/t/error-error-creating-revocation-database-revocation-database-error-boltdb-error-timeout/10139>\
**Category:** troubleshooting\
**Tags:** database\
**Created:** [November 9, 2020, 4:08pm UTC](https://forum.storj.io/t/error-error-creating-revocation-database-revocation-database-error-boltdb-error-timeout/10139 "2020-11-09T16:08:56Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![fdigennaro](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/fdigennaro/32/1133_2.png) [@fdigennaro](https://forum.storj.io/u/fdigennaro)\
**Post date:** [November 9, 2020, 4:08pm UTC](https://forum.storj.io/t/error-error-creating-revocation-database-revocation-database-error-boltdb-error-timeout/10139/1 "2020-11-09T16:08:56Z")

</div>

Hi  
It was necessary to restart my server, restarting the storagenode container is always restarting

I have this error in the log

> Error: Error creating revocation database: revocation database error: boltdb error: timeout

---

<div class="post-metadata">

**Author:** ![fdigennaro](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/fdigennaro/32/1133_2.png) [@fdigennaro](https://forum.storj.io/u/fdigennaro)\
**Post date:** [November 9, 2020, 4:19pm UTC](https://forum.storj.io/t/error-error-creating-revocation-database-revocation-database-error-boltdb-error-timeout/10139/2 "2020-11-09T16:19:39Z")

</div>

I’ve resolved by renaming revocations.db file and then restarting docker container.

---

<div class="post-metadata">

**Author:** ![Kozaks](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/kozaks/32/1128_2.png) [@Kozaks](https://forum.storj.io/u/Kozaks)\
**Post date:** [November 21, 2022, 7:47pm UTC](https://forum.storj.io/t/error-error-creating-revocation-database-revocation-database-error-boltdb-error-timeout/10139/3 "2022-11-21T19:47:36Z")

</div>

All my nodes are down. What’s going on? What can I do?

```auto
2022-11-21 19:27:02,679 INFO Set uid to user 0 succeeded
2022-11-21 19:27:02,689 INFO RPC interface 'supervisor' initialized
2022-11-21 19:27:02,689 INFO supervisord started with pid 1
2022-11-21 19:27:03,691 INFO spawned: 'processes-exit-eventlistener' with pid 11
2022-11-21 19:27:03,693 INFO spawned: 'storagenode' with pid 12
2022-11-21 19:27:03,695 INFO spawned: 'storagenode-updater' with pid 13
2022-11-21T19:27:03.774Z INFO Configuration loaded {"Process": "storagenode-updater", "Location": "/app/config/config.yaml"}
2022-11-21T19:27:03.774Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "server.private-address"}
2022-11-21T19:27:03.774Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "healthcheck.details"}
2022-11-21T19:27:03.774Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "storage.allocated-bandwidth"}
2022-11-21T19:27:03.774Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "storage.allocated-disk-space"}
2022-11-21T19:27:03.774Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "operator.email"}
2022-11-21T19:27:03.774Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "storage2.database-dir"}
2022-11-21T19:27:03.774Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "contact.external-address"}
2022-11-21T19:27:03.775Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "server.address"}
2022-11-21T19:27:03.775Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "console.address"}
2022-11-21T19:27:03.775Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "operator.wallet-features"}
2022-11-21T19:27:03.775Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "operator.wallet"}
2022-11-21T19:27:03.775Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "storage2.piece-scan-on-startup"}
2022-11-21T19:27:03.775Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "healthcheck.enabled"}
2022-11-21T19:27:03.776Z INFO Anonymized tracing enabled {"Process": "storagenode-updater"}
2022-11-21T19:27:03.778Z INFO Running on version {"Process": "storagenode-updater", "Service": "storagenode-updater", "Version": "v1.66.1"}
2022-11-21T19:27:03.778Z INFO Downloading versions. {"Process": "storagenode-updater", "Server Address": "https://version.storj.io"}
2022-11-21T19:27:03.846Z INFO Configuration loaded {"Process": "storagenode", "Location": "/app/config/config.yaml"}
2022-11-21T19:27:03.846Z INFO Anonymized tracing enabled {"Process": "storagenode"}
2022-11-21T19:27:03.847Z INFO Operator email {"Process": "storagenode", "Address": "xxxx"}
2022-11-21T19:27:03.847Z INFO Operator wallet {"Process": "storagenode", "Address": "xxx"}
2022-11-21T19:27:04.324Z INFO Current binary version {"Process": "storagenode-updater", "Service": "storagenode", "Version": "v1.66.1"}
2022-11-21T19:27:04.324Z INFO New version is being rolled out but hasn't made it to this node yet {"Process": "storagenode-updater", "Service": "storagenode"}
2022-11-21T19:27:04.343Z INFO Current binary version {"Process": "storagenode-updater", "Service": "storagenode-updater", "Version": "v1.66.1"}
2022-11-21T19:27:04.343Z INFO New version is being rolled out but hasn't made it to this node yet {"Process": "storagenode-updater", "Service": "storagenode-updater"}
Error: Error creating revocation database: revocation database: boltdb: timeout
        storj.io/storj/storage/boltdb.New:44
        storj.io/storj/private/revocation.openDBBolt:52
        storj.io/storj/private/revocation.OpenDB:35
        storj.io/storj/private/revocation.OpenDBFromCfg:23
        main.cmdRun:202
        storj.io/private/process.cleanup.func1.4:377
        storj.io/private/process.cleanup.func1:395
        github.com/spf13/cobra.(*Command).execute:852
        github.com/spf13/cobra.(*Command).ExecuteC:960
        github.com/spf13/cobra.(*Command).Execute:897
        storj.io/private/process.ExecWithCustomConfigAndLogger:92
        main.main:478
        runtime.main:255
2022-11-21 19:27:04,877 INFO success: processes-exit-eventlistener entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-11-21 19:27:04,878 INFO success: storagenode entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-11-21 19:27:04,878 INFO success: storagenode-updater entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-11-21 19:27:04,880 INFO exited: storagenode (exit status 1; not expected)
2022-11-21 19:27:05,882 INFO spawned: 'storagenode' with pid 45
2022-11-21 19:27:05,883 WARN received SIGQUIT indicating exit request
2022-11-21 19:27:05,883 INFO waiting for storagenode, processes-exit-eventlistener, storagenode-updater to die
2022-11-21T19:27:05.883Z INFO Got a signal from the OS: "terminated" {"Process": "storagenode-updater"}
2022-11-21 19:27:05,885 INFO stopped: storagenode-updater (exit status 0)
2022-11-21 19:27:05,886 INFO stopped: storagenode (terminated by SIGTERM)
2022-11-21 19:27:05,887 INFO stopped: processes-exit-eventlistener (terminated by SIGTERM)

```

---

<div class="post-metadata">

**Author:** ![heunland](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/heunland/32/6076_2.png) [@heunland](https://forum.storj.io/u/heunland)\
**Post date:** [November 21, 2022, 10:05pm UTC](https://forum.storj.io/t/error-error-creating-revocation-database-revocation-database-error-boltdb-error-timeout/10139/4 "2022-11-21T22:05:46Z")

</div>

did you already try the solution suggested in [this thread](https://forum.storj.io/t/error-error-creating-revocation-database-revocation-database-error-boltdb-error-timeout/10139/2)? Please consider first searching in this forum to see if the same issue has already been solved before, thanks!

---

<div class="post-metadata">

**Author:** ![Kozaks](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/kozaks/32/1128_2.png) [@Kozaks](https://forum.storj.io/u/Kozaks)\
**Post date:** [November 22, 2022, 10:08am UTC](https://forum.storj.io/t/error-error-creating-revocation-database-revocation-database-error-boltdb-error-timeout/10139/5 "2022-11-22T10:08:33Z")

</div>

Why revocation db is in config folder instead of defined folder for other databases?

---

<div class="post-metadata">

**Author:** ![kaloyan](https://storj.bcdn.literatehosting.com/letter_avatar/kaloyan/32/6_449c533f586939b6e5f246632a46421f.png) [@kaloyan](https://forum.storj.io/u/kaloyan)\
**Post date:** [November 22, 2022, 4:30pm UTC](https://forum.storj.io/t/error-error-creating-revocation-database-revocation-database-error-boltdb-error-timeout/10139/6 "2022-11-22T16:30:27Z")

</div>

There is a separate config for the location of the revocation db:

```auto
# url for revocation database (e.g. bolt://some.db OR redis://127.0.0.1:6378?db=2&password=abc123)
# server.revocation-dburl: bolt:///etc/storagenode/revocations.db

```

You can use it to change the location as desired.