Tom Dalla

+1 This is a great tool for optimising performance, but it would be even better if we could rebind selected divs for data that doesn't change often (not real time)...

+1, jcenter won't work in a few days ``` jcenter is deprecated Builds will no longer be able to resolve artifacts from JCenter after February 1st, 2022 ```

Attached slightly longer logs: [nethermind_logs.txt](https://github.com/NethermindEth/nethermind/files/9575657/nethermind_logs.txt) Except the `ERROR` messages for the unhealthy response, there's only one `WARN`, but that one doesn't make the node unhealthy: ``` nethermind | 2022-09-15 11:34:55.9880|INFO|JsonRpc.JsonRpcService|Executing...

Happened again: it briefly goes unhealthy (and alerts me) before going back healthy (seconds later). I had been running for weeks before `The Merge` and did not have that issue....

Same for me. I added a "grace period" of one minute on the first failure and it stopped the alerts. I can see in the logs that there are transient...

Sure. I'm running it on Docker and using Nimbus as the CL client.\ For completeness in case it's relevant, this is the fallback node of my main box that is...

Has the issue been fixed in the next release?

+1, updated to `1.14.3` about a day ago and no health check failures since then. Last *failed* entry (on the previous version): ``` 2022-10-03 13:47:10,410 (nethermind.py:30) INFO The node is...

Side question on that topic: when we set the `feeRecipient` and `gasLimit` via the validator REST APIs, does it update the `proposerConfig.json` file as well? Or is it just "in-memory"...

Any solution? Changing the `/etc/passwd` makes it impossible to `ssh` so looking for "The Syno Way"...