Interesting. This morning I signed on using PuTTY and found that the file was already gone [after I had done a couple of reboots]. AC3100 already seems to be cured: both CPU cores down to single digits, memory usage steady at 33% (168/512 MB) and no more "failed to write" log messages...
Thanks, and you're right, bad rollouts can happen to anyone at any time.
I see that the AX5700 for example gets good reviews, so I could get one of those, but wouldn't I just be buying another copy of the same bug? since presumably it will have the same memory leak issue.
OTOH, if ASUS...
After an overnight rest for the AC3100, I'm now seeing my two cores taking turns spiking to 90-100% every few seconds -- although core 2 seems to get the worst of it -- and RAM now settles around 70-72% usage and stays there.
I'll wait to see how it behaves today with more clients being added...
Hopefully you'll have better luck with your new router 👍
So the ASUS solution, from that support page, is to [1] reboot, and then [2] do a factory restore. I just tried the reboot and I'm monitoring the CPU and RAM ... I have 2 cores and 512MB in my AC3100. The cores are taking turns...
Networking novice here :) having the same problem with my home AC3100, also starting yesterday morning.
Starting first thing yesterday, the syslog has hundreds of the following errors in the log:
dnsmasq[393]: failed to allocate 124 bytes
dnsmasq-dhcp[393]: failed to write...
Networking novice here :-) having the same problem with my home AC3100, also starting yesterday morning.
As of first thing yesterday, the syslog has hundreds of the following errors in the log:
May 17 23:30:18 dnsmasq[393]: failed to allocate 124 bytes
May 17 23:30:18 dnsmasq-dhcp[393]...