BLOG ERROR blog_request Entries in System Log 86U

[GHammer]

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 corruption when adding flow net_p=ffffffc0157d5538  dir=0 old_key=0x20001adf new_key=0x20001ae5
Jan  3 17:33:49 kernel: ^[[0m
Jan  3 17:35:22 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when deleting flowfor net_p=ffffffc0157d5538
Jan  3 17:35:22 kernel: ^[[0m
Jan  3 18:34:18 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when adding flow net_p=ffffffc01362cc18  dir=0 old_key=0x200021ba new_key=0x200021c6
Jan  3 18:34:18 kernel: ^[[0m
Jan  3 18:35:24 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when deleting flowfor net_p=ffffffc01362cc18
Jan  3 18:35:24 kernel: ^[[0m
Jan  3 19:43:40 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when adding flow net_p=ffffffc013467380  dir=0 old_key=0x20002d1e new_key=0x20002d2f
Jan  3 19:43:40 kernel: ^[[0m
Jan  3 19:44:51 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when deleting flowfor net_p=ffffffc013467380
Jan  3 19:44:51 kernel: ^[[0m
Jan  3 19:48:40 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when adding flow net_p=ffffffc014b138a8  dir=0 old_key=0x20002dba new_key=0x20002df9
Jan  3 19:48:40 kernel: ^[[0m
Jan  3 19:49:46 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when deleting flowfor net_p=ffffffc014b138a8
Jan  3 19:49:46 kernel: ^[[0m
Jan  3 19:53:40 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when adding flow net_p=ffffffc0151fd538  dir=0 old_key=0x20002ebd new_key=0x20002ecd
Jan  3 19:53:40 kernel: ^[[0m
Jan  3 19:54:51 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when deleting flowfor net_p=ffffffc0151fd538
Jan  3 19:54:51 kernel: ^[[0m
Jan  3 19:58:40 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when adding flow net_p=ffffffc014b2b010  dir=0 old_key=0x20002f6c new_key=0x20002f7b
Jan  3 19:58:40 kernel: ^[[0m
Jan  3 19:59:56 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when deleting flowfor net_p=ffffffc014b2b010
Jan  3 19:59:56 kernel: ^[[0m
Jan  3 20:03:40 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when adding flow net_p=ffffffc01508add0  dir=0 old_key=0x2000302f new_key=0x2000303b
Jan  3 20:03:40 kernel: ^[[0m
Jan  3 20:05:00 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when deleting flowfor net_p=ffffffc01508add0
Jan  3 20:05:00 kernel: ^[[0m
Jan  3 20:08:40 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when adding flow net_p=ffffffc014826538  dir=0 old_key=0x200030e4 new_key=0x200030f4
Jan  3 20:08:40 kernel: ^[[0m

 

[GHammer]

Well, I wiped the jffs on a restart and found that the ssh key had changed. I'll watch it for a spell to see if that was the culprit. Likely so.

ECDSA host key for 10.10.100.1 has changed and you have requested strict checking.
Host key verification failed.

 

[GHammer]

No, that didn't correct the error.
Something has corrupted keys.

Jan  4 09:17:40 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when adding flow net_p=ffffffc01744a010  dir=0 old_key=0x20000305 new_key=0x20000307
Jan  4 09:17:40 kernel: ^[[0m
Jan  4 09:18:06 dropbear[1629]: Password auth succeeded for 'admin' from 10.10.100.100:49525
Jan  4 09:19:33 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when deleting flowfor net_p=ffffffc01744a010
Jan  4 09:19:33 kernel: ^[[0m

 

[RMerlin]

Blog is an internal Broadcom module. Only they would know what the message means.

 

[GHammer]

Blog is an internal Broadcom module. Only they would know what the message means.

Well, I think I'll restore to factory settings and rebuild manually.
If that does not correct the error, I'll have to contact ASUS.

 

[ColinTaylor]

Google doesn't turn up much on those messages, but there are a couple. The first points the finger of suspicion at link aggregation and the other at a WireGuard install. So if you're using either of those I suggest you leave them disabled initially.

 

[GHammer]

No, none of those.

I’m at a loss.

I will try a factory reset later.

I do wonder if it is related to using bridged adapter in VirtualBox to give a virtual machine a network IP.

 

[GHammer]

Just a follow up.
I didn't do a factory reset as it didn't add up to me.
I built a physical machine, removed the virtual machine from service and disabled the nic it used (just in case).
No more errors coming from the router.
I don't know what VirtualBox 6 is doing when you run a guest in bridged adapter mode, but the router didn't like it.

 

[maxbraketorque]

I'm now seeing this error too on one of my AC86Us operating in router mode.

 

[maxbraketorque]

Since this error message is from a Broadcom module, I figured that it would be tied to the wifi functions, but the message still persists even with both wireless radios turned off. So this may actually be due to something on the ethernet.

 

[maxbraketorque]

I've now traced the source of the message to my HP printer that is connected to the router via ethernet. I have the printer manually set to 100 mbps full duplex in the printer configuration settings. I suspect that even though full duplex is a valid setting, it is causing an issue. I've enabled half duplex and will see what happens.

 

[GHammer]

Since this error message is from a Broadcom module, I figured that it would be tied to the wifi functions, but the message still persists even with both wireless radios turned off. So this may actually be due to something on the ethernet.

It was absolutely ethernet. It came with a bridged NIC and left with the removal of the bridge. There is no WiFi associated with the servers.
You are on the right track.

 

[maxbraketorque]

When moving the printer to my standalone switch, the Blog error messages go away, so the issue seems to manifest only when particular devices are etherneted into the switch on the AC86U.

One thing I noticed is that the printer is capable of full duplex communication at 100 mbps, and when I set it to that mode, it shows up on the AC86U switch as 100 mbps half duplex, but when its attached to the standalone switch, the standalone switch reports the printer connection as 100 mbps full duplex. Trying all the other network connection options (100 mbps half duplex, and 10 mbps half or full duplex) also still cause the mBlog error when the printer is attached to the AC86U switch. So perhaps there is some sort of error in the Broadcom module associated with negotiating duplex status with at 10 and 100 mbps speeds.

One additional comment is that the standalone switch (a managed MS510TX) is not reporting any errors with the printer attached to it.

 

[cooloutac]

i get this issue too i thought it was due to me when i start a vpn app on my phone sometimes. now you got me wondering if it is the magick jack i have ethernet in at 100MBs. i notice now though right before the message i get Oct 27 14:28:48 kernel: br0: received packet on eth6 with own address as source address