Error creating revocation database

Node Operators troubleshooting
1

I am trying to setup a storj node, but I keep running into the error below.

The revocations.db file in the storage folder has been created, but it looks empty. Also the container created a bunch of other files in the directory, so i assume its not a permission issue (like it was the case with similar threads with this error).

What did I do wrong in the setup?

2023-09-03T17:20:00Z	INFO	db	database does not exist	{"process": "storagenode", "database": "info"}
2023-09-03T17:20:00Z	INFO	db	database does not exist	{"process": "storagenode", "database": "bandwidth"}
2023-09-03T17:20:00Z	INFO	db	database does not exist	{"process": "storagenode", "database": "orders"}
2023-09-03T17:20:00Z	INFO	db	database does not exist	{"process": "storagenode", "database": "piece_expiration"}
2023-09-03T17:20:00Z	INFO	db	database does not exist	{"process": "storagenode", "database": "pieceinfo"}
2023-09-03T17:20:00Z	INFO	db	database does not exist	{"process": "storagenode", "database": "piece_spaced_used"}
2023-09-03T17:20:00Z	INFO	db	database does not exist	{"process": "storagenode", "database": "reputation"}
2023-09-03T17:20:00Z	INFO	db	database does not exist	{"process": "storagenode", "database": "storage_usage"}
2023-09-03T17:20:00Z	INFO	db	database does not exist	{"process": "storagenode", "database": "used_serial"}
2023-09-03T17:20:00Z	INFO	db	database does not exist	{"process": "storagenode", "database": "satellites"}
2023-09-03T17:20:00Z	INFO	db	database does not exist	{"process": "storagenode", "database": "notifications"}
2023-09-03T17:20:00Z	INFO	db	database does not exist	{"process": "storagenode", "database": "heldamount"}
2023-09-03T17:20:00Z	INFO	db	database does not exist	{"process": "storagenode", "database": "pricing"}
2023-09-03T17:20:00Z	INFO	db	database does not exist	{"process": "storagenode", "database": "secret"}

Error: Error creating revocation database: revocation database: boltdb: no such device
	storj.io/storj/private/kvstore/boltdb.New:42
	storj.io/storj/private/revocation.openDBBolt:52
	storj.io/storj/private/revocation.OpenDB:35
	storj.io/storj/private/revocation.OpenDBFromCfg:23
	main.cmdRun:71
	main.newRunCmd.func1:32
	storj.io/private/process.cleanup.func1.4:399
	storj.io/private/process.cleanup.func1:417
	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.ExecWithCustomOptions:113
	main.main:30
	runtime.main:250
2023-09-03 17:20:00,776 INFO exited: storagenode (exit status 1; not expected)
2

Check mount points, check filesystem on the device that is mounted there,

Lastly, review this: https://support.storj.io/hc/en-us/sections/360004515252-Databases-Issues

Describe your setup.
Just based on the log – issues with mount point.

3

Hello @molnart,
Welcome to the forum!

It should be created not in the storage folder, but in the parent folder, near the config.yaml file.
So, please check permissions for the data location. Your user should have rwx permissions for this folder.

4

i see only two folder options, the identity and the storage, so thdse are the only place where the revocations.db file can be created.

my setup looks like this:

docker run -d --restart unless-stopped --stop-timeout 300 \
    -p 28967:28967/tcp \
    -p 28967:28967/udp \
    -p 127.0.0.1:14002:14002 \
    -e WALLET="0x.........................................." \
    -e EMAIL="............@........com" \
    -e ADDRESS="..................:28967" \
    -e STORAGE="6TB" \
    --user $(id -u):$(id -g) \
    --mount type=bind,source="/srv/dev-disk-by-uuid-6a783240-d831-4733-9a6c-075770839750/OMV-data/docker/storj/Identity/storagenode",destination=/app/identity \
    --mount type=bind,source="/srv/mergerfs/Data_all/storj",destination=/app/config \
    --name storagenode storjlabs/storagenode:latest

There are revovactions.db files both in the identity files both in the storage folder, and in the identity folder that was created when i created my identity.

5

Don’t use mergefs. It will backfire. Maybe it already did, which is why you are seeing disappearing files.

1 Like
6

This database should be created there:

so, please make sure that your user is the owner of this folder and all other subfolders and files inside it.

@arrogantrabbit is right - do not use mergefs, your node will be disqualified after the one disk failure.