Otra vez con reinicios!

El nodo había conseguido recuperarlo y sin más ha empezado otra vez a reiniciarse… Lo que no entiendo es que se haya cambiado la configuración y me dé este error:

2024-07-23T14:17:54Z INFO Configuration loaded {“Process”: “storagenode”, “Location”: “/app/config/config.yaml”}
2024-07-23T14:17:54Z INFO Invalid configuration file key {“Process”: “storagenode”, “Key”: “operator.email”}
2024-07-23T14:17:54Z INFO Invalid configuration file key {“Process”: “storagenode”, “Key”: “contact.external-address”}
2024-07-23T14:17:54Z INFO Invalid configuration file key {“Process”: “storagenode”, “Key”: “storage.allocated-disk-space”}
2024-07-23T14:17:54Z INFO Invalid configuration file key {“Process”: “storagenode”, “Key”: “storage.allocated-bandwidth”}
2024-07-23T14:17:54Z INFO Invalid configuration file key {“Process”: “storagenode”, “Key”: “operator.wallet”}
2024-07-23T14:17:54Z INFO Invalid configuration file key {“Process”: “storagenode”, “Key”: “server.private-address”}
2024-07-23T14:17:54Z INFO Invalid configuration file key {“Process”: “storagenode”, “Key”: “server.address”}
2024-07-23T14:17:54Z INFO Anonymized tracing enabled {“Process”: “storagenode”}

He encontrado esto también que me preocupa y creo que es por alguna actualización:

Error: Error migrating tables for database on storagenode: migrate: v58: database disk image is malformed
storj.io/storj/private/migrate.(*Migration).Run:212
storj.io/storj/storagenode/storagenodedb.(*DB).MigrateToLatest:425

El archivo config.yaml se comparte entre 2 procesos, por eso ves esas líneas de registro. Esto no es un error sino sólo una información. Puedes ver su etiqueta como INFO.

ok, entiendo. Pero he encontrado esto otro…

docker logs -f --tail 100 storagenode
[…]
2024-07-23 14:44:10,310 INFO exited: storagenode (exit status 1; not expected)
2024-07-23 14:44:11,312 INFO spawned: ‘storagenode’ with pid 64
2024-07-23 14:44:11,313 WARN received SIGQUIT indicating exit request
2024-07-23 14:44:11,313 INFO waiting for storagenode, processes-exit-eventlistener, storagenode-updater to die
2024-07-23T14:44:11Z INFO Got a signal from the OS: “terminated” {“Process”: “storagenode-updater”}
2024-07-23 14:44:11,314 INFO stopped: storagenode-updater (exit status 0)
2024-07-23T14:44:11Z INFO Configuration loaded {“Process”: “storagenode”, “Location”: “/app/config/config.yaml”}
2024-07-23T14:44:11Z INFO Anonymized tracing enabled {“Process”: “storagenode”}
2024-07-23T14:44:11Z INFO Operator email {“Process”: “storagenode”, “Address”: “”}
2024-07-23T14:44:11Z INFO Operator wallet {“Process”: “storagenode”, “Address”: “”}
2024-07-23T14:44:11Z INFO server kernel support for server-side tcp fast open remains disabled. {“Process”: “storagenode”}
2024-07-23T14:44:11Z INFO server enable with: sysctl -w net.ipv4.tcp_fastopen=3 {“Process”: “storagenode”}
2024-07-23T14:44:11Z INFO Telemetry enabled {“Process”: “storagenode”, “instance ID”: “”}
2024-07-23T14:44:11Z INFO Event collection enabled {“Process”: “storagenode”, “instance ID”: “”}
2024-07-23T14:44:11Z INFO db.migration.58 Remove unused trash column {“Process”: “storagenode”}
2024-07-23T14:44:11Z ERROR failure during run {“Process”: “storagenode”, “error”: “Error migrating tables for database on storagenode: migrate: v58: database disk image is malformed\n\tstorj.io/storj/private/migrate.(*Migration).Run:212\n\tstorj.io/storj/storagenode/storagenodedb.(*DB).MigrateToLatest:425\n\tmain.cmdRun:100\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.cleanup.func1.4:393\n\tstorj.io/common/process.cleanup.func1:411\n\tgithub.com/spf13/cobra.(*Command).execute:983\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1115\n\tgithub.com/spf13/cobra.(*Command).Execute:1039\n\tstorj.io/common/process.ExecWithCustomOptions:112\n\tmain.main:34\n\truntime.main:271”, “errorVerbose”: "Error migrating tables for database on storagenode: migrate: v58: database disk image is malformed\n\tstorj.io/storj/private/migrate.(*Migration).Run:212\n\tstorj.io/storj/storagenode/storagenodedb.(*DB).MigrateToLatest:425\n\tmain.cmdRun:100\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.cleanup.func1.4:393\n\tstorj.io/common/process.cleanup.func1:411\n\tgithub.com/spf13/cobra.(*Command).execute:983\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1115\n\tgithub.com/spf13/cobra.(*Command).Execute:1039\n\tstorj.io/common/process.ExecWithCustomOptions:112\n\tmain.main:34\n\truntime.main:271\n\tmain.cmdRun:102\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.cleanup.func1.4:393\n\tstorj.io/common/process.cleanup.func1:411\n\tgithub.com/spf13/cobra.(*Command).execute:983\n\tgithub.com/spf13/cobra.(Command).ExecuteC:1115\n\tgithub.com/spf13/cobra.(Command).Execute:1039\n\tstorj.io/common/process.ExecWithCustomOptions:112\n\tmain.main:34\n\truntime.main:271"}
Error: Error migrating tables for database on storagenode: migrate: v58: database disk image is malformed
** storj.io/storj/private/migrate.(Migration).Run:212

