09:32:04 <moneromooo> Can someone who has a large history of level 1 logs (or at least net.cn:ERROR) check whether they have instances of "Got NOTIFY_RESPONSE_CHAIN_ENTRY past expected height, dropping connection" please ?
09:43:29 <m-relay> <r​brunner7:monero.social> I guess this is something different - just had it now catching up about 1 week of chain: 2024-09-27 09:42:10.560	E [209.222.252.83:18081 OUT] Got NOTIFY_RESPONSE_CHAIN_ENTRY out of the blue, dropping connection
09:44:07 <m-relay> <r​brunner7:monero.social> Although that daemon is a few months old, compiled master
10:03:11 <m-relay> <r​brunner7:monero.social> Had one now:
10:03:13 <m-relay> <r​brunner7:monero.social> 2024-09-27 09:59:31.858	E [181.27.66.171:18080 OUT] Got NOTIFY_RESPONSE_CHAIN_ENTRY past expected height, dropping connection
10:04:14 <m-relay> <r​brunner7:monero.social> Maybe that's just "daily live of a Monero daemon" nowadays, if I get it at first attempt merely syncing 1 week or so?
10:30:34 <gingeropolous_> moneromooo, i have 11 instances, 7 are in the past 4 days. the other 4 are from 2021
10:31:37 <gingeropolous_> apparently i saved some log files from 2021 for some reason, but that string is present
10:35:57 <gingeropolous_> but on that machine, my logs only span from 09/22 to 09/27, except for those random ones from 2021
10:48:14 <Guest92> Helllo everyome
10:56:45 <sech1> I don't have it my node's logs but I don't run level 1 all the time - only when I need to debug stuff
10:57:22 <sech1> I'll run with log level 1 for a while
10:57:27 <m-relay> <r​brunner7:monero.social> Funny, I have also some logs from 2021 still standing, like g​ingeropolous_. Maybe a bug or at least a quirk in the log rotation code?
10:59:15 <gingeropolous_> naw, i think i grepped the logfiles at that time with "error", because the file those are found in is error.log , next to some other files named with that date
11:15:58 <sech1> log level 1 is too verbose, I switched to level 0 + net.cn:ERROR
12:23:22 <moneromooo> Thanks.
12:24:02 <moneromooo> rbrunner7: that "out of the blue" is plausibly/probably a very late answer, after a timeout, so your node doesn't expect a reply anymore.
12:25:46 <moneromooo> It's an error I got in townforge, but looking at the code I expected to see it in monerod too. I did not see it in my own logs, but they're only a couple days old.
12:26:40 <moneromooo> I *think* protocol is accessing the chain at two places and expecting those states to be consistent, but they are not.
12:26:58 <moneromooo> In this case it's mostly innocuous.