Info.db Failure

Node Operators troubleshooting
1

Greetings the warriors of the decentralized world! :slight_smile:

If we are having info.db file access issue as mentioned below log outputs, is it better to delete the node permanently and create a new node from the scratch by formatting the related HDD?
If there is a way to fix this issue somehow, could you please guide me?
This issue is also related to the topic that I created a couple of days ago…

Error: Error starting master database on storagenode: database: info opening file "config/storage/info.db" failed: file is not a database

docker logs --tail 50 storagenode
        storj.io/private/process.ExecWithCustomConfigAndLogger:92
        main.main:478
        runtime.main:250
2023-04-19 22:26:23,397 INFO exited: storagenode (exit status 1; not expected)
2023-04-19 22:26:25,417 INFO spawned: 'storagenode' with pid 57
2023-04-19T22:26:25.990Z        INFO    Configuration loaded    {"Process": "storagenode", "Location": "/app/config/config.yaml"}
2023-04-19T22:26:25.993Z        INFO    Anonymized tracing enabled      {"Process": "storagenode"}
2023-04-19T22:26:26.103Z        INFO    Operator email  {"Process": "storagenode", "Address": "nazimyildiz90@gmail.com"}
2023-04-19T22:26:26.104Z        INFO    Operator wallet {"Process": "storagenode", "Address": "0x412c63a480cfcc6a3bd771cc33a181ba8e098067"}       
Error: Error starting master database on storagenode: database: info opening file "config/storage/info.db" failed: file is not a database
        storj.io/storj/storagenode/storagenodedb.(*DB).openDatabase:331
        storj.io/storj/storagenode/storagenodedb.(*DB).openExistingDatabase:308
        storj.io/storj/storagenode/storagenodedb.(*DB).openDatabases:283
        storj.io/storj/storagenode/storagenodedb.OpenExisting:250
        main.cmdRun:193
        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:250
2023-04-19 22:26:26,124 INFO exited: storagenode (exit status 1; not expected)
2023-04-19 22:26:29,145 INFO spawned: 'storagenode' with pid 67
2023-04-19T22:26:29.712Z        INFO    Configuration loaded    {"Process": "storagenode", "Location": "/app/config/config.yaml"}
2023-04-19T22:26:29.715Z        INFO    Anonymized tracing enabled      {"Process": "storagenode"}
2023-04-19T22:26:29.828Z        INFO    Operator email  {"Process": "storagenode", "Address": "abcdefg90@gmail.com"}
2023-04-19T22:26:29.830Z        INFO    Operator wallet {"Process": "storagenode", "Address": "0xXXXXXXXXXXXXXXXXXXXXXXXXX"}

Lastly, my Suspension and Online scores were below %70 for all of the satellites.

2
3

Thank you, Alexey, I’ve followed this guide and what happened is as below.

  • The info.db was deleted and the rest of the database files were backed up
  • All .db files were deleted under the storage folder and the node started again. New database files were created
  • The node was stopped and backup files were copied under the storage folder
  • The node started again but this time other database file threw away an error which is
Error: Error starting master database on storagenode: database: heldamount opening file "config/storage/heldamount.db" failed: file is not a database

Basically, this error exists for all database files. So what should I do as the next step?
Shall I start with completely empty database files? If I do that what will be the pros and cons for me?

Thank you very much for your help :slight_smile:

4

If all your databases corrupted, then you can do not move them back, leave the node running with a new ones.
See