blog_key corruption when adding / deleting flowfor net_p

[mrkorky]

I recently purchased a RT-AC86U router and I keep seeing the lines similar to below in the general log. I've searched online and through forums and couldn't find any helpful information. Any idea what is causing the error and what I might be able to do to stop the error from occurring?

May 10 13:58:47 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when adding flow net_p=ffffffc005491dd0 dir=0 old_key=0xa0001678 new_key=0xa00020fb
May 10 13:58:47 kernel: ^[[0m
May 10 13:58:47 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when adding flow net_p=ffffffc00540edd0 dir=0 old_key=0xa00021de new_key=0xa00027ea
May 10 13:58:47 kernel: ^[[0m
May 10 13:58:48 kernel: ERR: bdmf_attrelem_add_as_buf#4250: ucast: status:Entry already exists. attribute:flow index:4294967295
May 10 13:58:48 kernel: ^[[0;33;41m[ERROR pktrunner] runnerUcast_activate,1971: Cannot rdpa_ucast_flow_add^[[0m
May 10 13:58:48 kernel: ERR: bdmf_attrelem_add_as_buf#4250: ucast: status:Entry already exists. attribute:flow index:4294967295
May 10 13:58:48 kernel: ^[[0;33;41m[ERROR pktrunner] runnerUcast_activate,1971: Cannot rdpa_ucast_flow_add^[[0m
May 10 13:58:48 kernel: ERR: bdmf_attrelem_add_as_buf#4250: ucast: status:Entry already exists. attribute:flow index:4294967295
May 10 13:58:48 kernel: ^[[0;33;41m[ERROR pktrunner] runnerUcast_activate,1971: Cannot rdpa_ucast_flow_add^[[0m
May 10 13:59:35 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when adding flow net_p=ffffffc0114648a8 dir=0 old_key=0xa0001f39 new_key=0xa0002018
May 10 13:59:35 kernel: ^[[0m
May 10 14:00:34 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when deleting flowfor net_p=ffffffc00540edd0
May 10 14:00:34 kernel: ^[[0m
May 10 14:00:34 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when deleting flowfor net_p=ffffffc005491dd0
May 10 14:00:34 kernel: ^[[0m
May 10 14:01:28 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when deleting flowfor net_p=ffffffc0114648a8
May 10 14:01:28 kernel: ^[[0m

I did open a ticket with Asus and received this response "Please advise that our Research and Development team had reviewed the log file and they are normal, won't affect any functionality of the router. " I've already reset the router multiple times using the WPS button as well as the Restore w/ initialize. I also tried following OE's suggested install method and it's still occurring.

 

[OzarkEdge]

I recently purchased a RT-AC86U router and I keep seeing the lines similar to below in the general log. I've searched online and through forums and couldn't find any helpful information. Any idea what is causing the error and what I might be able to do to stop the error from occurring?

May 10 13:58:47 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when adding flow net_p=ffffffc005491dd0 dir=0 old_key=0xa0001678 new_key=0xa00020fb
May 10 13:58:47 kernel: ^[[0m
May 10 13:58:47 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when adding flow net_p=ffffffc00540edd0 dir=0 old_key=0xa00021de new_key=0xa00027ea
May 10 13:58:47 kernel: ^[[0m
May 10 13:58:48 kernel: ERR: bdmf_attrelem_add_as_buf#4250: ucast: status:Entry already exists. attribute:flow index:4294967295
May 10 13:58:48 kernel: ^[[0;33;41m[ERROR pktrunner] runnerUcast_activate,1971: Cannot rdpa_ucast_flow_add^[[0m
May 10 13:58:48 kernel: ERR: bdmf_attrelem_add_as_buf#4250: ucast: status:Entry already exists. attribute:flow index:4294967295
May 10 13:58:48 kernel: ^[[0;33;41m[ERROR pktrunner] runnerUcast_activate,1971: Cannot rdpa_ucast_flow_add^[[0m
May 10 13:58:48 kernel: ERR: bdmf_attrelem_add_as_buf#4250: ucast: status:Entry already exists. attribute:flow index:4294967295
May 10 13:58:48 kernel: ^[[0;33;41m[ERROR pktrunner] runnerUcast_activate,1971: Cannot rdpa_ucast_flow_add^[[0m
May 10 13:59:35 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when adding flow net_p=ffffffc0114648a8 dir=0 old_key=0xa0001f39 new_key=0xa0002018
May 10 13:59:35 kernel: ^[[0m
May 10 14:00:34 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when deleting flowfor net_p=ffffffc00540edd0
May 10 14:00:34 kernel: ^[[0m
May 10 14:00:34 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when deleting flowfor net_p=ffffffc005491dd0
May 10 14:00:34 kernel: ^[[0m
May 10 14:01:28 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when deleting flowfor net_p=ffffffc0114648a8
May 10 14:01:28 kernel: ^[[0m

I did open a ticket with Asus and received this response "Please advise that our Research and Development team had reviewed the log file and they are normal, won't affect any functionality of the router. " I've already reset the router multiple times using the WPS button as well as the Restore w/ initialize. I also tried following OE's suggested install method and it's still occurring.

Change among the last two firmwares, 81792 and 81858, maybe it will stop. Also, observe the router as you configure it to see if you determine when it starts. And, you could take Asus at their word.

OE

 

[PhilG1300]

I recently purchased a RT-AC86U router and I keep seeing the lines similar to below in the general log. I've searched online and through forums and couldn't find any helpful information. Any idea what is causing the error and what I might be able to do to stop the error from occurring?

May 10 13:58:47 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when adding flow net_p=ffffffc005491dd0 dir=0 old_key=0xa0001678 new_key=0xa00020fb
May 10 13:58:47 kernel: ^[[0m
May 10 13:58:47 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when adding flow net_p=ffffffc00540edd0 dir=0 old_key=0xa00021de new_key=0xa00027ea
May 10 13:58:47 kernel: ^[[0m
May 10 13:58:48 kernel: ERR: bdmf_attrelem_add_as_buf#4250: ucast: status:Entry already exists. attribute:flow index:4294967295
May 10 13:58:48 kernel: ^[[0;33;41m[ERROR pktrunner] runnerUcast_activate,1971: Cannot rdpa_ucast_flow_add^[[0m
May 10 13:58:48 kernel: ERR: bdmf_attrelem_add_as_buf#4250: ucast: status:Entry already exists. attribute:flow index:4294967295
May 10 13:58:48 kernel: ^[[0;33;41m[ERROR pktrunner] runnerUcast_activate,1971: Cannot rdpa_ucast_flow_add^[[0m
May 10 13:58:48 kernel: ERR: bdmf_attrelem_add_as_buf#4250: ucast: status:Entry already exists. attribute:flow index:4294967295
May 10 13:58:48 kernel: ^[[0;33;41m[ERROR pktrunner] runnerUcast_activate,1971: Cannot rdpa_ucast_flow_add^[[0m
May 10 13:59:35 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when adding flow net_p=ffffffc0114648a8 dir=0 old_key=0xa0001f39 new_key=0xa0002018
May 10 13:59:35 kernel: ^[[0m
May 10 14:00:34 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when deleting flowfor net_p=ffffffc00540edd0
May 10 14:00:34 kernel: ^[[0m
May 10 14:00:34 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when deleting flowfor net_p=ffffffc005491dd0
May 10 14:00:34 kernel: ^[[0m
May 10 14:01:28 kernel: ^[[0;33;41mBLOG ERROR blog_request :blog_key corruption when deleting flowfor net_p=ffffffc0114648a8
May 10 14:01:28 kernel: ^[[0m

I did open a ticket with Asus and received this response "Please advise that our Research and Development team had reviewed the log file and they are normal, won't affect any functionality of the router. " I've already reset the router multiple times using the WPS button as well as the Restore w/ initialize. I also tried following OE's suggested install method and it's still occurring.

mrkorky,
Did you get a resolution to this issue.
I am seeing the same on my AC86U, have been using merlin firmware but back on stock ASUS now and still seeing the issue.
I did raise a ticket with ASUS, I have had some response. I thought I had fixed the problem and closed the ticket, but now I am still seeing the BLOG ERROR and some times get many together. I have also witnessed my router restarting a few times if there are too many errors!
Regards
Phil

 

[Donga120]

mrkorky,
Did you get a resolution to this issue.
I am seeing the same on my AC86U, have been using merlin firmware but back on stock ASUS now and still seeing the issue.
I did raise a ticket with ASUS, I have had some response. I thought I had fixed the problem and closed the ticket, but now I am still seeing the BLOG ERROR and some times get many together. I have also witnessed my router restarting a few times if there are too many errors!
Regards
Phil

I have the same issue now too. Seems to only happen when Wi-Fi connections are added. If no Wi-Fi connections are added, it seems fine.

 

[kennymc.c]

I have also noticed these strange log entries recently. They occur about every 3-5 minutes. I was wondering 4 days ago because my AC86U seems to have rebooted at some point. Could have to do with the messages as mentioned above. Otherwise, however, I have not noticed any strange behavior. I run a WAN reboot watch script every 3 minutes, but it doesn't cause any messages when I start it manually.

 

[Donga120]

Mine are completely random, once they start the don't stop, even after a reboot. I can have hundreds per minute or sometimes a couple per minute. Been about 2-3 months now and no fix as of yet. I am sure these are linked to my Router rebooting.

 

[kennymc.c]

I have the same issue now too. Seems to only happen when Wi-Fi connections are added. If no Wi-Fi connections are added, it seems fine.

I can confirm that. As soon as I am no longer at home, the messages no longer occur. As soon as I am back, they are there again. The only device I have taken with me is an iPhone. A MacBook was still at home in standby but that doesn't seem to have any effect.

Unfortunately, reboots are now occurring every few hours as well, which are logged unusually accurately in the log. I have not seen this before with manual restarts.

 

[Donga120]

I can confirm that. As soon as I am no longer at home, the messages no longer occur. As soon as I am back, they are there again. The only device I have taken with me is an iPhone. A MacBook was still at home in standby but that doesn't seem to have any effect.

Unfortunately, reboots are now occurring every few hours as well, which are logged unusually accurately in the log. I have not seen this before with manual restarts.

Interesting, see my findings here, the reboots are very very annoying: http://www.snbforums.com/threads/connection-dropped-ac86u-rebooting.73949/post-716627

 

[kennymc.c]

Yesterday the error messages stopped when I went to work but when I came back they did not repapered until about 3,5 hours later. So I assume my iPhone is not the main reason. These are the log messages after the last reboot from this morning: https://pastebin.com/fem9FhxM

 

[Donga120]

Strange, I cant make heads or tail of the logs, but i would suggest to reset the router to stock ASUS firmware, unplug any ethernet devices so nothing is into the LAN ports, give it a few days and see how you get on.

 

[kennymc.c]

It is definitely my iPhone that is causing the errors. I have tested disabling Wi-Fi for several hours and the errors disappeared. In between I restarted the router but as soon as I re-enabled Wi-Fi, the messages reappeared. What I noticed though is that when I connect the iPhone to a guest WiFi without LAN access, there are no error messages either. Since the problems occurred only a few days after the iOS 15 update, I suspect the cause here as well. Unfortunately, nothing else can be found about this error. However, I noticed a warning in the Wi-Fi info on the iPhone that the network blocks encrypted DNS traffic. I haven't noticed this before, could this have something to do with it? This warning does not appear when I connect to the guest network. In addition, perhaps the note that I use a custom domain via dnsmasq. This has never caused any problems so far and is described in the wiki.

 

[Donga120]

Try reset the network settings on your iPhone and setup again?

 

[kennymc.c]

I have probably found the reason: Wi-Fi calls.

I reset the network settings of the iPhone last week. After that, no more messages or reboots occurred. I had then noticed the next day that wifi calls were disabled. But when I activated them, the messages reappeared.
I then reset the network settings again and waited until today without enabling Wi-Fi calls. In between there were no strange log messages or reboots. When I re-enabled it today, the messages immediately reappeared. I had no problems making or receiving calls with wifi calling activated. As soon as I deactivated the option again the messages did not occur even after more than two hours.
So I think it's pretty safe to say that these messages and reboots that didn't exist a few weeks ago come from Wi-Fi calls. As written before, I suspect that this has something to do that maybe changed with iOS 15. I currently have iOS 15.0.2 installed.

@RMerlin Can you make any connection to wifi calling when analyzing these messages? Is there anything I could try on the router side besides a reset? As you can read here, it seems to be caused directly by devices on the network and many have the same problems after a reset or even with a new device. So I would avoid resetting my router for now. I could of course ask Apple, but they will probably refer me back to Asus, since there are no problems on the iPhone itself.

 

[RMerlin]

@RMerlin Can you make any connection to wifi calling when analyzing these messages?

I don`t know. I have no issue with Wifi Calling with my Android phone, and my house is Apple-free.

 

[kennymc.c]

After almost 7 months in contact with Asus support, the problem has now probably been solved. I have received 8 test firmware versions from Asus in this time and the last one seems to finally cause no more crashes with Wifi Calling on the iPhone. With the test version the log level is set a bit higher, but the messages occur only a few times per day. I think this will no longer occur in a stable firmware.
Since it will probably take some time until the fix is released in one of the stable firmwares, here is the version number: 9.0.0.4_386_49252-gd396640. Maybe the support will release this version to other affected users.