Asus RT-AC66 running on 100% cpu

[MoogLe]

Hey guys,

We've been having some power outages recently and it has caused my router to really start acting up.

This is the second time that the router has been running at 100% cpu utilization and I noticed that it pretty much kills the wifi reliablility.

Last time I had to do a firmware update and factory reset to get it back to normal CPU levels.

I'm wondering, is there an easier method to kill whatever process is taking up all the cpu cycles?

I'm running Merlin 380.64_2 and no usb or hard drives attached to the router.

 

[MoogLe]

Just tried a factory reset and it didnt seem to even help this time. Was still running at 100% with factory settings....

Hope you guys can give me some hope that this router isn't fried

 

[swetoast]

do you have anything from the syslog when it acts up ? or a ps -w from shell even ? would narrow it down whats causing the cpu usage

 

[MoogLe]

I'm affraid I am not so advanced yet.

I did look at the syslog but can't really decipher anything in there.

Here's what my syslog has been showing on jan 11th

Jan 11 10:27:43 miniupnpd[447]: remove port mapping 59298 TCP because it has expired
Jan 11 10:27:43 miniupnpd[447]: remove port mapping 59298 UDP because it has expired
Jan 11 10:27:43 rc_service: ntp 448:notify_rc restart_upnp
Jan 11 10:27:43 miniupnpd[447]: shutting down MiniUPnPd
Jan 11 10:27:44 rc_service: ntp 448:notify_rc restart_diskmon
Jan 11 10:27:44 disk_monitor: Finish
Jan 11 10:27:44 miniupnpd[460]: HTTP listening on port 35115
Jan 11 10:27:44 miniupnpd[460]: Listening for NAT-PMP/PCP traffic on port 5351
Jan 11 10:27:45 disk monitor: be idle
Jan 11 10:27:51 dnsmasq-dhcp[241]: DHCPREQUEST(br0) 172.16.0.144 6c:ad:f8:17:c9:4c
Jan 11 10:27:51 dnsmasq-dhcp[241]: DHCPACK(br0) 172.16.0.144 6c:ad:f8:17:c9:4c Chromecast
Jan 11 10:28:11 dnsmasq-dhcp[241]: DHCPREQUEST(br0) 172.16.0.168 38:63:bb:d4:d8:e8
Jan 11 10:28:11 dnsmasq-dhcp[241]: DHCPACK(br0) 172.16.0.168 38:63:bb:d4:d8:e8 HPD4D8E7
Jan 11 10:28:35 crond[244]: time disparity of 762627 minutes detected
Jan 11 10:29:18 dnsmasq-dhcp[241]: DHCPREQUEST(br0) 172.16.0.168 38:63:bb:d4:d8:e8
Jan 11 10:29:18 dnsmasq-dhcp[241]: DHCPACK(br0) 172.16.0.168 38:63:bb:d4:d8:e8 HPD4D8E7
Jan 11 10:30:27 dnsmasq-dhcp[241]: DHCPDISCOVER(br0) 38:63:bb:d4:d8:e8
Jan 11 10:30:27 dnsmasq-dhcp[241]: DHCPOFFER(br0) 172.16.0.168 38:63:bb:d4:d8:e8
Jan 11 10:30:32 dnsmasq-dhcp[241]: DHCPDISCOVER(br0) 38:63:bb:d4:d8:e8
Jan 11 10:30:32 dnsmasq-dhcp[241]: DHCPOFFER(br0) 172.16.0.168 38:63:bb:d4:d8:e8
Jan 11 10:30:41 dnsmasq-dhcp[241]: DHCPDISCOVER(br0) 38:63:bb:d4:d8:e8
Jan 11 10:30:41 dnsmasq-dhcp[241]: DHCPOFFER(br0) 172.16.0.168 38:63:bb:d4:d8:e8
Jan 11 10:30:59 dnsmasq-dhcp[241]: DHCPDISCOVER(br0) 38:63:bb:d4:d8:e8
Jan 11 10:30:59 dnsmasq-dhcp[241]: DHCPOFFER(br0) 172.16.0.168 38:63:bb:d4:d8:e8
Jan 11 10:31:32 dnsmasq-dhcp[241]: DHCPDISCOVER(br0) 38:63:bb:d4:d8:e8
Jan 11 10:31:32 dnsmasq-dhcp[241]: DHCPOFFER(br0) 172.16.0.168 38:63:bb:d4:d8:e8
Jan 11 10:31:42 dnsmasq-dhcp[241]: DHCPREQUEST(br0) 172.16.0.179 98:fe:94:6f:53:89
Jan 11 10:31:42 dnsmasq-dhcp[241]: DHCPACK(br0) 172.16.0.179 98:fe:94:6f:53:89 Linseis-iPad-4
Jan 11 10:32:03 rc_service: httpd 242:notify_rc restart_wlcscan
Jan 11 10:32:38 dnsmasq-dhcp[241]: DHCPDISCOVER(br0) 38:63:bb:d4:d8:e8
Jan 11 10:32:38 dnsmasq-dhcp[241]: DHCPOFFER(br0) 172.16.0.168 38:63:bb:d4:d8:e8
Jan 11 10:33:02 rc_service: httpd 242:notify_rc set_wltxpower;restart_wireless
Jan 11 10:33:13 kernel: br0: port 2(eth1) entering disabled state
Jan 11 10:33:13 kernel: device eth1 left promiscuous mode
Jan 11 10:33:13 kernel: br0: port 2(eth1) entering disabled state
Jan 11 10:33:13 kernel: br0: port 3(eth2) entering disabled state
Jan 11 10:33:13 kernel: device eth2 left promiscuous mode
Jan 11 10:33:13 kernel: br0: port 3(eth2) entering disabled state
Jan 11 10:33:20 kernel: wl_module_init: passivemode set to 0x0
Jan 11 10:33:20 kernel: eth1: Broadcom BCM4331 802.11 Wireless Controller 6.30.163.2002 (r382208)
Jan 11 10:33:20 kernel: eth2: Broadcom BCM4360 802.11 Wireless Controller 6.30.163.2002 (r382208)
Jan 11 10:33:21 kernel: wlc_phy_cal_init_acphy: NOT Implemented
Jan 11 10:33:21 kernel: device eth2 entered promiscuous mode
Jan 11 10:33:21 kernel: br0: port 2(eth2) entering listening state
Jan 11 10:33:21 kernel: br0: port 2(eth2) entering learning state
Jan 11 10:33:21 kernel: br0: topology change detected, sending tcn bpdu
Jan 11 10:33:21 kernel: br0: port 2(eth2) entering forwarding state
Jan 11 10:33:26 dnsmasq-dhcp[241]: DHCPREQUEST(br0) 172.16.0.192 18:ee:69:bc:ca:a1
Jan 11 10:33:26 dnsmasq-dhcp[241]: DHCPACK(br0) 172.16.0.192 18:ee:69:bc:ca:a1 Melinas-iPad
Jan 11 10:34:11 rc_service: httpd 242:notify_rc restart_wireless
Jan 11 10:34:15 kernel: br0: port 2(eth2) entering disabled state
Jan 11 10:34:15 kernel: device eth2 left promiscuous mode
Jan 11 10:34:15 kernel: br0: port 2(eth2) entering disabled state
Jan 11 10:34:21 kernel: wl_module_init: passivemode set to 0x0
Jan 11 10:34:21 kernel: eth1: Broadcom BCM4331 802.11 Wireless Controller 6.30.163.2002 (r382208)
Jan 11 10:34:22 kernel: eth2: Broadcom BCM4360 802.11 Wireless Controller 6.30.163.2002 (r382208)
Jan 11 10:34:23 kernel: wlc_phy_cal_init_acphy: NOT Implemented
Jan 11 10:34:23 kernel: device eth2 entered promiscuous mode
Jan 11 10:34:23 kernel: br0: port 2(eth2) entering listening state
Jan 11 10:34:23 kernel: br0: port 2(eth2) entering learning state
Jan 11 10:34:23 kernel: br0: topology change detected, sending tcn bpdu
Jan 11 10:34:23 kernel: br0: port 2(eth2) entering forwarding state
Jan 11 10:34:32 dnsmasq-dhcp[241]: DHCPDISCOVER(br0) 54:e4:3a:c1:7e:d0
Jan 11 10:34:32 dnsmasq-dhcp[241]: DHCPOFFER(br0) 172.16.0.225 54:e4:3a:c1:7e:d0
Jan 11 10:34:32 dnsmasq-dhcp[241]: DHCPDISCOVER(br0) 54:e4:3a:c1:7e:d0
Jan 11 10:34:32 dnsmasq-dhcp[241]: DHCPOFFER(br0) 172.16.0.225 54:e4:3a:c1:7e:d0
Jan 11 10:34:36 dnsmasq-dhcp[241]: DHCPDISCOVER(br0) 20:ab:37:73:fe:b6
Jan 11 10:34:36 dnsmasq-dhcp[241]: DHCPOFFER(br0) 172.16.0.229 20:ab:37:73:fe:b6
Jan 11 10:34:36 dnsmasq-dhcp[241]: DHCPREQUEST(br0) 172.16.0.225 54:e4:3a:c1:7e:d0
Jan 11 10:34:36 dnsmasq-dhcp[241]: DHCPACK(br0) 172.16.0.225 54:e4:3a:c1:7e:d0 ChristoersiPad2
Jan 11 10:34:36 dnsmasq-dhcp[241]: DHCPREQUEST(br0) 172.16.0.225 54:e4:3a:c1:7e:d0
Jan 11 10:34:36 dnsmasq-dhcp[241]: DHCPACK(br0) 172.16.0.225 54:e4:3a:c1:7e:d0 ChristoersiPad2
Jan 11 10:34:36 dnsmasq-dhcp[241]: DHCPDISCOVER(br0) 20:ab:37:73:fe:b6
Jan 11 10:34:36 dnsmasq-dhcp[241]: DHCPOFFER(br0) 172.16.0.229 20:ab:37:73:fe:b6
Jan 11 10:34:37 dnsmasq-dhcp[241]: DHCPREQUEST(br0) 172.16.0.229 20:ab:37:73:fe:b6
Jan 11 10:34:37 dnsmasq-dhcp[241]: DHCPACK(br0) 172.16.0.229 20:ab:37:73:fe:b6 Chris-iPhone-7
Jan 11 10:35:10 rc_service: httpd 242:notify_rc restart_wireless
Jan 11 10:35:14 kernel: br0: port 2(eth2) entering disabled state
Jan 11 10:35:14 kernel: device eth2 left promiscuous mode
Jan 11 10:35:14 kernel: br0: port 2(eth2) entering disabled state
Jan 11 10:35:20 kernel: wl_module_init: passivemode set to 0x0
Jan 11 10:35:20 kernel: eth1: Broadcom BCM4331 802.11 Wireless Controller 6.30.163.2002 (r382208)
Jan 11 10:35:20 kernel: eth2: Broadcom BCM4360 802.11 Wireless Controller 6.30.163.2002 (r382208)
Jan 11 10:35:21 kernel: wlc_phy_cal_init_acphy: NOT Implemented
Jan 11 10:35:21 kernel: device eth2 entered promiscuous mode
Jan 11 10:35:21 kernel: br0: port 2(eth2) entering listening state
Jan 11 10:35:21 kernel: br0: port 2(eth2) entering learning state
Jan 11 10:35:21 kernel: br0: topology change detected, sending tcn bpdu
Jan 11 10:35:21 kernel: br0: port 2(eth2) entering forwarding state
Jan 11 10:35:26 kernel: br0: neighbor 8000.20:cf:30:b7:2f:30 lost on port 1(vlan1)
Jan 11 10:35:26 kernel: br0: topology change detected, propagating
Jan 11 10:35:28 dnsmasq-dhcp[241]: DHCPREQUEST(br0) 172.16.0.192 18:ee:69:bc:ca:a1
Jan 11 10:35:28 dnsmasq-dhcp[241]: DHCPACK(br0) 172.16.0.192 18:ee:69:bc:ca:a1 Melinas-iPad
Jan 11 10:35:39 kernel: device br0 entered promiscuous mode
Jan 11 10:35:44 dnsmasq-dhcp[241]: DHCPREQUEST(br0) 172.16.0.4 d0:e7:82:d9:cf:78
Jan 11 10:35:44 dnsmasq-dhcp[241]: DHCPACK(br0) 172.16.0.4 d0:e7:82:d9:cf:78 Chromecast
Jan 11 10:36:48 kernel: device br0 left promiscuous mode
Jan 11 10:37:05 dnsmasq-dhcp[241]: DHCPREQUEST(br0) 172.16.0.4 d0:e7:82:d9:cf:78
Jan 11 10:37:05 dnsmasq-dhcp[241]: DHCPACK(br0) 172.16.0.4 d0:e7:82:d9:cf:78 Chromecast

 

