Home Network Community > Deco > M9+ V2 log flooded with errors every 10 seconds
< Deco

M9+ V2 log flooded with errors every 10 seconds

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

M9+ V2 log flooded with errors every 10 seconds

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
M9+ V2 log flooded with errors every 10 seconds
M9+ V2 log flooded with errors every 10 seconds
2020-09-21 18:16:16
Model: Deco M9 Plus  
Hardware Version: V2
Firmware Version: 1.4.2 Build 20200725 Rel. 65637

Hi,

 

Why is My Deco M9+ being flooded with error messages every 10 seconds? What are these messages saying? What can I do to fix this? Is this a firmware bug that TP-link should address? Please advice. This goes on 24/7 and fills the log completely.

 

Mon Sep 21 20:04:21 2020 user.err csrMeshGw[5452]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2
Mon Sep 21 20:04:21 2020 user.err csrMeshGw[5452]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30
Mon Sep 21 20:04:21 2020 user.err csrMeshGw[5452]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30
Mon Sep 21 20:04:21 2020 user.err csrMeshGw[5452]: 
CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!
Mon Sep 21 20:04:23 2020 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block
Mon Sep 21 20:04:24 2020 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block
Mon Sep 21 20:04:25 2020 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block
Mon Sep 21 20:04:27 2020 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.252 is Local Network Control Block
Mon Sep 21 20:04:28 2020 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block
Mon Sep 21 20:04:28 2020 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.252 is Local Network Control Block
Mon Sep 21 20:04:29 2020 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block
Mon Sep 21 20:04:31 2020 user.err csrMeshGw[5452]: 
CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff
Mon Sep 21 20:04:31 2020 user.err csrMeshGw[5452]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2
Mon Sep 21 20:04:31 2020 user.err csrMeshGw[5452]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30
Mon Sep 21 20:04:31 2020 user.err csrMeshGw[5452]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30
Mon Sep 21 20:04:31 2020 user.err csrMeshGw[5452]: 
CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!
Mon Sep 21 20:04:41 2020 user.err csrMeshGw[5452]: 
CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff
Mon Sep 21 20:04:41 2020 user.err csrMeshGw[5452]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2
Mon Sep 21 20:04:41 2020 user.err csrMeshGw[5452]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30
Mon Sep 21 20:04:41 2020 user.err csrMeshGw[5452]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30
Mon Sep 21 20:04:41 2020 user.err csrMeshGw[5452]: 
CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!
Mon Sep 21 20:04:51 2020 user.err csrMeshGw[5452]: 
CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff
Mon Sep 21 20:04:51 2020 user.err csrMeshGw[5452]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2
Mon Sep 21 20:04:51 2020 user.err csrMeshGw[5452]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30
Mon Sep 21 20:04:51 2020 user.err csrMeshGw[5452]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30
Mon Sep 21 20:04:51 2020 user.err csrMeshGw[5452]: 
CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!
Mon Sep 21 20:05:01 2020 user.err csrMeshGw[5452]: 
CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff
Mon Sep 21 20:05:01 2020 user.err csrMeshGw[5452]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2
Mon Sep 21 20:05:01 2020 user.err csrMeshGw[5452]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30
Mon Sep 21 20:05:01 2020 user.err csrMeshGw[5452]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30
Mon Sep 21 20:05:01 2020 user.err csrMeshGw[5452]: 
CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!
Mon Sep 21 20:05:07 2020 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block
Mon Sep 21 20:05:10 2020 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block
Mon Sep 21 20:05:11 2020 user.err csrMeshGw[5452]: 
CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff
Mon Sep 21 20:05:11 2020 user.err csrMeshGw[5452]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2
Mon Sep 21 20:05:11 2020 user.err csrMeshGw[5452]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30
Mon Sep 21 20:05:11 2020 user.err csrMeshGw[5452]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30
Mon Sep 21 20:05:11 2020 user.err csrMeshGw[5452]: 
CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!
 

  0      
 
  0      
 
#1
Options
9 Reply
Re:M9+ V2 log flooded with errors every 10 seconds
2020-11-01 01:23:32 - last edited 2020-11-01 01:25:13

I also am getting this same behavior, about every few seconds the same/similar error messages as you have posted.

 

********

Sat Oct 31 21:21:25 2020 user.err csrMeshGw[5629]: 

CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff

Sat Oct 31 21:21:25 2020 user.err csrMeshGw[5629]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Sat Oct 31 21:21:25 2020 user.err csrMeshGw[5629]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Sat Oct 31 21:21:25 2020 user.err csrMeshGw[5629]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Sat Oct 31 21:21:25 2020 user.err csrMeshGw[5629]: 

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

**********

  1  
  1  
#2
Options
Re:M9+ V2 log flooded with errors every 10 seconds
2020-11-02 11:28:19

@cacb That message means there is a device with weak network signal on the network and the router is struggling to fulfill the device's requests, as the device is not correctly responding. 

  0  
  0  
#3
Options
Re:M9+ V2 log flooded with errors every 10 seconds
2020-11-02 11:42:58

@richpriest Interesting, I will try to shut down some of my more suspect devices then, and see if it makes any difference. Possibly an old laptop could be the problem. Thanks for the tip, we shall see if that makes any difference

  0  
  0  
#4
Options
Re:M9+ V2 log flooded with errors every 10 seconds
2020-11-02 16:15:05
I do not have devices with weak signal on my network, as far as I can tell, but I am getting plenty of these in logs. Perhaps, there are multiple reasons for those.
  0  
  0  
