Fabio Di Fabio

@ajsutton beside this PR that after my last analysis is not helpful as I thought and will probably discard, let me clarify better that full sync already runs in parallel...

@kirillp if your node is still running and stuck, could you please run this command: `curl -X POST --data '{"jsonrpc":"2.0","method":"admin_peers","params":[],"id":1}' http://127.0.0.1:8545` and post the result? See also: https://besu.hyperledger.org/en/stable/Reference/API-Methods/#admin_peers

@kirillp probably on Window the command needs to be written differently, but I do not know how. If you node is still stuck, then a restart usually solves.

As commented [here](https://github.com/hyperledger/besu/pull/4175#issuecomment-1196418927) we should also focus on why Full sync is not able to recover these situation, since it runs in parallel to the block synchronization, so I am...

Probably is worth to have a feedback from @ahamlat on the potential performance changes that this could introduce

Release 22.10.0 has a first improvements that result in bigger blocks, please report your exeperience. We are currently monitoring and working on further improvements.

> > I think we need to first define which is our goal, because I see 2 possibility here: > > > > 1. Follow the specs, then we need...

I agree we can improve the logging, showing only the progress and critical errors, and pushing transient errors to debug. Instead for the timing, it is normal that it takes...

> Is this still open for PR consideration? Seems to be an easy fix, can do it this week. Please sync with @daniellehrner that is working on https://github.com/hyperledger/besu/pull/4451

Same problem here, did some debugging between an instance running Ubuntu 22.94 minimal (default shell is dash) and another one that is working and use Amazon Linux 2. What I...