adrienmo
commented
5 years ago it's weird, the only thing I can think about now would be:
- the remaining node is not responding in less than 2000 ms so it times out
- the remaining node does not have application log enabled
- the remaining node is stuck at the same block height
2 out of 3 of the RPC nodes lagged. However, the configuration of the Neoscan was:
NEO_SEEDS: "http://eco-neo-csharp-node1-running:30333;http://eco-neo-csharp-noderpc1-running:30334;http://eco-neo-csharp-noderpc1-running:30337"Node at port 30334 was still on top. Neoscan has been stuck for more than 2 hours and just returned after restarting those 2 nodes.
However, it may not be a problem of neoscan, since dockers swarm (or docker-compose) still lose connection in some weird scenarios.