Nico Flaig

@achingbrain I caught some DEBUG logs ([libp2p-debug.log](https://github.com/ChainSafe/lodestar/files/13112989/libp2p-debug.log)), I didn't see any `libp2p:*` logs afterwards but the `libp2p.stop` promise never resolved, and the process was not shutting down due to that....

> It's not clear from the logs when shutdown is started ([this line](https://github.com/libp2p/js-libp2p/blob/master/packages/libp2p/src/libp2p.ts#L254) is not present) Was capturing the logs in tmux which seems to only capture the last 2k...

> Does it happen with @libp2p/tcp from before https://github.com/libp2p/js-libp2p/pull/2058? E.g. when pinned to 8.0.7 Haven't seen the issue so far when [downgrading @libp2p/tcp to 8.0.7](https://github.com/ChainSafe/lodestar/compare/unstable...nflaig/downgrade-libp2p-tcp), it's been only 3 days...

@achingbrain it's been a week now and I haven't seen the issue, whereas before it would happen at least once a day on a long running beacon node process. If...

@achingbrain is https://github.com/libp2p/js-libp2p/pull/2421 expected to fix this issue? I can still see timeouts due to `libp2p.stop` resolving but our unstable branch should have that change as we recently updated `@libp2p/tcp`...

I am not sure having all lint config in a module is that great as it is less flexible. Lodestar is a huge codebase and different from libraries in some...

Additional information from [rocknet on discord](https://discord.com/channels/593655374469660673/743858262864167062/1147952397180739636) further indicates that the delay 30+ seconds could be caused by hashing the state and causing the request timeout ([default: 30s](https://github.com/ChainSafe/lodestar/blob/6646e23cfeb5b51ca6a5609befa2b329b993a65c/packages/beacon-node/src/eth1/provider/jsonRpcHttpClient.ts#L10)). - Version message...

- Should be implemented together with https://github.com/ChainSafe/lodestar/issues/6108. I can work on those

- Reopening as issue is not resolved by https://github.com/ChainSafe/lodestar/pull/5797 ``` ^CDec-01 16:48:48.925[] info: Stopping gracefully, use Ctrl+C again to force process exit Dec-01 16:48:50.981[execution] error: Execution client went offline oldState=SYNCED,...

> On a related note, at some point we should update the api error messages to be compliant with the Beacon API spec. I have looked at this before, it...