SNBForums
I've got an Asus RT-AC88U that intermittently has an issue where it essentially locks up and has to be power cycled.
While locked up:
Here's a rather typical snippet from the router's logfile:
There are numerous entries that are repeated at rather patternistic intervals. The thing I've noticed that isn't quite as "rhythmic" are the entries making mention of miniupnpd. Sometimes there's a single entry as shown above, but there are a few places in the log that have 10 or so entries back-to-back.
The other thing worth mention is I suspect this lockup is somehow related to a specific laptop I have that stays powered off most of the time. I say this because the router can go MONTHS without having an issue at all. However last week, the router did this lockup twice, and that laptop was powered and online both times it happened. And I suspect that the previous events of this happening were also when this laptop was powered. Add to this, the IP address indicated in that miniupnpd entry is that laptop's IP when powered. So I suspect this being related to UPnP. However I have to admit ignorance to UPnP. I'm aware that it's a thing, but I don't really know what services or features it enables that I would notice or miss if I disabled UPnP support in the router. I do see there are switch controls to disable it on the WAN page. But before I tried that, I thought I might should ask others more familiar with these log messages, this issue, and/or those settings before I proceeded.
Other things of note, I've confirmed the issue is not my cable modem. Each time this has happened, a restart of the router fixes the issue until it happens again. And while the router is in its locked-up state, the cable modem shows online and even responds to remote-commands to restart via the Xfinity app.
I also have an RT-AC68U as an AIMesh Node however I haven't come across anything so far that makes me suspicious of it yet.
Anybody have an idea as to what this issue might be?
And more importantly what setting(s) I can change to possible make it go away?
While locked up:
- Router displays a Red Led
- Ethernet connected devices do not have Internet access
- Wifi SSIDs (main and guest) are being broadcast but no device can actually connect
Here's a rather typical snippet from the router's logfile:
Code:
...
May 5 01:05:24 kernel: xhci_hcd 0000:00:0c.0: Failed to enable MSI-X
May 5 01:05:24 kernel: xhci_hcd 0000:00:0c.0: failed to allocate MSI entry
Jan 24 02:02:55 crond[524]: time disparity of 3009717 minutes detected
Jan 26 02:00:21 Mastiff: Got SIGTERM
Jan 26 02:00:21 Mastiff: Got SIGTERM
Jan 26 02:00:21 Mastiff: Got SIGTERM
Jan 26 02:00:22 Mastiff: Select error
May 5 01:05:12 kernel: pflash: found no supported devices
May 5 01:05:12 kernel: bcmsflash: found no supported devices
May 5 01:05:19 acsd: selected channel spec: 0x1009 (9)
May 5 01:05:19 acsd: Adjusted channel spec: 0x1009 (9)
May 5 01:05:19 acsd: selected channel spec: 0x1009 (9)
May 5 01:05:19 acsd: acs_set_chspec: 0x1009 (9) for reason APCS_INIT
May 5 01:05:20 acsd: selected channel spec: 0xe09b (149/80)
May 5 01:05:20 acsd: Adjusted channel spec: 0xe09b (149/80)
May 5 01:05:20 acsd: selected channel spec: 0xe09b (149/80)
May 5 01:05:20 acsd: acs_set_chspec: 0xe09b (149/80) for reason APCS_INIT
May 5 01:05:20 Mastiff: init
May 5 01:05:25 kernel: xhci_hcd 0000:00:0c.0: Failed to enable MSI-X
May 5 01:05:25 kernel: xhci_hcd 0000:00:0c.0: failed to allocate MSI entry
Jan 26 02:03:13 crond[526]: time disparity of 3012597 minutes detected
Jan 26 17:53:54 miniupnpd[1031]: upnpevents_processfds: 0x2f378, remove subscriber uuid:e17e7ea4-bc72-4606-b8a1-d288901315df after an ERROR cb: http://192.168.1.130:2869/upnp/eventing/bndasswcnc
Jan 27 02:00:06 Mastiff: Got SIGTERM
Jan 27 02:00:06 Mastiff: Got SIGTERM
Jan 27 02:00:06 syslog: Got SIGTERM
May 5 01:05:11 kernel: pflash: found no supported devices
May 5 01:05:11 kernel: bcmsflash: found no supported devices
May 5 01:05:18 acsd: selected channel spec: 0x100b (11)
May 5 01:05:18 acsd: Adjusted channel spec: 0x100b (11)
May 5 01:05:18 acsd: selected channel spec: 0x100b (11)
May 5 01:05:18 acsd: acs_set_chspec: 0x100b (11) for reason APCS_INIT
May 5 01:05:19 acsd: selected channel spec: 0xe09b (149/80)
May 5 01:05:19 acsd: Adjusted channel spec: 0xe09b (149/80)
May 5 01:05:19 acsd: selected channel spec: 0xe09b (149/80)
May 5 01:05:19 acsd: acs_set_chspec: 0xe09b (149/80) for reason APCS_INIT
May 5 01:05:20 Mastiff: init
May 5 01:05:25 kernel: xhci_hcd 0000:00:0c.0: Failed to enable MSI-X
May 5 01:05:25 kernel: xhci_hcd 0000:00:0c.0: failed to allocate MSI entry
Jan 27 02:03:02 crond[524]: time disparity of 3014037 minutes detected
...There are numerous entries that are repeated at rather patternistic intervals. The thing I've noticed that isn't quite as "rhythmic" are the entries making mention of miniupnpd. Sometimes there's a single entry as shown above, but there are a few places in the log that have 10 or so entries back-to-back.
The other thing worth mention is I suspect this lockup is somehow related to a specific laptop I have that stays powered off most of the time. I say this because the router can go MONTHS without having an issue at all. However last week, the router did this lockup twice, and that laptop was powered and online both times it happened. And I suspect that the previous events of this happening were also when this laptop was powered. Add to this, the IP address indicated in that miniupnpd entry is that laptop's IP when powered. So I suspect this being related to UPnP. However I have to admit ignorance to UPnP. I'm aware that it's a thing, but I don't really know what services or features it enables that I would notice or miss if I disabled UPnP support in the router. I do see there are switch controls to disable it on the WAN page. But before I tried that, I thought I might should ask others more familiar with these log messages, this issue, and/or those settings before I proceeded.
Other things of note, I've confirmed the issue is not my cable modem. Each time this has happened, a restart of the router fixes the issue until it happens again. And while the router is in its locked-up state, the cable modem shows online and even responds to remote-commands to restart via the Xfinity app.
I also have an RT-AC68U as an AIMesh Node however I haven't come across anything so far that makes me suspicious of it yet.
Anybody have an idea as to what this issue might be?
And more importantly what setting(s) I can change to possible make it go away?