-
Notifications
You must be signed in to change notification settings - Fork 12
Open
Description
*** Normal operation:
If you launch a node (or update the node)
./run_node.sh -n TESTNET --ip xxx.xxx.xx.xxx
it will execute the batch file to download the node binary and launch it smoothly.
*** Bug:
If by mistake you launch with sudo
sudo ./run_node.sh -n TESTNET --ip xxx.xxx.xx.xxx
It will still execute the batch file, but will download a full copy of the parity database before launching the container.
Then you are stuck with launching everytime with "sudo ./run_node.sh", which is not recommended. It does not work when calling again "./run_node.sh" (without sudo) : docker container output is restarting continuously)
*** Workaround (unsuccessful)
- Deleting the full database and removing the aleph_node_runner directory, git pull and restarting won't be a success.
*** Solution found
- Clean reinstall of ubuntu server and
./run_node.sh -n TESTNET --ip xxx.xxx.xx.xxx
works.
Metadata
Metadata
Assignees
Labels
No labels