#5
Options
Re:M9+ V2 log flooded with errors every 10 seconds
2020-11-02 18:21:41 - last edited 2020-11-02 18:26:21

@Alexandre. I switched off the laptop I was not sure about, and cleared the logs. But they are still filled with lots of messages like below. Sometimes there are IP-addresses like "Sending ACK to 10.0.0.105" as in the example below, but this seems to happen for several (all?) IP addresses in my network, not just one. 10.0.0.105 is a wired Win10 desktop computer with no connection issues (CAT6 cable), for example. The same pattern repeats itself for several other IPs

 

Mon Nov  2 16:43:38 2020 user.err csrMeshGw[5413]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2
Mon Nov  2 16:43:38 2020 user.err csrMeshGw[5413]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30
Mon Nov  2 16:43:38 2020 user.err csrMeshGw[5413]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30
Mon Nov  2 16:43:38 2020 user.err csrMeshGw[5413]: 
CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!
Mon Nov  2 16:43:39 2020 daemon.err udhcpd[9170]: Sending ACK to 10.0.0.105
Mon Nov  2 16:43:39 2020 daemon.err udhcpd[9170]: clear ip 6900000a
Mon Nov  2 16:43:48 2020 user.err csrMeshGw[5413]: 
CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff
Mon Nov  2 16:43:48 2020 user.err csrMeshGw[5413]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2
Mon Nov  2 16:43:48 2020 user.err csrMeshGw[5413]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30
Mon Nov  2 16:43:48 2020 user.err csrMeshGw[5413]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30
Mon Nov  2 16:43:48 2020 user.err csrMeshGw[5413]: 
CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!
Mon Nov  2 16:43:58 2020 user.err csrMeshGw[5413]: 
CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff
Mon Nov  2 16:43:58 2020 user.err csrMeshGw[5413]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2
Mon Nov  2 16:43:58 2020 user.err csrMeshGw[5413]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30
Mon Nov  2 16:43:58 2020 user.err csrMeshGw[5413]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30
Mon Nov  2 16:43:58 2020 user.err csrMeshGw[5413]: 
CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!
Mon Nov  2 16:44:08 2020 user.err csrMeshGw[5413]: 
CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff
Mon Nov  2 16:44:08 2020 user.err csrMeshGw[5413]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2
Mon Nov  2 16:44:08 2020 user.err csrMeshGw[5413]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30
Mon Nov  2 16:44:08 2020 user.err csrMeshGw[5413]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30
Mon Nov  2 16:44:08 2020 user.err csrMeshGw[5413]: 
CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

 

P.S. After starting this thread, the firmware was upgraded to 1.4.3 Build 20200921 Rel. 42500, so this flooding of error messages happens also with this latest firmware.

  0  
  0  
#6
Options
Re:M9+ V2 log flooded with errors every 10 seconds
2020-11-02 20:34:33

@cacb 

 

Mon Nov  2 16:43:39 2020 daemon.err udhcpd[9170]: Sending ACK to 10.0.0.105
Mon Nov  2 16:43:39 2020 daemon.err udhcpd[9170]: clear ip 6900000a

 

I can guess what this is. You must be running your Deco in router mode. udhcpd is mini DHCP server daemon. It will reply to computer request for IP address with IP address in ACK message. 

Which means, your Win10 desktop must have asked to renew IP address and got a response from your Deco. 

 

These udhcpd log lines can be ignored. They are part of standard network activities.

 

I checked my logs for Deco running in AP mode and can't find ACK messages. Must be because my Hitron Coda cable modem/router is running DHCP server for my network, not Deco.

  0  
  0  
#7
Options
Re:M9+ V2 log flooded with errors every 10 seconds
2020-11-02 21:01:40

@Alexandre. You are correct, my Deco is running in router mode. My fiber "home central" is put in bridge mode and Deco M9+ is in router mode.

 

But if thise messages do not indicate an error I wonder why these messages are listed under Log Type "ERROR" in the system log?

 

Even so this does not really explain the somewhat hysterical looking (4 exclamation marks) No message of desired type!!!! that is repeated over and over, filling the log:

 

Mon Nov 2 18:28:59 2020 user.err csrMeshGw[5413]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2

Mon Nov 2 18:28:59 2020 user.err csrMeshGw[5413]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30

Mon Nov 2 18:28:59 2020 user.err csrMeshGw[5413]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30

Mon Nov 2 18:28:59 2020 user.err csrMeshGw[5413]:

CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!

 

It is not really possible to know (unless you know the code) if there are any serious problems or not from reading the error log. In any case it does not seem right that the ERROR log is filled almost instantly unless there is some error that should be fixed?

  0  
  0  
#8
Options
Re:M9+ V2 log flooded with errors every 10 seconds
2022-01-21 11:33:33

i'm having the same issue and it is dropping my connection for a few seconds

  0  
  0  
#9
Options
Re:M9+ V2 log flooded with errors every 10 seconds
2022-03-08 00:16:36

  @zsam288 same here...

  0  
  0  
#10
Options

Information

Helpful: 0

Views: 2689

Replies: 9

Related Articles
 Deco M9 Plus Error log flooded
327 0
 DECO M9 issue --> connection interrupts every 5-10 seconds
901 1
 Deco M9 plus periodical ping spikes every 10 seconds
1114 0
 repeating errors in log
894 0
 Log filling up with errors
659 0
3000+ Ping spike Pattern every 8-10 seconds
14137 1
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.