Closed JeffXiesk closed 2 years ago
Hi Jeff, sorry for the late response! I tried to run the local deployment too and indeed the nodes wouldn't connect to each other. But I found the reason and the fix.
The problem was that by default, TLS is enabled and the (dummy) TLS certificates that are part of the repository are expired. This can be resolved in 2 ways:
cd tls-data
./generate.sh -f # The -f option forces re-generation even of certificates that are already present
UseTLS
to false
in config-file-templates/mir-modular.yml
(From experience so far, using TLS has no observable impact on performance anyway)For remote deployments, I expect this issue not to occur, as certificates are always freshly generated with remote deployments.
Ohh, The problem has been fixed perfectly. Thanks for your kind and detailed response !
Hi, when I am working on branch research-iss in Ubuntu 20.04, after finishing installing and deployment described in readme, and I try to run example 3 (local example) in deployment.
However, no matter how many times I run, it always ends up with the result below. Terminal
master-log.log
Below is the process status. (By running
ps -aux
) In the status, we can see that most state of the process is Sl+ or S+, which means it is interruptible sleep (waiting for an event to complete), but what are the processes waiting?It says it is waiting until they connect to each other. I am so confused and wondering why, am I missing some operation or something wrong? And how to fix it?
Thank you soooo much!