I got the node stopped unexpectedly from yesterday. It was running 24/7 flawlessly from 1 year and now suddently stopped and cannot start.
I reinstalled the node setup but have the same issue.
Here is the log from NAS Container Manager looks like:
Please make sure that you used only straight quotes " and not a curly ones “ and ”, use double dashes -- and not hyphens –.
Use a plain text editor to form the command, not word processors, because they could replace all these characters to a fancy ones but incompatible with the terminal.
Does -e expression 1 means the wallet address? Maybe you got hacked and they changed the wallet?
I would stop and remove the container, change the SSH port to something else than 22, maybe investigate if something nefarious is running on the machine, and restart the container after copy-paste the wallet address from the wallet app into the run command.
They can change a few characters and you miss them on a quick look. I heard so many cases of changed addresses that looked so similar to the original one.
Of course, do what Alexey sugests, use Notepad++ to edit commands, use straight quotes, double dash --, etc, but I imagine these are not the problem if the node worked untill now and you didn’t input anything.
I would mask the wallet address also when post on forums. You can use the option “<> insert code”, to paste your command in the forum. It would format it better.
I saved my last paraghraph used to work before, bout double checked what you suggested now. All seem to be ok as text punctuation.
I am thinking to migrate it to a windows pc, but I guess copying almost 10tb of data will take longer than the node will be disqualified from the network…
What do you recommend to do here?
I think you are right, as long as nothing was changed in terms of ports settings etc. before container crush.
Below is the commands I did yesterday to remove and reinstall again the container. Perhaps something is not right here… but I cannot see it
Maybe could ring a bell to someone about this one. Nas is working well. I did a speed test and there are the same results as before this unfortunate event.
What is the name of the other storagenode?
One has to be storagenode, the other storagenode2, with different identity and different paths for each, if both are on the same machine.
Check the run command for both at the paramether:
–name
And you need to use different ports for server address I believe. So you need to add one more paramether or edit the config.yaml.
Also, change the log level, because now, it uses the one set in config.yaml, and the default is info, which will fill up your drive quicker than the client’s data.