Daily crash/lockup ac56u 380.63_2 (and earlier versions)

[Lesani]

Hello SNBers!

For some time now I've had problems with my ac56u and various lost realms.
Sometimes when I came back from work, my router would have locked up somehow. It still offered wifi, lights were flashing, but it was not accessible over cable and trying to actually join the wifi lead to timeouts.

It got more extreme lately. Nowadays every single day (atleast it is consistent) my router is locked up like this. I need to physically go there, switch it off and on again. Then after a while the wifi comes back and the router works as intended.

I do have a USB HDD attached which works bad on the USB3 Port (different unrelated problem), so now it is on the USB2 Port. Other than that the setup is very basic. TV, AV, BD-Player attached via cable, PCs and Phone on WiFi.

What can I do to find the underlying issue, are there any log files that would be interresting at all or such?

 

[Lesani]

Does noone have an idea? @RMerlin maybe?
I surely can'T be the only one with such issues... I have not modified my router with any scripts of my own or such...

 

[RMerlin]

Test without a USB HDD. If it still fails, do a factory default reset and reconfigure it. If after that it still crashes, then it's most likely a hardware problem.

 

[Lesani]

I must say I respectfully disagree with the hardware statement.
atleast it would be a very strong coincidence that the router locked up at precisely 03:00

