[Bug] Tons of "WARNING Rate limiting ourselves. message type: respond_peers" messages in log

What happened?

After upgrade to 1.5.1 (from 1.5.0), full node shows a large number of “WARNING Rate limiting ourselves. message type: respond_peers” messages in debug.log. Full node is in sync. Most connected peers are in sync, have even farmed a block since the upgrade, but these warning messages are filling up the log.

Version

1.5.1

What platform are you using?

Linux

What ui mode are you using?

CLI

Relevant log output

2022-08-23T22:56:57.376 full_node full_node_server        : WARNING  Rate limiting ourselves. message type: respond_proof_of_weight, peer: 31.19.126.71
2022-08-23T22:56:58.384 full_node full_node_server        : WARNING  Rate limiting ourselves. message type: respond_proof_of_weight, peer: 31.19.126.71
2022-08-23T22:56:59.391 full_node full_node_server        : WARNING  Rate limiting ourselves. message type: respond_proof_of_weight, peer: 31.19.126.71
2022-08-23T22:57:01.625 full_node full_node_server        : WARNING  Rate limiting ourselves. message type: respond_peers, peer: 190.16.85.253
2022-08-23T22:57:01.626 full_node full_node_server        : WARNING  Rate limiting ourselves. message type: respond_peers, peer: 109.111.131.6

Last 5 lines of log

Since upgrade, 1851 lines of this message type has shown up in log, with a total of 14 unique IPs.

[CEduardoGR]

Anyone reporting these problems, can you also share what pool you are with?

I’m farming solo and I have this problem too. I also have a few of this message but it is far less frequent than the respond_peers message:

full_node full_node_server : WARNING Rate limiting ourselves. message type: respond_end_of_sub_slot, peer:

And also this one (repeated with the node ID of each harvester, several times):

farmer chia.plot_sync.receiver : ERROR reset: node_id ebd9821959799dff28ccf5f5d0efeef9b341444131349a1029678f41dc7df54e, current_sync: [state 0, sync_id 0, next_message_id 0, plots_processed 0, plots_total 0, delta [valid +0/-0, invalid +0/-0, keys missing: +0/-0, duplicates: +0/-0], time_done None]

The last message has its own topic already.

The warnings and the error came with version 1.5.1. I took another look in the archived logs to see if the errors where there and the frequency they occurred before but couldn’t find them, it is pretty clear to me that 1.5.1 is the culprit for introducing all this problems.

[emlowe]

There are some config.yaml settings you can adjust if you want:

log_maxfilesrotation - keep this many log files in rotation. default is 7 log_maxbytesrotation - max bytes in log before rotating, default is 52428800 (50 MiB) log_use_gzip - compress rotated logs, default false.

So for example, you could keep more but smaller rotated logs, etc.