Solvedchia blockchain full_node chia.full_node.full_node: ERROR Consensus error 124, not disconnecting[BUG]

Describe the bug
Installed new version 1.1.5
also tried recreated the wallet DB.

looked at logs and seen the following:

full_node chia.full_node.full_node: ERROR Consensus error 124, not disconnecting

To Reproduce
Install version 1.1.5
deleted wallet DB as instructed in #3561

If people are interest, we are launching a Chia Pool soon called https://Seedpool.org. Check it out.

Thanks for the explanation. But this should then be an INFO message, since it's not an error on my node's side... Also no ERROR messages should ever be ignored (do you also ignore errors in your web server/infrastructure logs?). That's just bad practice and poor craftsmanship what your're doing. I believe we can do better.

That error shows when a node running an older version (1.1.4 or older) tries to sync with your node. Those nodes potentially tries to sync invalid transactions which were fixed in 1.1.5, and so your node is rejecting them. This also means that as more nodes are upgraded you will see this error less. In short, it's working as intended and you can ignore the error.

Source: https://chiaforum.com/t/fyi-network-is-down-block-255108-upgrade-to-1-1-5-asap/2292/22

Yeah this being an ERROR is confusing and not correct, because it's not an error on your client and you can nothing do about it.
Furthermore, the message shouldn't say "consensus error" because no one know what this means. It should say something like "INFO: rejecting old client (pre 1.1.5)", so no one has to search the issues for a solution in panic.
Finally, it says "not disconnecting", which doesn't make sense because it obviously means "not letting client connect".

I'm impressed how fast you guys hotfixed the problem with negative value coins, but please let the debug messages tell your users something useful and don't let everything be an ERROR, because users want to fix ERRORS asap. ;)

Yes good feedback. This should probably be an info level. Usually if a peer sends us invalid blocks or transactions, that is an error and we instantly disconnect. Right now we are not disconnecting, so that we don't kick out old peers from the network, in this case.

A side effect of this is also that my logfile grew to 4gb within 3 or 4 days. And my loglevel is on warning. This might surprise some people down the line, if their Logfile is growing faster than their farming drives ^^