** storj.io/storj/storagenode/storagenodedb.(DB).MigrateToLatest:425

main.cmdRun:100
main.newRunCmd.func1:33
storj.io/common/process.cleanup.func1.4:393
storj.io/common/process.cleanup.func1:411
github.com/spf13/cobra.(*Command).execute:983
github.com/spf13/cobra.(*Command).ExecuteC:1115
github.com/spf13/cobra.(*Command).Execute:1039
storj.io/common/process.ExecWithCustomOptions:112
main.main:34
runtime.main:271
2024-07-23 14:44:11,785 INFO stopped: storagenode (exit status 1)
2024-07-23 14:44:11,785 INFO stopped: processes-exit-eventlistener (terminated by SIGTERM)

1 Like

Estoy aplicando… Me sale esto:

root@storj:/storj/datastorage/storage# docker run --rm -it --mount type=bind,source=${PWD},destination=/data sstc/sqlite3 find . -maxdepth 1 -iname ".db" -print0 -exec sqlite3 ‘{}’ ‘PRAGMA integrity_check;’ ‘;’
Unable to find image ‘sstc/sqlite3:latest’ locally
latest: Pulling from sstc/sqlite3
63b65145d645: Pull complete
a22c9f5fb7da: Pull complete
61b29bd318d0: Pull complete
Digest: sha256:59f29aaff0e2977eb5ac2cbc6a6d782b99fa9956dbd4bdf40ac3a612f8f0a80b
Status: Downloaded newer image for sstc/sqlite3:latest
./garbage_collection_filewalker_progress.dbok
./piece_expiration.db
** in database main ***
Page 2919: btreeInitPage() returns error code 11
Page 2915: btreeInitPage() returns error code 11
Page 2913: btreeInitPage() returns error code 11
Page 2428: btreeInitPage() returns error code 11
Page 2927: btreeInitPage() returns error code 11
Page 2920: btreeInitPage() returns error code 11
Page 2929: btreeInitPage() returns error code 11
Page 2917: btreeInitPage() returns error code 11
Page 1684: btreeInitPage() returns error code 11
Page 2918: btreeInitPage() returns error code 11
Page 2925: btreeInitPage() returns error code 11
Page 2928: btreeInitPage() returns error code 11
Page 2427: btreeInitPage() returns error code 11
Page 2924: btreeInitPage() returns error code 11
Page 2429: btreeInitPage() returns error code 11
Page 2424: btreeInitPage() returns error code 11
Page 2423: btreeInitPage() returns error code 11
Error: stepping, database disk image is malformed (11)
./info.dbok
./heldamount.dbok
./orders.dbok
./pricing.dbok
./notifications.dbok
./pieceinfo.dbok
./secret.dbok
./bandwidth.dbok
./piece_spaced_used.dbok
./storage_usage.dbok
./satellites.dbok
./reputation.dbok
./used_serial.dbok
./used_space_per_prefix.dbok

Siga los pasos dados en la guía para arreglar esta base de datos.

2 Likes

Arreglado! Muchas gracias! no lo hubiera encontrado sin tu ayuda!

2 Likes