Odd error in syslog - BLOG ERROR blog_request :blog_key corruption when deleting flow for ...

[MvW]

I have an odd error in syslog, which I've never seen before and the forum search has only little results, and none of the situations others describe are applicable. Nothing has changed, just out of the blue I see:

Apr  1 20:22:54 RT-AC86U kernel: [0;33;41mBLOG ERROR blog_request :blog_key corruption when adding flow net_p=ffffffc0087f79a8  dir=0 old_key=0x2000343a new_key=0x20003448
Apr  1 20:22:54 RT-AC86U kernel: [0m
Apr  1 20:22:54 RT-AC86U kernel: [0;33;41mBLOG ERROR blog_request :blog_key corruption when adding flow net_p=ffffffc00bc217d8  dir=0 old_key=0x2000343d new_key=0x20003449
Apr  1 20:22:54 RT-AC86U kernel: [0m
Apr  1 20:24:28 RT-AC86U kernel: [0;33;41mBLOG ERROR blog_request :blog_key corruption when deleting flowfor net_p=ffffffc00bc217d8 
Apr  1 20:24:28 RT-AC86U kernel: [0m
Apr  1 20:26:51 RT-AC86U kernel: [0;33;41mBLOG ERROR blog_request :blog_key corruption when deleting flowfor net_p=ffffffc0087f79a8 
Apr  1 20:26:51 RT-AC86U kernel: [0m
Apr  1 20:29:51 RT-AC86U kernel: [0;33;41mBLOG ERROR blog_request :blog_key corruption when adding flow net_p=ffffffc0087f79a8  dir=0 old_key=0x2000348a new_key=0x20003497
Apr  1 20:29:51 RT-AC86U kernel: [0m
Apr  1 20:29:58 RT-AC86U kernel: [0;33;41mBLOG ERROR blog_request :blog_key corruption when adding flow net_p=ffffffc00bc217d8  dir=0 old_key=0x20003490 new_key=0x20003499
Apr  1 20:29:58 RT-AC86U kernel: [0m
Apr  1 20:33:16 RT-AC86U kernel: [0;33;41mBLOG ERROR blog_request :blog_key corruption when deleting flowfor net_p=ffffffc0087f79a8 
Apr  1 20:33:16 RT-AC86U kernel: [0m
Apr  1 20:33:16 RT-AC86U kernel: [0;33;41mBLOG ERROR blog_request :blog_key corruption when deleting flowfor net_p=ffffffc00bc217d8 
Apr  1 20:33:16 RT-AC86U kernel: [0m

As it happened in previous versions I can't imagine it has to with beta 3, I've made no changes to the network or the routers settings today, I only just logged in to check for updates in amtm and noticed these in uiScribe. I don't use Wireguard or Cloudflare Warp (as suggested cause in the search results). I have two OpenVPN clients connect to ProtonVPN in two different countries, I use NextDNS CLI for DNS resolution and the rest is in my signature. I have an inactive installation of Diversion, just for it's mailing functionality. Any clues as to what could be causing this strange error?

I've never seen it before.

Best regards,
Marco

 

[Butterfly Bones]

Know issue, see RMerlin reply in this thread.

BLOG ERROR blog_request Entries in System Log 86U

I've never seen this error, and though it gave me a chuckle, need to know what is going on. No options/addons just a plain vanilla install with some port forwarding. The router has been rock solid for months, then this. Jan 3 17:33:49 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key...

www.snbforums.com

 

[MvW]

Know issue, see RMerlin reply in this thread.

Yeah, I found that during my search before posting, but as Eric doesn't know either (at least not in his reply 27 months ago, because it's part of proprietary broadcom part), I was kinda hoping somebody got any more info in the meantime.

I can't stand errors just popping up out the middle of nowhere, with no logical explanation whatsoever, and most of the time vanishing again after some time, never to be seen again. It is as if our routers are completely living their own lives.

 

[L&LD]

But, they are.

 

[pdc]

For what it's worth, with 386.2 beta3 my AiMesh node (only!) started getting strange messages regarding blog_request as well. If I revert to beta1 they go away.

Apr  3 10:20:04 AC86U-OFFICE kernel: blog_request 1502: dev dpsta put_stats           (null)
(etc...)

Release - Asuswrt-Merlin 386.2 is now available

NTP still doesn't work with Asus_Merlin 386.2 It works with Asus 386.41994 My router is RT-AC68U in Repeater mode.

www.snbforums.com

Edit: I poked around some more and found my messages were caused by a patch from Asus in beta3 that added the log message. Those changes do not appear to be related to your log message at all, sorry for the false alarm.

 

[MvW]

Thanks for poking around. I just added the messages to one of the scribe filters and decide to drop them, as they kept coming back and apparently there's no fix yet.