[MoogLe]

I turned off my 2.4 ghz antenna and got the cpu down to 75%

But another wierd issue im having is that when my devices try to connect to my 5ghz network its saying that im using the wrong password, eventhough it's right. If I change the SSID to something else, it will work just fine, when I go back to my default SSID, same problem. I also had this problem yesterday which went away after resetting and rebooting a couple of times but I could not figure out the root issue....

 

[Nullity]

I'd definitely try running "ps" and/or "top" via SSH/telnet. It'll show you exactly what's causing it.

 

[MoogLe]

any links to a guide on how to do that?

 

[MoogLe]

ok so nevermind the guide

Here is what ps gave me

PID USER VSZ STAT COMMAND
1 moogle 4988 S /sbin/init
2 moogle 0 SW< [kthreadd]
3 moogle 0 SWN [ksoftirqd/0]
4 moogle 0 SW< [events/0]
5 moogle 0 SW< [khelper]
20 moogle 0 SW< [kblockd/0]
51 moogle 0 SW [pdflush]
52 moogle 0 SW [pdflush]
53 moogle 0 SW< [kswapd0]
54 moogle 0 SW< [aio/0]
98 moogle 0 SW< [mtdblockd]
121 moogle 0 SW< [kmmcd]
125 moogle 648 S hotplug2 --persistent --no-coldplug
156 moogle 4972 S console
157 moogle 1436 S /bin/sh
166 moogle 0 SWN [jffs2_gcd_mtd5]
224 moogle 4980 S /sbin/wanduck
227 moogle 1216 S /bin/eapd
229 moogle 4980 S wpsaide
232 moogle 1608 S nas
234 moogle 1256 S /usr/sbin/acsd
237 nobody 1224 S dnsmasq --log-async
240 moogle 1436 S crond
241 moogle 1180 S /usr/sbin/infosvr br0
244 moogle 4980 S watchdog
245 moogle 2296 S rstats
247 moogle 4980 S sw_devled
249 moogle 1192 S cstats
250 moogle 4980 S ots
259 moogle 1224 S lld2d.rtac66r br0
262 moogle 1052 S mDNSNetMonitor
263 moogle 1232 S networkmap --bootwait
284 moogle 5888 S nmbd -D -s /etc/smb.conf
285 moogle 5828 S nmbd -D -s /etc/smb.conf
287 moogle 6048 S /usr/sbin/smbd -D -s /etc/smb.conf
316 moogle 0 SW< [khubd]
391 moogle 4980 S usbled
392 moogle 2284 S u2ec
398 moogle 1280 S lpd br0
399 moogle 2284 S u2ec
400 moogle 2284 S u2ec
442 moogle 4980 S ntp
444 moogle 1448 S /sbin/udhcpc -i eth0 -p /var/run/udhcpc0.pid -s /tmp
452 moogle 4980 S disk_monitor
606 moogle 1424 S /sbin/syslogd -m 0 -S -O /tmp/syslog.log -s 256 -l 7
608 moogle 1428 S /sbin/klogd -c 1
621 moogle 1116 S dropbear -p 172.16.0.1:22
640 moogle 4752 S httpd -i br0
643 moogle 884 S miniupnpd -f /etc/upnp/config
652 moogle 1184 S dropbear -p 172.16.0.1:22
654 moogle 1436 S -sh
664 moogle 0 Z [sh]
677 moogle 1428 R ps

