Same problem here... nvram is filled to the top and I must say that there are sume funny enrties (besides the fact that the nvram summary does not sup up to what the router interface says).
ASUS RT-AC68U
Main problem that had me writing here is the yellow exclamation sign that was informing me regarding nvram avilability (appeared after upgrade to 384.14):
Your router is running low on free NVRAM, which might affect its stability.<br>Review long parameter lists (like DHCP reservations), or consider doing a factory default reset and reconfiguring.
Review System Information now
yes, I`ll factory reset it in a minute, first I`ll backup everything (just in case, maybe I need some info later on -- although I can`t read read config files)
Logs with respect to this problem were also present:
Dec 31 16:12:31 kernel: nvram: consolidating space!
Status in web interface is: NVRAM usage 65185 / 65536 bytes
What I get from nvram summary command is:
size: 65184 bytes (352 left)
4813 MULTIFILTER_TMP_T *** what the goose?!?!?
1089 sshd_hostkey
810 nc_setting_conf
624 sshd_dsskey
516 rc_support
515 share_link
411 sshd_authkeys
338 sshd_ecdsakey
205 wl1_chansps
194 custom_clientlist
The respective field looks quite funny. Any hint on it`s usage? I`ll flush nvram in a second, see what I have after facory reset. Screenshot with its content attached
Besides that I also have the "dnsmasq.leases: No space left on device"... Ram is ok (now), half filled. Router reboot cron job configured every night, it`s much more stable this way.
I only updated on the 31st to 384.14 since the lets encrypt automated certificate renewal no longer worked (issue with new json fields support in client api), plus I always hope for stability improvements, as everyone does
What was also annoying is that the internet would fail with days (unless I manually un/re-plug the brick).. initially the reboot job was every 2-3 days (now every day), yet I had some issues with my home alarm system, it was unreachable for 2 days in a row and I was really away (it will however scream, should it detect motion)... since I have previous experiences with thieves, I was quite worried (neighbours were also away and power cycling my apartment would not fix it, router and amenities can live 10+ hours on ups...). I`m currently looking into solutions with GPRS-based modems, yet I don`t think it would have helped in the given situation... It seems the router ran out of ram, God knows why... I only have samba, ai cloud, transmission (which I just stopped, I`ve seeded some old gimp and open office versions for more than 10 months, lol), 1 vpn server...
On the 24th the router was really unreachable. I have some traces which seem interesting for me. Ivestigating the logs I noticed the following (reboot cron is 03:21):
Dec 26 03:20:20 dnsmasq-dhcp[231]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60s) *** this actually floods the logs, it accounts for more than 75% of the logs....
Dec 26 03:21:08 rc_service: watchdog 263:notify_rc reboot
Dec 26 03:21:08 dnsmasq-dhcp[231]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60s)
Dec 26 03:21:09 pppd[589]: fork failed: Cannot allocate memory
Dec 26 03:21:09 pppd[589]: Failed to create child process for /tmp/ppp/ip-down: Cannot allocate memory
Dec 26 03:21:09 kernel: Attempt to kill tasklet from interrupt
Dec 26 03:21:10 ovpn-server1[3614]: event_wait : Interrupted system call (code=4)
Dec 26 03:21:10 miniupnpd[3786]: Failed to get IP for interface ppp0
Dec 26 03:21:10 miniupnpd[3786]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Dec 26 03:21:11 WAN_Connection: Fail to connect with some issues.
Dec 26 03:21:12 ovpn-server1[3614]: openvpn_execve: unable to fork: Cannot allocate memory (errno=12)
Some more ram-deprived processes:
Dec 31 12:01:19 smbd[3440]: smbd_accept_connection: sys_fork() failed: Cannot allocate memory
Dec 31 12:01:19 smbd[3440]: [2019/12/31 12:01:19.225982, 0] smbd/server.c:572(smbd_accept_connection)
[...]
Dec 31 13:52:23 dnsmasq-dhcp[237]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60s)
Dec 31 13:53:14 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth xx:xx:xx:xx:xx:xx, status: 0, reason: d11 RC reserved (0)
Dec 31 13:53:14 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc xx:xx:xx:xx:xx:xx, status: 0, reason: d11 RC reserved (0)
Dec 31 13:53:15 dnsmasq-dhcp[237]: DHCPDISCOVER(br0) xx:xx:xx:xx:xx:xx
Dec 31 13:53:15 dnsmasq-dhcp[237]: DHCPOFFER(br0) xxx.xxx.xxx.xxx xx:xx:xx:xx:xx:xx
Dec 31 13:53:15 dnsmasq-dhcp[237]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60s)
Dec 31 13:53:15 dnsmasq-dhcp[237]: DHCPREQUEST(br0) xxx.xxx.xxx.xxx xx:xx:xx:xx:xx:xx
Dec 31 13:53:15 dnsmasq-dhcp[237]: DHCPACK(br0) xxx.xxx.xxx.xxx xx:xx:xx:xx:xx:xx xxxxxxxxxxxxxxxxxx
Dec 31 13:53:15 dnsmasq-dhcp[237]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60s)
Dec 31 13:53:36 dnsmasq[237]: failed to allocate 1028 bytes
Dec 31 13:54:15 dnsmasq-dhcp[237]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60s)
[...]
Dec 31 15:06:32 dnsmasq[237]: failed to allocate 1028 bytes
Dec 31 15:06:32 dnsmasq[237]: failed to allocate 1028 bytes
Dec 31 15:06:33 dnsmasq[237]: failed to allocate 1028 bytes
Dec 31 15:06:34 dnsmasq[237]: failed to allocate 1028 bytes
Dec 31 15:06:37 dnsmasq[237]: failed to allocate 1028 bytes
Dec 31 15:07:04 dnsmasq[237]: failed to allocate 1028 bytes
Dec 31 15:07:04 dnsmasq[237]: failed to allocate 1028 bytes
Dec 31 15:07:18 dnsmasq-dhcp[237]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60s)
Dec 31 15:08:03 dnsmasq[237]: script process exited with status 20
Dec 31 15:08:18 dnsmasq-dhcp[237]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60s)
Dec 31 15:09:07 dnsmasq[237]: failed to allocate 1028 bytes
[...]
and many others..
I am also facing a problem with traffic analyzer. Even after resetting the traffic monitoring settings and reinitializing the file, I still get:
Jan 1 09:10:55 rstats[270]: Problem loading /mnt/Data/Trafic/tomato_rstats_38d5471f9658.gz. Still trying...
I`ll turn off logs for JFFS`s sake (were on debug for several days), if anything like this ever occurs, I`ll turn them on again.
Any help or hints are greatly appreciated. I have downloaded both config file (for debug) and jffs.
I`ll factory reset it now.
Ah, yes, have a Happy New Year! Shall we all grow younger, be healthier, wealthier, smarter and better than before!