Logs spam in ethdocker and sedge

[MarekM25]

Starting from 1.20 we have lots of spam in logs in ethdocker and we have it in sedge as well. Here is how it looks for eth_docker

And how it should look (even without colors):

We should check NLog configurations for sedge and ethdocker

FYI: @yorickdowne

[yorickdowne]

I am using the NLog as it’s in the image, without any adjustments made. Thanks for taking a look!

[smartprogrammer93]

could it be something to do with the way we create our docker images?

[yorickdowne]

Possibly - the NLog.Config is in the image. Does it differ in the image to how it would otherwise be deployed?

[yorickdowne]

In case that helps, here is the NLog.config as it is shipped in the image

NLog.config.txt

[yorickdowne]

Looking through that config, here's what I don't see. If this existed, it would likely stop the RPC spam.

  <rules>
    <logger name="JsonRpc.*" minlevel="Warn" writeTo="file-async" final="true" />
    <logger name="JsonRpc.*" minlevel="Warn" writeTo="auto-colored-console-async" final="true" />
    <logger name="JsonRpc.*" final="true" />

It may be as simple as adding rules for "JsonRpc.*"

[emlautarom1]

@yorickdowne The NLog.config file you provided looks like exactly like the one we have on this repo, except for a invisible character at the begging (maybe an issue when sharing the file?)

Could you please provide details on how are you running Nethermind? It would be great if you could share:

• The full command used to run Nethermind (use docker inspect -f "{{.Name}} {{.Config.Cmd}}" [container-id] if you're using Docker).
• The first ~100 logs (use docker logs [container-id] | head -n 100 if you're using Docker).

[emlautarom1]

We were able to find the root cause and a fix is already available on #6097. With this change you should not see any more spam related to HTTP calls.