Error creating revocation database: revocation database error: boltdb error: invalid database

Node Operators troubleshooting
1

Hey guys i try to have my second node running via docker on the same host.
I created a new identity for the storage node and gave it another mount point for the config dir.
So the Problem is that i get errrors from the second container. The first runs fine but my second throws me following error:

2021-04-30T13:06:14.170Z	INFO	Configuration loaded	{"Location": 
"/app/config/config.yaml"},
2021-04-30T13:06:14.222Z	INFO	Operator email	{"Address": "andreschuele@gmail.com"},
2021-04-30T13:06:14.222Z	INFO	Operator wallet	{"Address": "0xebDC5CE870F753316E022624B72bDF0f54abf712"},
2021-04-30T13:06:14.224Z	INFO	db	database does not exists	{"database": "info"},
2021-04-30T13:06:14.224Z	INFO	db	database does not exists	{"database": "bandwidth"},
2021-04-30T13:06:14.224Z	INFO	db	database does not exists	{"database": "orders"},
2021-04-30T13:06:14.224Z	INFO	db	database does not exists	{"database": "piece_expiration"},
2021-04-30T13:06:14.224Z	INFO	db	database does not exists	{"database": "pieceinfo"},
2021-04-30T13:06:14.224Z	INFO	db	database does not exists	{"database": "piece_spaced_used"},
2021-04-30T13:06:14.224Z	INFO	db	database does not exists	{"database": "reputation"},
2021-04-30T13:06:14.224Z	INFO	db	database does not exists	{"database": "storage_usage"},
2021-04-30T13:06:14.224Z	INFO	db	database does not exists	{"database": "used_serial"},
2021-04-30T13:06:14.224Z	INFO	db	database does not exists	{"database": "satellites"},
2021-04-30T13:06:14.225Z	INFO	db	database does not exists	{"database": "notifications"},
2021-04-30T13:06:14.225Z	INFO	db	database does not exists	{"database": "heldamount"},
2021-04-30T13:06:14.225Z	INFO	db	database does not exists	{"database": "pricing"},
2021-04-30T13:06:14.225Z	INFO	db	database does not exists	{"database": "secret"},
Error: Error creating revocation database: revocation database error: boltdb error: invalid database,
	storj.io/storj/storage/boltdb.New:44,
```
2

Czy zrobiłeś dla drugiego węzła “konfigurację wstępną”?

docker run --rm -e SETUP="true" \
    --mount type=bind,source="<identity-dir>",destination=/app/identity \
    --mount type=bind,source="<storage-dir>",destination=/app/config \
    --name storagenode storjlabs/storagenode:latest
3

Yes i have done this :slight_smile:

4

And still:

???

This may be a directory permission problem …

5

Yes still database does not exists.
Ok i will check them.

6

@peem Is it a problem that i mounted the config dir as rclone sftp?

7

He doesn’t understand what you are doing :frowning:

8

@peem

I have an sftp Server. And i want to run a second node on this sftp server.
So i installed rclone and mounted the sftp storage to a mount point on my server.
i created a new identity and configured the docker container to use that new identity.
The config dir and the database are laying in the mounted rclone sftp directory.

Maybe its now more understandable? :slight_smile:

9

He understands nothing. But if you have the same done for the first node and it works then you have to repeat the configuration for the second …

All I know is that network protocols such as SMB and NFS are not stable enough to ensure a stable node operation (for databases). Maybe only ISCSI (in the LAN) is stable enough. Overall - only locally mounted disk storage is supported (SATA, USB), not disk storage on remote server …

10

Just - run the node directly on that server

1 Like
11

This will not work. The storagenode is incompatible with any network protocols except iSCSI.