Lost peers would be explained by bad internet connection. Node restart would be explained by low ram or slow cpu.
Where did you run your node? What are it's specifications?
Please do that connection test and share it's results.
Where did you run your node? What are it's specifications?
Please do that connection test and share it's results.
This node is going offline 5 minutes before start validation (the countdown timer did not even appear). I made mistake and manually restart this PC, which caused an even longer launch of the node software itself. but the basic problem is that after a successful update it went into offline mode waiting for a new synchronization.
I can't doubt the bad connection, because the other node on the same radio worked perfectly and without problems all the time.
This is an internet connection:
Node is running on HP brand machine, i3, 6GB memory...
Of course, all other software was turned off, except regular Windows (win 7, there are no more regular updates which can cause network congestion)