i keep getting this error during bootup. how do i fix this? 2024-07-25T15:14:38Z ERROR failure during run {"Process": "storagenode", "error": "Error checking version for storagenode database: validate db version mismatch: expected 26, but current version is 60\n\tstorj.io/storj/private/migrate.(*Mi…

when your NodeID would be eligible. How is it happened that your node have been upgraded to a not fully released version? Ok, right now you can download a new v1.114.6 binaries for your platform and extract them to the bin subfolder in your data location, then restart the container.

You can run something like this on the host. Change the variables to match. #!/bin/bash VERSION=v1.104.1 CONTAINER=storagenode ARCH=$(docker exec $CONTAINER printenv GOARCH) cat <<EOF | docker exec -i $CONTAINER bash wget https://github.com/storj/storj/releases/download/$VERSION/storagenode_linux…

This is a new format for these files used in 1.108.x, and they are incompatible with a previous version. This node cannot be downgraded to any previous version. [image] nerdatwork: Did you rename the file? You should remove the .pb from the file name. they shouldn’t touch anything in the sto…

there was a power interruption yesterday, and after that, the nodes keeps restarting. i didnt done anything for version related. but i tried removing all *.db files but didnt work so i remove the newly create dbs and i put back the old *.db, heres the log docker logs 1sn -f downloading storagenode…

the sn is running now. but im seeing alot of 2024-07-26T15:53:01Z WARN collector unable to delete piece {“Process”: “storagenode”, “Satellite ID”: is this expected?

this is weird. i haven’t changed anything today, yet both my SNs are now running again. was it related to the version? did i just got rolled back yesterday?

[image] clearing: but im seeing alot of [image] V58 db migrate fail - piece_expiration.db - 1.108.3 troubleshooting It looks like they have made a fix for one of those issues. Just needs to be released. storagenode/{collector,pieces}: batch up collection of expired …

Race condition in the update process in docker (when the new version is incompatible with the old one) opened 03:25AM - 30 Jul 24 UTC (UTC) [AlexeyALeonov] AlexeyALeonov …

its happening again. 2024-10-09T05:59:10Z FATAL Unrecoverable error {"Process": "storagenode", "error": "Error checking version for storagenode database: validate db version mismatch: expected 56, but current version is 62\n\tstorj.io/storj/private/migrate.(*Migration).ValidateVersions:141\n\tstorj…

Yes, because you need to download a version, which has this database migration. I may guess, but it should be the same which was running before. Please search in the logs, which one you have used before. It should print that to the logs when it’s checking for a new version. By the way, why do you n…

Hi, i am using the official image of storagenode. [image] the version is v1.113.2 2024-10-09T11:35:47Z INFO Anonymized tracing enabled {"Process": "storagenode-updater"} 2024-10-09T11:35:47Z INFO Running on version {"Process": "storagenode-updater", "Service": "storagenode-updater", "Version": "…

ERROR Error updating service

Node Operators troubleshooting

nerdatwork July 26, 2024, 4:36pm 12