Today I was online long enough to experience it firsthand. The "General" system protocols last entry before the crash was 11 minutes earlier
Then there are lots of messages from August 1st (I guess it doesn't know what date/time it is when booting) finally switching back to the correct date/time on the NTP update.

-----------------
Dec 3 02:49:23 dnsmasq-dhcp[447]: DHCPREQUEST(br0) 192.168.1.x [Phone MACADRESS]
Dec 3 02:49:23 dnsmasq-dhcp[447]: DHCPACK(br0) 192.168.1.x [Phone MACADRESS] [Phone's Name]
Aug 1 02:00:17 syslogd started: BusyBox v1.20.2
...
Aug 1 02:00:58 ntp: start NTP update
Dec 3 03:03:13 rc_service: ntp 876:notify_rc restart_upnp
...
-----------------

I did not set anything to be done by the router at 3am... it is entirely possible my provider does the daily-disconnect at that time, but that should not lead to a lockup.

I will do a factory reset again this weekend (I already did that when the issue started a long time ago)

 

[john9527]

Do you have native ipv6 active? If so, you might try turning it off. Renewing the ipv6 lease has been reported to sometimes have problems with some ISPs.

 

[Zirescu]

There is no hardware based clock on the router so it will reset back to defaults on power cycle. There is fake-hwclock which will help keep the system clock a little more honest until ntp update kicks-in. More info here. Might be a unrelated but Windows does it's Automatic updates at 3 am. Do you have the router connected to the battery side of a UPS? What are the temps like?

 

[RMerlin]

I must say I respectfully disagree with the hardware statement.

I didn't say it WAS a hardware problem. I said you have to do the mentioned troubleshooting steps first. If these steps fail, THEN you are most likely dealing with a hardware issue.

 

[Lesani]

Thanks for the responses
@Zirescu I guessed the clock part. as for the UPS, I do not have one. My temps are currently:
2.4 GHz: 52°C - 5 GHz: 56°C - CPU: 78°C
I've seen the CPU at 82°C

Concerning windows updates: Usually at 3am my PC is off. I only notice it being locked up the next evening when I come back home from work. The only thing that may or may not update during that timeframe is my TV.

@john9527 I'm note entirely sure how to check for native ipv6.

@RMerlin It read to me as if you were rooting for that. Nevermind. I will try the hard reset and fresh flash soon and give feedback if it worked.

 

[Lesani]

Little report:
So for no good reason it stopped doing that the day (or day after) I posted the system protocol lines above...

It consistently showed the behavior described for multiple weeks, and - without any intervention - stopped for nearly a week now.
Not complaining or anything, but weird it is anyway.

 

[VANT]

i think that this issue (i have also problems with latest fw) can be related to AIProtection definitin file and AI services.

 

[Jong]

I have also been chasing this issue on my 87u for some time.

Right now, following a post from one other guy on here, I think, I am wondering if it could be caused by AI Protection's alert preferences. By default it is set to send emails for vulnerability protection and infected device events (boxes ticked), but I have not configured an email address. It has been 9 days since I unticked the boxes for those two alerts and my 87u is still up.

 

[Bipin Patel]

I have a similar issue with my RT-AC66U. Every morning i loose internet connection... the router status shows as disconnected on the main page. Sometimes it would come back by itself and some times I have to manually power cycle the router. This happens every morning. I have posted the logs in another thread that I started but nobody has replied to that yet.
The problem does not happen at a specific time but also everytime in the morning.
Here are the logs:


Dec 8 06:59:33 pppd[308]: Serial link appears to be disconnected.
Dec 8 06:59:33 miniupnpd[7875]: Failed to get IP for interface ppp0
Dec 8 06:59:33 miniupnpd[7875]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Dec 8 06:59:34 WAN Connection: Fail to connect with some issues.
Dec 8 06:59:34 stop_nat_rules: apply the redirect_rules!
Dec 8 06:59:36 pppd[308]: Connection terminated.
Dec 8 06:59:46 pppd[308]: Connected to 8c:90:d3:0d:25:60 via interface eth0
Dec 8 06:59:46 pppd[308]: Connect: ppp0 <--> eth0
Dec 8 06:59:47 pppd[308]: PAP authentication succeeded
Dec 8 06:59:47 pppd[308]: peer from calling number 8C:903:0D:25:60 authorized
Dec 8 06:59:47 miniupnpd[7875]: Failed to get IP for interface ppp0
Dec 8 06:59:47 miniupnpd[7875]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Dec 8 06:59:47 miniupnpd[7875]: Failed to get IP for interface ppp0
Dec 8 06:59:47 miniupnpd[7875]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Dec 8 06:59:47 miniupnpd[7875]: Failed to get IP for interface ppp0
Dec 8 06:59:47 miniupnpd[7875]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Dec 8 06:59:47 pppd[308]: local IP address 107.179.141.165
Dec 8 06:59:47 pppd[308]: remote IP address 206.248.155.244
Dec 8 06:59:47 pppd[308]: primary DNS address 206.248.154.170
Dec 8 06:59:47 pppd[308]: secondary DNS address 206.248.154.22
Dec 8 06:59:47 rc_service: ip-up 7943:notify_rc start_firewall
Dec 8 06:59:47 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
Dec 8 06:59:47 wan: finish adding multi routes
Dec 8 06:59:47 rc_service: ip-up 7943:notify_rc stop_upnp
Dec 8 06:59:47 rc_service: ip-up 7943:notify_rc start_upnp
Dec 8 06:59:47 rc_service: waitting "stop_upnp" via ip-up ...
Dec 8 06:59:47 miniupnpd[7875]: shutting down MiniUPnPd
Dec 8 06:59:49 miniupnpd[7980]: HTTP listening on port 34865
Dec 8 06:59:49 miniupnpd[7980]: Listening for NAT-PMP/PCP traffic on port 5351
Dec 8 06:59:49 WAN Connection: WAN was restored.
Dec 8 07:01:53 pppd[308]: Serial link appears to be disconnected.
Dec 8 07:01:53 miniupnpd[7980]: Failed to get IP for interface ppp0
Dec 8 07:01:53 miniupnpd[7980]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Dec 8 07:01:54 WAN Connection: Fail to connect with some issues.
Dec 8 07:01:54 stop_nat_rules: apply the redirect_rules!
Dec 8 07:01:59 pppd[308]: Connection terminated.
Dec 8 07:01:59 pppd[308]: Modem hangup
Dec 8 07:02:44 pppd[308]: Timeout waiting for PADO packets
Dec 8 07:03:59 pppd[308]: Timeout waiting for PADO packets
Dec 8 07:05:14 pppd[308]: Timeout waiting for PADO packets
Dec 8 07:06:29 pppd[308]: Timeout waiting for PADO packets
Dec 8 07:07:44 pppd[308]: Timeout waiting for PADO packets

 

[Lesani]

03:00 precisely again - impeccable timing really - stopps responding to PING, disconnecting wifi and trying to reconnect doesnt work.
System protocol says exactly nothing - last entry is 45mins prior to the crash this time.

Again the question if there is a deeper or more verbose log that could lead to the problem? This is already after factory reset and re-flash...

 

[evilfry]

same lockup problem here with this version on a AC3200. I just updated to 380.34 beta 1. Hope it can be resolved

 

[digimon04]

happen to me too. It's been 3 consecutive days. I found it lost internet connection (wifi connection still exist) and lost wifi connection today when I wake up at the morning. There is no problem at night before I sleep.

Router is AC68U at 380.63_2

 

[Jong]

12 days uptime since I unticked all AIprotection email alerts. Has anyone else tried this?

 

[digimon04]

12 days uptime since I unticked all AIprotection email alerts. Has anyone else tried this?

Do you mean the three switches in AiPortection tab? I have never enabled those features.

 

[Jong]

If you haven't enabled aiProtection then it's probably something else for you. Traffic Analysis has also been suspected.

But for those who think aiProtection may be the cause, it's worth going to "alert preferences" and unticking all options, even if you do not have an email address configured. In another thread someone said it helped them and it seems to be working for me.

 

[evilfry]

Even with the latest 64 beta 1 same issue. Then i realised i should at least do a factory reset. Now it seem to be alot more stable.

 

[digimon04]

If you haven't enabled aiProtection then it's probably something else for you. Traffic Analysis has also been suspected.

But for those who think aiProtection may be the cause, it's worth going to "alert preferences" and unticking all options, even if you do not have an email address configured. In another thread someone said it helped them and it seems to be working for me.

It's been the fourth day. I found that no wifi signal from the router when I wake up at 9:30 a.m. There is no problem before I slept at 2:30 a.m. These shouldn't be coincidence.

Dec 15 01:30:24 dhcp client: bound 223.18.200.165 via 223.18.192.1 during 10800 seconds.
Dec 15 01:30:24 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Dec 15 05:20:01 crond[450]: crond: USER admin pid 16010 cmd /tmp/mnt/sda1/adblocking/addon/rotate-logs.add
Dec 15 05:20:04 rc_service: service 16032:notify_rc restart_dnsmasq
Dec 15 05:20:04 custom script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)
Dec 15 05:20:05 admin: AB-Solution added entries via ab_dnsmasq_postconf.sh
Dec 15 05:20:05 admin: AB-Solution linked dnsmasq.postconf to ab_dnsmasq_postconf.sh
Dec 15 05:44:22 miniupnpd[5758]: upnp_event_recv: recv(): Connection reset by peer
Dec 15 06:51:54 miniupnpd[5758]: upnp_event_recv: recv(): Connection reset by peer
Dec 15 06:54:41 miniupnpd[5758]: HTTP Connection from 192.168.1.34 closed unexpectedly
Aug 1 08:00:13 syslogd started: BusyBox v1.20.2

Above is the log. The entry of Aug 1 is probably the result of restarting router (by pushing the power button).

I will try to turn off Traffic Analysis to see if it can solve the problem. Thanks.