And Top was showing me a cpu utilization of below 10% most of the time...... with httpd -i br0 usually using the most cpu cycles at around 6-8%

so..... what now?

 

[swetoast]

is your dropbear configured for wan usage ?

 

[MoogLe]

is your dropbear configured for wan usage ?

I have no idea what dropbear is

 

[swetoast]

ssh dropbear

Administration > System > SSH Daemon

that should always be off or lan only

just looking at the log it seems like that one is facing wan

 

[MoogLe]

Oh yea

I actually just turned that on cause i thought it was needed to telnet into the router

It is currently set to LAN only

So yea that is definately not the root issue

 

[MoogLe]

So i dont get why top is showing such a low cpu utilization and the web interface is showing a very high %.

Or am i reading the top session % wrong?

 

[swetoast]

nope your not reading it wrong, the trick is to catch it when it starts acting up.

 

[MoogLe]

Its still showing 75-85% utilization in the web interface. While the ssh session is showing below 10%

I had them both open at the same time.

 

[swetoast]

from my experience the webui lives its own life i trust top and ps rather then the webui

 

[MoogLe]

from my experience the webui lives its own life i trust top and ps rather then the webui

I can understand that

BUT

The high utilization on the web interface seems to coincide with the wifi issues.

Just before the power went out, I just so happen to have opened an app on my phone "Wifi sweetspot" that checks your wifi's performance. I was getting around 300mb/s average. After the outage im hovering around 30 if I can even connect.

The wired network works fine, no issues at all, it's just the wifi that's all jacked up. I also have an RTN66U working as an access point which also seems to having similar issues.

Yesterday when I had these same issues, everything seemed to get back to normal once I got the cpu utilization down to around 30%.

 

[MoogLe]

So yea,

Utilization is back down and everything is back to normal.

I'm stumped on what is causing this....

 

[MoogLe]

No ideas?

This keeps happening everytime the router loses power. Takes a while before it gets back to normal.

 

[MoogLe]

I figured it out.

The culprit turned out to be my Nvidia Shield TV.

I think what's happening is since the shield is running Plex media server and it gets the media from my NAS, every time I lose power, the shield boots up much faster than my NAS, and it keeps trying to connect to the NAS unsuccessfully. For some reason I have to reboot it to successfully reconnect to the NAS.

I don't get why this is making my router go absolutely crazy though, how much traffic could this possibly be causing?

 

[Reinvented]

Could be using a lot if your PMS is exposed to the internet for shared streaming, etc.