So my node started reboot by it self, every up to 40min.
I found that:
find -maxdepth 1 -iname “*.db” -print0 -exec sqlite3 ‘{}’ ‘PRAGMA integrity_check;’ ‘;’
./reputation.dbok
./piece_expiration.dbok
./pieceinfo.dbok
./piece_spaced_used.db*** in database main ***
Page 5: btreeInitPage() returns error code 11
Error: stepping, database disk image is malformed (11)
./info.dbok
./storage_usage.dbok
./used_serial.dbok
./orders.dbok
./notifications.dbok
./heldamount.dbok
./satellites.dbok
./pricing.dbok
./bandwidth.db*** in database main ***
Page 19845: btreeInitPage() returns error code 11
Page 19181: btreeInitPage() returns error code 11
Page 19879: btreeInitPage() returns error code 11
Page 19866: btreeInitPage() returns error code 11
Page 19738: btreeInitPage() returns error code 11
Error: stepping, database disk image is malformed (11)
./secret.dbok
so i fix it. Now i have:
find -maxdepth 1 -iname “*.db” -print0 -exec sqlite3 ‘{}’ ‘PRAGMA integrity_check;’ ‘;’
./reputation.dbok
./piece_expiration.dbok
./pieceinfo.dbok
./piece_spaced_used.dbok
./info.dbok
./storage_usage.dbok
./used_serial.dbok
./orders.dbok
./notifications.dbok
./heldamount.dbok
./satellites.dbok
./pricing.dbok
./bandwidth.dbok
./secret.dbok
BUT still when i run the node, it stops and gives this error:
2024-02-24T14:50:37Z INFO Current binary version {"Process": "storagenode-updater", "Service": "storagenode-updater", "Version": "v1.96.6"}
2024-02-24T14:50:37Z INFO Version is up to date {"Process": "storagenode-updater", "Service": "storagenode-updater"}
2024-02-24T14:50:37Z INFO server kernel support for server-side tcp fast open remains disabled. {"process": "storagenode"}
2024-02-24T14:50:37Z INFO server enable with: sysctl -w net.ipv4.tcp_fastopen=3 {"process": "storagenode"}
2024-02-24T14:50:37Z INFO Telemetry enabled {"process": "storagenode", "instance ID": "12Tna3C4LrMXzUn3GJmwuCAopFPJGmH6mXyzfF5HiY2G5Uapuoh"}
2024-02-24 14:50:37,897 INFO success: processes-exit-eventlistener entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-02-24 14:50:37,899 INFO success: storagenode entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-02-24 14:50:37,900 INFO success: storagenode-updater entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-02-24T14:50:37Z INFO Event collection enabled {"process": "storagenode", "instance ID": "12Tna3C4LrMXzUn3GJmwuCAopFPJGmH6mXyzfF5HiY2G5Uapuoh"}
2024-02-24T14:50:37Z INFO db.migration Database Version {"process": "storagenode", "version": 54}
Error: Error during preflight check for storagenode databases: preflight: database "bandwidth": expected schema does not match actual: &dbschema.Schema{
Tables: {&{Name: "bandwidth_usage", Columns: {&{Name: "action", Type: "INTEGER"}, &{Name: "amount", Type: "BIGINT"}, &{Name: "created_at", Type: "TIMESTAMP"}, &{Name: "satellite_id", Type: "BLOB"}}}, &{Name: "bandwidth_usage_rollups", Columns: {&{Name: "action", Type: "INTEGER"}, &{Name: "amount", Type: "BIGINT"}, &{Name: "interval_start", Type: "TIMESTAMP"}, &{Name: "satellite_id", Type: "BLOB"}}, PrimaryKey: {"action", "interval_start", "satellite_id"}}},
- Indexes: []*dbschema.Index{
- s`Index<Table: bandwidth_usage, Name: idx_bandwidth_usage_created, Columns: created_at, Unique: false, Partial: "">`,
- s`Index<Table: bandwidth_usage, Name: idx_bandwidth_usage_satellite, Columns: satellite_id, Unique: false, Partial: "">`,
- },
+ Indexes: nil,
Sequences: nil,
}
storj.io/storj/storagenode/storagenodedb.(*DB).preflight:429
storj.io/storj/storagenode/storagenodedb.(*DB).Preflight:376
main.cmdRun:108
main.newRunCmd.func1:32
storj.io/private/process.cleanup.func1.4:393
storj.io/private/process.cleanup.func1:411
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:112
main.main:30
runtime.main:267
2024-02-24 14:50:38,019 INFO exited: storagenode (exit status 1; not expected)
2024-02-24 14:50:39,027 INFO spawned: 'storagenode' with pid 98
2024-02-24 14:50:39,028 WARN received SIGQUIT indicating exit request
2024-02-24 14:50:39,029 INFO waiting for storagenode, processes-exit-eventlistener, storagenode-updater to die
2024-02-24T14:50:39Z INFO Got a signal from the OS: "terminated" {"Process": "storagenode-updater"}
2024-02-24 14:50:39,041 INFO stopped: storagenode-updater (exit status 0)
2024-02-24 14:50:39,048 INFO stopped: storagenode (terminated by SIGTERM)
2024-02-24 14:50:39,049 INFO stopped: processes-exit-eventlistener (terminated by SIGTERM)
Is there any way to fix it?
/dev/sda1 5.5T 4.9T 316G 95% /home/node/storj/8
Is it to full ? Or where is the problem?
I know even ready to delete all DB’s lost info, but keep the node alive.
Thank you.
