Test-network node does not start after update

Hi, my test-network node decided to automatically update and now does not start. I have tried to delete and recreate the docker container, but it still behaves the same.

2025-03-05 19:58:07 (52.6 MB/s) - '/tmp/storagenode.zip' saved [37713858/37713858]

2025-03-05 19:58:09,234 INFO Set uid to user 0 succeeded
2025-03-05 19:58:09,240 INFO RPC interface 'supervisor' initialized
2025-03-05 19:58:09,240 INFO supervisord started with pid 1
2025-03-05 19:58:10,244 INFO spawned: 'processes-exit-eventlistener' with pid 118
2025-03-05 19:58:10,246 INFO spawned: 'storagenode' with pid 119
2025-03-05 19:58:10,248 INFO spawned: 'storagenode-updater' with pid 120
2025-03-05T19:58:10Z    INFO    Configuration loaded    {"Process": "storagenode-updater", "Location": "/app/config/config.yaml"}
2025-03-05T19:58:10Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "server.use-peer-ca-whitelist"}
2025-03-05T19:58:10Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "server.address"}
2025-03-05T19:58:10Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "operator.wallet"}
2025-03-05T19:58:10Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "console.address"}
2025-03-05T19:58:10Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "storage.allocated-bandwidth"}
2025-03-05T19:58:10Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "operator.wallet-features"}
2025-03-05T19:58:10Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "server.private-address"}
2025-03-05T19:58:10Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "storage.allocated-disk-space"}
2025-03-05T19:58:10Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "storage2.trust.sources"}
2025-03-05T19:58:10Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "operator.email"}
2025-03-05T19:58:10Z    INFO    Invalid configuration file key  {"Process": "storagenode-updater", "Key": "contact.external-address"}
2025-03-05T19:58:10Z    INFO    Anonymized tracing enabled      {"Process": "storagenode-updater"}
2025-03-05T19:58:10Z    INFO    Running on version      {"Process": "storagenode-updater", "Service": "storagenode-updater", "Version": "v1.124.0-rc"}
2025-03-05T19:58:10Z    INFO    Downloading versions.   {"Process": "storagenode-updater", "Server Address": "https://version.qa.storj.io"}
2025-03-05T19:58:10Z    INFO    Configuration loaded    {"Process": "storagenode", "Location": "/app/config/config.yaml"}
2025-03-05T19:58:10Z    INFO    Anonymized tracing enabled      {"Process": "storagenode"}
2025-03-05T19:58:10Z    INFO    Operator email  {"Process": "storagenode", "Address": "p100@pentium100.com"}
2025-03-05T19:58:10Z    INFO    Operator wallet {"Process": "storagenode", "Address": "0xe5470344f4C4b3f72334d88AcD1b88A86Fb168D5"}
2025-03-05T19:58:10Z    INFO    server  kernel support for server-side tcp fast open remains disabled.  {"Process": "storagenode"}
2025-03-05T19:58:10Z    INFO    server  enable with: sysctl -w net.ipv4.tcp_fastopen=3  {"Process": "storagenode"}
2025-03-05T19:58:10Z    ERROR   failure during run      {"Process": "storagenode", "error": "Failed to create storage node peer: hashstore: invalid header checksum: 0 != b24a8b203efcceb0\n\tstorj.io/storj/storagenode/hashstore.ReadTblHeader:87\n\tstorj.io/storj/storagenode/hashstore.OpenHashtbl:132\n\tstorj.io/storj/storagenode/hashstore.NewStore:250\n\tstorj.io/storj/storagenode/hashstore.New:94\n\tstorj.io/storj/storagenode/piecestore.(*HashStoreBackend).getDB:248\n\tstorj.io/storj/storagenode/piecestore.NewHashStoreBackend:114\n\tstorj.io/storj/storagenode.New:598\n\tmain.cmdRun:84\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.cleanup.func1.4:392\n\tstorj.io/common/process.cleanup.func1:410\n\tgithub.com/spf13/cobra.(*Command).execute:985\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1117\n\tgithub.com/spf13/cobra.(*Command).Execute:1041\n\tstorj.io/common/process.ExecWithCustomOptions:112\n\tmain.main:34\n\truntime.main:272", "errorVerbose": "Failed to create storage node peer: hashstore: invalid header checksum: 0 != b24a8b203efcceb0\n\tstorj.io/storj/storagenode/hashstore.ReadTblHeader:87\n\tstorj.io/storj/storagenode/hashstore.OpenHashtbl:132\n\tstorj.io/storj/storagenode/hashstore.NewStore:250\n\tstorj.io/storj/storagenode/hashstore.New:94\n\tstorj.io/storj/storagenode/piecestore.(*HashStoreBackend).getDB:248\n\tstorj.io/storj/storagenode/piecestore.NewHashStoreBackend:114\n\tstorj.io/storj/storagenode.New:598\n\tmain.cmdRun:84\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.cleanup.func1.4:392\n\tstorj.io/common/process.cleanup.func1:410\n\tgithub.com/spf13/cobra.(*Command).execute:985\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1117\n\tgithub.com/spf13/cobra.(*Command).Execute:1041\n\tstorj.io/common/process.ExecWithCustomOptions:112\n\tmain.main:34\n\truntime.main:272\n\tmain.cmdRun:86\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.cleanup.func1.4:392\n\tstorj.io/common/process.cleanup.func1:410\n\tgithub.com/spf13/cobra.(*Command).execute:985\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1117\n\tgithub.com/spf13/cobra.(*Command).Execute:1041\n\tstorj.io/common/process.ExecWithCustomOptions:112\n\tmain.main:34\n\truntime.main:272"}
Error: Failed to create storage node peer: hashstore: invalid header checksum: 0 != b24a8b203efcceb0
        storj.io/storj/storagenode/hashstore.ReadTblHeader:87
        storj.io/storj/storagenode/hashstore.OpenHashtbl:132
        storj.io/storj/storagenode/hashstore.NewStore:250
        storj.io/storj/storagenode/hashstore.New:94
        storj.io/storj/storagenode/piecestore.(*HashStoreBackend).getDB:248
        storj.io/storj/storagenode/piecestore.NewHashStoreBackend:114
        storj.io/storj/storagenode.New:598
        main.cmdRun:84
        main.newRunCmd.func1:33
        storj.io/common/process.cleanup.func1.4:392
        storj.io/common/process.cleanup.func1:410
        github.com/spf13/cobra.(*Command).execute:985
        github.com/spf13/cobra.(*Command).ExecuteC:1117
        github.com/spf13/cobra.(*Command).Execute:1041
        storj.io/common/process.ExecWithCustomOptions:112
        main.main:34
        runtime.main:272
2025-03-05 19:58:10,461 WARN exited: storagenode (exit status 1; not expected)

It tries to restart a few times and then gives up. The node was working before the update.

Are you running a -rc version?

Yes, it’s for the test network.

My normal node is unaffected.

Do you mean a storj-sim or do you have joined a test satellite?

For the test satellite. I have tried to update it again and it started, but the version was slightly different, so I guess you fixed the problem.

Yes, we released a new version, the previous one has had a bug.