The CLI becomes unresponsive on a Dynode running on a VPS. The underlying daemon is also apparently unresponsive. This seemingly happens randomly. I have not found a coloration between the unresponsiveness and any given event. However, this only "seems" to occur on a VPS running more than one Dynode.
Steps to reproduce
- Run multiple Dynodes on a single VPS
- Wait until it becomes unresponsive. (it seems to be rare)
- I created a custom script to capture the log in the event that the CLI becomes unresponsive.
What platform are you using (Linux, Windows, Mac)
Ubuntu 18.04.3 LTS (GNU/Linux 4.15.0-65-generic x86_64)
Description
See attached for the debug output. Note that each "Unknown error" report gives a 250 line dump of the log file. It runs every 5 min, so a lot of it repeats from error to error. The error code "143" is caused by the "timeout --preserve-status -k 45s 40s " that is used before each CLI command to detect freezing. Please note that the line that says "CLI Unknown Error 143: Shutting Down" is a typo, I was not attempting to shut down the Dynode, I should have typed in "dumping log".
dynamiccd_A.error.txt
As a side note, I also have a sequence daemon running on the same VPS. It was also unresponsive when Dynode A had the issue. The act of restarting the sequence daemon caused the dynamic CLI to become responsive and the script was then able to heal the issue.
I can improve the error reporting if there is something you want to catch. Crashes have been very rare for me, but I was able to capture this when I loaded up a single instance with multiple Dynodes. (yes each has its own IPv4 address)
The CLI becomes unresponsive on a Dynode running on a VPS. The underlying daemon is also apparently unresponsive. This seemingly happens randomly. I have not found a coloration between the unresponsiveness and any given event. However, this only "seems" to occur on a VPS running more than one Dynode.
Steps to reproduce
What platform are you using (Linux, Windows, Mac)
Ubuntu 18.04.3 LTS (GNU/Linux 4.15.0-65-generic x86_64)
Description
See attached for the debug output. Note that each "Unknown error" report gives a 250 line dump of the log file. It runs every 5 min, so a lot of it repeats from error to error. The error code "143" is caused by the "timeout --preserve-status -k 45s 40s " that is used before each CLI command to detect freezing. Please note that the line that says "CLI Unknown Error 143: Shutting Down" is a typo, I was not attempting to shut down the Dynode, I should have typed in "dumping log".
dynamiccd_A.error.txt
As a side note, I also have a sequence daemon running on the same VPS. It was also unresponsive when Dynode A had the issue. The act of restarting the sequence daemon caused the dynamic CLI to become responsive and the script was then able to heal the issue.
I can improve the error reporting if there is something you want to catch. Crashes have been very rare for me, but I was able to capture this when I loaded up a single instance with multiple Dynodes. (yes each has its own IPv4 address)