Error: Error starting master database on storagenode:

Meine node ist heute gecrasht und das ist meine fehlermeldung:
My node crashed today and this is my error message:

2023-07-06T17:47:53.856Z        INFO    Operator wallet {"process": "storagenode", "Address": "XXXXXXXXX"}
Error: Error starting master database on storagenode: database: bandwidth opening file "config/storage/bandwidth.db" failed: file is not a database
        storj.io/storj/storagenode/storagenodedb.(*DB).openDatabase:347
        storj.io/storj/storagenode/storagenodedb.(*DB).openExistingDatabase:324
        storj.io/storj/storagenode/storagenodedb.(*DB).openDatabases:299
        storj.io/storj/storagenode/storagenodedb.OpenExisting:266
        main.cmdRun:62
        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-07-06 17:47:53,871 INFO exited: storagenode (exit status 1; not expected)
2023-07-06 17:47:55,878 INFO spawned: 'storagenode' with pid 52
2023-07-06T17:47:55.978Z        INFO    Configuration loaded    {"process": "storagenode", "Location": "/app/config/config.yaml"}
2023-07-06T17:47:55.979Z        INFO    Anonymized tracing enabled      {"process": "storagenode"}
2023-07-06T17:47:55.982Z        INFO    Operator email  {"process": "storagenode", "Address": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"}
2023-07-06T17:47:55.982Z        INFO    Operator wallet {"process": "storagenode", "Address": "xxxxxxxxxxxxxxxxxxxxxxxxxxxx"}
Error: Error starting master database on storagenode: database: bandwidth opening file "config/storage/bandwidth.db" failed: file is not a database
        storj.io/storj/storagenode/storagenodedb.(*DB).openDatabase:347
        storj.io/storj/storagenode/storagenodedb.(*DB).openExistingDatabase:324
        storj.io/storj/storagenode/storagenodedb.(*DB).openDatabases:299
        storj.io/storj/storagenode/storagenodedb.OpenExisting:266
        main.cmdRun:62
        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-07-06 17:47:55,997 INFO exited: storagenode (exit status 1; not expected)
2023-07-06 17:47:59,009 INFO spawned: 'storagenode' with pid 61
2023-07-06T17:47:59.173Z        INFO    Configuration loaded    {"process": "storagenode", "Location": "/app/config/config.yaml"}
2023-07-06T17:47:59.174Z        INFO    Anonymized tracing enabled      {"process": "storagenode"}
2023-07-06T17:47:59.177Z        INFO    Operator email  {"process": "storagenode", "Address": "xxxxxxxxxxxxxxxxxxxxxxxxxxxx"}
2023-07-06T17:47:59.178Z        INFO    Operator wallet {"process": "storagenode", "Address": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"}
Error: Error starting master database on storagenode: database: bandwidth opening file "config/storage/bandwidth.db" failed: file is not a database
        storj.io/storj/storagenode/storagenodedb.(*DB).openDatabase:347
        storj.io/storj/storagenode/storagenodedb.(*DB).openExistingDatabase:324
        storj.io/storj/storagenode/storagenodedb.(*DB).openDatabases:299
        storj.io/storj/storagenode/storagenodedb.OpenExisting:266
        main.cmdRun:62
        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-07-06 17:47:59,193 INFO exited: storagenode (exit status 1; not expected)
2023-07-06 17:48:00,195 INFO gave up: storagenode entered FATAL state, too many start retries too quickly

sehe ich das richtig das die einzige l├Âsung folgende ist:
I see that the only solution is the following:

oder habe ich etwas ├╝bersehen
or have I missed something

dinge wie restart, etc habe ich schon versucht danke f├╝r die hilfe
things like restart, etc I have already tried thanks for the help

Wenn Sie sicher sind, dass das Ziel richting ist und die Dateien sich wirklich in der Mappe befinden, die Sie als Mount mitgegeben habe. Dann ist die l├Âsung richtig.

1 Like

woher wei├č ich ob das Ziel richtig ist und die Daten ini der Mappe sind?

Nein, du hast nichts ├╝bersehen. Deine bandwidth.db ist offenbar kaputt und du musst sie wie dort beschrieben neu erstellen lassen und ersetzen.

1 Like

Wenn es sich um einen Docker-Knoten handelt, k├Ânnen Sie sehen, welchen Pfad Sie in der Option --mount angegeben haben.
Und Sie k├Ânnen diesen Pfad wie folgt ├╝berpr├╝fen (geben Sie Ihren Pfad anstelle von /mnt/storj/storagenode an):

ls -l /mnt/storj/storagenode/storage/*.db

Wenn Sie eine Liste mit Datenbanken sehen, haben Sie den richtigen Pfad eingegeben.

1 Like