It is not Docker. And as I have said, I did not change anything except replacing the storagenode and dashboard binaries with the new versions.
Node 1 is running. Node 2 enters a failed state always after
IIRC 1.16.1 adds a secret DB and reverting to previous version might negatively impact your node. I am not sure what the secret DB does though but wanted you to know.
don’t go backwards in versions… it’s really really dangerous for your databases…
might not kill your node this time around, but you really cannot know what kind of damage it can cause.
tho it may be unlikely to fully kill your node… it might ruin all the databases if you are really unlucky.
common practice is never to roll back software that controls databases unless if the software is certified / built with that feature in mind.
ofc sometimes one doesn’t follow the rules to make stuff work… but then one better understand the risk assessment involved.
I wouldn’t advice to ever roll back versions espically if your node isn’t new, if your testing who cares but if your running this node long term once you update don’t go back. With the binary files you can easily just delete the binary and replace with a different version.
So it seems to be fixed by now. The issue was that the node ran out of memory processing thousand over thousands of unsent orders.
After manually sorting the good ones from the corrupted ones v 1.16.1 is working without error or restarting.
You need to locate your orders/unsent folder. It depends on your OS and settings where it is. Normally it is next to the ‘storage’ folder where the blobs are in resp. where your config.yaml is.
Then you move all orders out of the unsent folder into a new folder, I believe you have to stop the node first.
Then you move them back in 1 by 1 or in batches and start up the node.
Upon start, the node tries to send the orders and fails sending if encountering a corrupted order which you then can dispose. This you repeat until all you have identified all corrupted ones