Release [Fork] Asuswrt-Merlin 374 LTS release 49E4

[frazor77]

Will do and no probs, I really appreciate the effort you put in to maintaining this firmware for all of us and for all the assistance you've given me!

I've spotted some different entries in the log:

dnsmasq-dhcp[16240]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device

Full Log: https://pastebin.com/wi10duUd

This would have been occurring between when I pasted the last log, but before you'd given me further instructions on next steps. Sorry I don't have the full log. I guess it could just be further deterioration?, but thought I'd share just in case. Sadly I rebooted since then when you suggested the additional steps.

 

[frazor77]

Thanks for hanging in there....sorry I'm having trouble getting my arms around this one.
Also, just for completeness, if it hangs again, also get a 'df' output.

Had another occurrence... however didn't spot when it happened so sadly the log might not be super useful: https://pastebin.com/uMXrNPxH

admin@RT-AC66U:/tmp/home/root# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root                20544     20544         0 100% /
tmpfs                   119760      4460    115300   4% /tmp
devfs                   119760         0    119760   0% /dev
/dev/mtdblock5           32768      1088     31680   3% /jffs

admin@RT-AC66U:/tmp/home/root# free
             total       used       free     shared    buffers     cached
Mem:        239524     151352      88172          0       9296      30648
-/+ buffers/cache:     111408     128116
Swap:            0          0          0



Mem: 151352K used, 88172K free, 0K shrd, 9296K buff, 30648K cached
CPU:  0.0% usr  0.0% sys  0.0% nic  100% idle  0.0% io  0.0% irq  0.0% sirq
Load average: 0.07 0.03 0.04 3/52 4282
  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND
  319     1 admin    S    46164 19.1   0  0.0 /sbin/wanduck
  619     1 admin    S    26276 10.9   0  0.0 httpd
  372     1 admin    S     9360  3.8   0  0.0 /usr/sbin/acsd
  361     1 admin    S     9024  3.7   0  0.0 rstats
  406     1 admin    S     7132  2.9   0  0.0 usbled
  325     1 admin    S     6552  2.7   0  0.0 /usr/sbin/haveged -r0 -w1024
  620     1 admin    S     5012  2.0   0  0.0 httpd -s -p 8443
  358     1 admin    S     3176  1.3   0  0.0 watchdog02
    1     0 admin    S     2924  1.2   0  0.0 /sbin/init
  567     1 admin    S     2868  1.1   0  0.0 ntp
  357     1 admin    S     2840  1.1   0  0.0 ots
  574     1 admin    S     2840  1.1   0  0.0 disk_monitor
  339     1 admin    S     2840  1.1   0  0.0 wpsaide
  160     1 admin    S     2836  1.1   0  0.0 console
  336     1 admin    S     2556  1.0   0  0.0 /bin/eapd
  413   412 admin    S     2184  0.9   0  0.0 u2ec
  412     1 admin    S     2184  0.9   0  0.0 u2ec
  414   413 admin    S     2184  0.9   0  0.0 u2ec
  342     1 admin    S     1732  0.7   0  0.0 nas
  379     1 admin    S     1496  0.6   0  0.0 /usr/sbin/pppd file /tmp/ppp/options.wan0
 4274  4268 admin    S     1488  0.6   0  0.0 -sh
  377     1 admin    S     1484  0.6   0  0.0 udhcpc -i eth0 -p /var/run/udhcpc0.pid -s /tmp/udhcpc -
  162   160 admin    S     1484  0.6   0  0.0 /bin/sh
 4282  4274 admin    R     1484  0.6   0  0.0 top
  348     1 admin    S     1480  0.6   0  0.0 crond -l 8
  612     1 admin    S     1476  0.6   0  0.0 syslogd -m 0 -O /tmp/syslog.log -S -s 256 -l 7
  616     1 admin    S     1476  0.6   0  0.0 /sbin/klogd
  326     1 admin    R     1384  0.5   0  0.0 protect_srv
  330   326 admin    S     1384  0.5   0  0.0 protect_srv
  331   330 admin    S     1384  0.5   0  0.0 protect_srv
  344     1 nobody   S     1376  0.5   0  0.0 dnsmasq --log-async
 4268   618 admin    S     1336  0.5   0  0.0 dropbear -p 192.168.1.99:22 -I 1200 -j -k
  618     1 admin    S     1316  0.5   0  0.0 dropbear -p 192.168.1.99:22 -I 1200 -j -k
  350     1 admin    S     1292  0.5   0  0.0 networkmap --bootwait
  416     1 admin    S     1248  0.5   0  0.0 lpd
  369     1 admin    S     1192  0.4   0  0.0 lld2d br0
  349     1 admin    S     1160  0.4   0  0.0 /usr/sbin/infosvr br0
  673     1 admin    S      900  0.3   0  0.0 miniupnpd -f /etc/upnp/config
  125     1 admin    S      644  0.2   0  0.0 hotplug2 --persistent --no-coldplug
    3     2 admin    SWN      0  0.0   0  0.0 [ksoftirqd/0]
    4     2 admin    SW<      0  0.0   0  0.0 [events/0]
   52     2 admin    SW       0  0.0   0  0.0 [pdflush]
   98     2 admin    SW<      0  0.0   0  0.0 [mtdblockd]
  186     2 admin    SW<      0  0.0   0  0.0 [khubd]
  167     2 admin    SWN      0  0.0   0  0.0 [jffs2_gcd_mtd5]
    5     2 admin    SW<      0  0.0   0  0.0 [khelper]
    2     0 admin    SW<      0  0.0   0  0.0 [kthreadd]
   20     2 admin    SW<      0  0.0   0  0.0 [kblockd/0]
   53     2 admin    SW<      0  0.0   0  0.0 [kswapd0]
   54     2 admin    SW<      0  0.0   0  0.0 [aio/0]
   51     2 admin    SW       0  0.0   0  0.0 [pdflush]
  121     2 admin    SW<      0  0.0   0  0.0 [kmmcd]

 

[serrj]

Will do and no probs, I really appreciate the effort you put in to maintaining this firmware for all of us and for all the assistance you've given me!

I've spotted some different entries in the log:

dnsmasq-dhcp[16240]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device

Full Log: https://pastebin.com/wi10duUd

This would have been occurring between when I pasted the last log, but before you'd given me further instructions on next steps. Sorry I don't have the full log. I guess it could just be further deterioration?, but thought I'd share just in case. Sadly I rebooted since then when you suggested the additional steps.

I just had the same on 50E8:

Release - [Fork] Asuswrt-Merlin 374 LTS release 50E8

www.snbforums.com

 

[frazor77]

More data, if its useful:

admin@RT-AC66U:/tmp/home/root# free
             total       used       free     shared    buffers     cached
Mem:        239524     133760     105764          0       9296      30740
-/+ buffers/cache:      93724     145800
Swap:            0          0          0
admin@RT-AC66U:/tmp/home/root# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root                20544     20544         0 100% /
tmpfs                   119760      4548    115212   4% /tmp
devfs                   119760         0    119760   0% /dev
/dev/mtdblock5           32768      1088     31680   3% /jffs
admin@RT-AC66U:/tmp/home/root# top
Mem: 133744K used, 105780K free, 0K shrd, 9296K buff, 30740K cached
CPU:  8.3% usr  0.0% sys  0.0% nic 91.6% idle  0.0% io  0.0% irq  0.0% sirq
Load average: 0.00 0.01 0.00 2/51 5742
  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND
 5742  5732 admin    R     1484  0.6   0  8.3 top
  619     1 admin    S    37776 15.6   0  0.0 httpd
  372     1 admin    S    14764  6.1   0  0.0 /usr/sbin/acsd
  361     1 admin    S    14140  5.8   0  0.0 rstats
  406     1 admin    S     9844  4.0   0  0.0 usbled
  325     1 admin    S     6552  2.7   0  0.0 /usr/sbin/haveged -r0 -w1024
  620     1 admin    S     5012  2.0   0  0.0 httpd -s -p 8443
  358     1 admin    S     4016  1.6   0  0.0 watchdog02
  336     1 admin    S     3000  1.2   0  0.0 /bin/eapd
    1     0 admin    S     2932  1.2   0  0.0 /sbin/init
  567     1 admin    S     2892  1.2   0  0.0 ntp
  357     1 admin    S     2840  1.1   0  0.0 ots
  574     1 admin    S     2840  1.1   0  0.0 disk_monitor
  339     1 admin    S     2840  1.1   0  0.0 wpsaide
  160     1 admin    S     2836  1.1   0  0.0 console
  413   412 admin    S     2184  0.9   0  0.0 u2ec
  412     1 admin    S     2184  0.9   0  0.0 u2ec
  414   413 admin    S     2184  0.9   0  0.0 u2ec
  342     1 admin    S     1732  0.7   0  0.0 nas
  379     1 admin    S     1496  0.6   0  0.0 /usr/sbin/pppd file /tmp/ppp/options.wan0
 5732  5731 admin    S     1488  0.6   0  0.0 -sh
  377     1 admin    S     1484  0.6   0  0.0 udhcpc -i eth0 -p /var/run/udhcpc0.pid -s /tmp/udhcpc -t2 -T5 -A160 -b -
  162   160 admin    S     1484  0.6   0  0.0 /bin/sh
  348     1 admin    S     1480  0.6   0  0.0 crond -l 8
  612     1 admin    S     1476  0.6   0  0.0 syslogd -m 0 -O /tmp/syslog.log -S -s 256 -l 7
  616     1 admin    S     1476  0.6   0  0.0 /sbin/klogd
  326     1 admin    S     1384  0.5   0  0.0 protect_srv
  330   326 admin    S     1384  0.5   0  0.0 protect_srv
  331   330 admin    S     1384  0.5   0  0.0 protect_srv
  344     1 nobody   S     1376  0.5   0  0.0 dnsmasq --log-async
 5731   618 admin    S     1336  0.5   0  0.0 dropbear -p 192.168.1.99:22 -I 1200 -j -k
  618     1 admin    S     1316  0.5   0  0.0 dropbear -p 192.168.1.99:22 -I 1200 -j -k
  350     1 admin    S     1292  0.5   0  0.0 networkmap --bootwait
  416     1 admin    S     1248  0.5   0  0.0 lpd
  369     1 admin    S     1192  0.4   0  0.0 lld2d br0
  349     1 admin    S     1160  0.4   0  0.0 /usr/sbin/infosvr br0
  673     1 admin    S      900  0.3   0  0.0 miniupnpd -f /etc/upnp/config
  125     1 admin    S      644  0.2   0  0.0 hotplug2 --persistent --no-coldplug
    3     2 admin    SWN      0  0.0   0  0.0 [ksoftirqd/0]
    4     2 admin    SW<      0  0.0   0  0.0 [events/0]
   52     2 admin    SW       0  0.0   0  0.0 [pdflush]
   98     2 admin    SW<      0  0.0   0  0.0 [mtdblockd]
  186     2 admin    SW<      0  0.0   0  0.0 [khubd]
  167     2 admin    SWN      0  0.0   0  0.0 [jffs2_gcd_mtd5]
    5     2 admin    SW<      0  0.0   0  0.0 [khelper]
    2     0 admin    SW<      0  0.0   0  0.0 [kthreadd]
   20     2 admin    SW<      0  0.0   0  0.0 [kblockd/0]
   51     2 admin    SW       0  0.0   0  0.0 [pdflush]
   53     2 admin    SW<      0  0.0   0  0.0 [kswapd0]
   54     2 admin    SW<      0  0.0   0  0.0 [aio/0]
  121     2 admin    SW<      0  0.0   0  0.0 [kmmcd]
admin@RT-AC66U:/tmp/home/root#

Log: https://pastebin.com/ex6R1QBv

 

[frazor77]

Needed to reboot... weird thing post reboot (probably some reasonable explanation)... there's a gap in the log output between Aug 8 (when the watchdog last died) and Aug 12 (today)... i.e. it stops logging when the watchdog dies? (although this then does not show the missing log data I noted was mussing back on Tuesdays post - so that might now be helpful!)

log: https://pastebin.com/RgD1kuC7

 

[john9527]

Posted a 50DA development build...
- Prevents a potential conflict when trying to recover from httpd fails
- Reverts a Merlin backport which added an additional CONNTRACK option

I still have no idea what could have changed to cause AC66 problems, so these are shots in the dark.

 

[john9527]

there's a gap in the log output between Aug 8 (when the watchdog last died) and Aug 12 (today)

This would seem to indicate multiple processes are dying. I hate to come back to it, but has anyone actually tried swapping out the power supply?

 

[Nite01]

This would seem to indicate multiple processes are dying. I hate to come back to it, but has anyone actually tried swapping out the power supply?

All I can tell you regarding this, is that I tried 49E4 and I had the router rebooting randomly. I then reverted to 46E9 and I currently have an uptime of 29 days without any problem.
So I think its unlikely an hardware issue.

 

[john9527]

@Nite01
Did you reformat jffs when moving 'up' in level.....the other possibility is still a corrupted jffs partition.

 

[mistercoffee1]

I’m also back on 46E9 with my N66U, 24+ days of uptime.
Prior to this, 48E7 and 49E4 would reboot after 5 to 7 days, with watchdog in the error logs.
I haven’t seen this code in 46E9 ever.

 

[fiasko]

My AC66 unit acts as secondary AP role in my house, and I didn't realy notice the rebooting issue before. It's using 48E7 build and looks like the reboot issue was there as well. I just updated to 50DA firmware to see if it makes any difference.

 

[Nite01]

@Nite01
Did you reformat jffs when moving 'up' in level.....the other possibility is still a corrupted jffs partition.

I had the stock firmware before 49e4 (I used the asus utility to flash it, and did the reformat jffs as per instructions).
Then I just flashed 46e9 from the gui, and did the reformat again.

One note I can add, is that I always keep the 5ghz antenna disabled, as I only need the 2.4ghz. I disabled it in all the three cases. Could that cause a problem with >46e9 ?

Also note that I didn't try any in-between releases... I just picked 46e9 because people were reporting not having issues with it.

 

[frazor77]

This would seem to indicate multiple processes are dying. I hate to come back to it, but has anyone actually tried swapping out the power supply?

Updated to 50DA... will report back.

I don't have access to another compatible supply currently. If this update yields nothing, might try downgrading to see if 46e9 fixes it... either way that will show if 46e9 was the last good pre-break point or not.

 

[tsanga]

All I can tell you regarding this, is that I tried 49E4 and I had the router rebooting randomly. I then reverted to 46E9 and I currently have an uptime of 29 days without any problem.
So I think its unlikely an hardware issue.

I’m also back on 46E9 with my N66U, 24+ days of uptime.
Prior to this, 48E7 and 49E4 would reboot after 5 to 7 days, with watchdog in the error logs.
I haven’t seen this code in 46E9 ever.

I’ve gone through 46Ex, 47Ex, 48Ex and 49Ex.

No issues with 46 and 47. I’m currently running 47EB with no reboots, with all the same samba error messages in syslog that I’ve seen all along since restricting to SMBv2 only. With 48Ex, I started seeing the watchdog error messages and reboots every few days.

 

[aarv]

I downgraded to 48E2 look like no issues too, watchdog and wanduck are not increase memory usage in every minute, always stay in 2840 VSZ

 

[Rahul_K]

Been running 50DA for about 37 hours now. It does not look promising. I ran this script every hour:

#/bin/sh
# cru a uptimelog "0 * * * * /mnt/RouterStor/Scripts/uptime-mem.sh"

LOG_DIR=/mnt/RouterStor/Scripts/uptime-mem
LOG_FILE1=$LOG_DIR/top.log
LOG_FILE2=$LOG_DIR/df.log

uptime >> $LOG_FILE1
top -n 1 | grep "wanduck$\|watchdog$\|PID" >> $LOG_FILE1

uptime >> $LOG_FILE2
df -hT >> $LOG_FILE2

While the df output has remained constant throughout at:

 08:00:00 up 1 day, 13:12,  load average: 0.00, 0.00, 0.00
Filesystem           Type            Size      Used Available Use% Mounted on
/dev/root            squashfs       20.1M     20.1M         0 100% /
tmpfs                tmpfs         117.0M      4.8M    112.1M   4% /tmp
devfs                tmpfs         117.0M         0    117.0M   0% /dev
/dev/mtdblock5       jffs2          32.0M      1.0M     31.0M   3% /jffs

wanduck and watchdog's memory consumption has been steadily rising as before:

 19:01:40 up 13 min,  load average: 0.01, 0.07, 0.05
[7m  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND[0m
  392     1 admin    S     2976  1.2   0  0.0 watchdog
  361     1 admin    S     2972  1.2   0  0.0 /sbin/wanduck
 10:00:00 up 15:12,  load average: 0.00, 0.00, 0.00
[7m  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND[0m
  392     1 admin    S    12752  5.2   0  0.0 watchdog
  361     1 admin    S    11964  4.9   0  0.0 /sbin/wanduck
 11:00:00 up 16:12,  load average: 0.00, 0.00, 0.00
[7m  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND[0m
  392     1 admin    S    13404  5.5   0  0.0 watchdog
  361     1 admin    S    12564  5.2   0  0.0 /sbin/wanduck
 12:00:00 up 17:12,  load average: 0.00, 0.11, 0.13
[7m  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND[0m
  392     1 admin    S    14060  5.8   0  0.0 watchdog
  361     1 admin    S    13164  5.4   0  0.0 /sbin/wanduck
 13:00:00 up 18:12,  load average: 0.00, 0.00, 0.00
[7m  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND[0m
  392     1 admin    S    14712  6.1   0  0.0 watchdog
  361     1 admin    S    13764  5.7   0  0.0 /sbin/wanduck
 14:00:00 up 19:12,  load average: 0.00, 0.00, 0.00
[7m  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND[0m
  392     1 admin    S    15364  6.3   0  0.0 watchdog
  361     1 admin    S    14368  5.9   0  0.0 /sbin/wanduck
 15:00:01 up 20:12,  load average: 0.00, 0.00, 0.00
[7m  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND[0m
  392     1 admin    S    16016  6.6   0  0.0 watchdog
  361     1 admin    S    14968  6.2   0  0.0 /sbin/wanduck
 16:00:00 up 21:12,  load average: 0.00, 0.00, 0.00
[7m  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND[0m
  392     1 admin    S    16668  6.9   0  0.0 watchdog
  361     1 admin    S    15568  6.4   0  0.0 /sbin/wanduck
 17:00:00 up 22:12,  load average: 0.00, 0.00, 0.00
[7m  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND[0m
  392     1 admin    S    17324  7.1   0  0.0 watchdog
  361     1 admin    S    16168  6.7   0  0.0 /sbin/wanduck
 18:00:00 up 23:12,  load average: 0.00, 0.00, 0.00
[7m  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND[0m
  392     1 admin    S    17976  7.4   0  0.0 watchdog
  361     1 admin    S    16768  6.9   0  0.0 /sbin/wanduck
 19:00:00 up 1 day, 12 min,  load average: 0.00, 0.00, 0.00
[7m  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND[0m
  392     1 admin    S    18628  7.7   0  0.0 watchdog
  361     1 admin    S    17368  7.2   0  0.0 /sbin/wanduck
 20:00:00 up 1 day,  1:12,  load average: 0.00, 0.00, 0.00
[7m  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND[0m
  392     1 admin    S    19280  8.0   0  0.0 watchdog
  361     1 admin    S    17972  7.4   0  0.0 /sbin/wanduck
 21:00:00 up 1 day,  2:12,  load average: 0.05, 0.04, 0.00
[7m  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND[0m
  392     1 admin    S    19932  8.2   0  0.0 watchdog
  361     1 admin    S    18572  7.7   0  0.0 /sbin/wanduck
 22:00:00 up 1 day,  3:12,  load average: 0.00, 0.02, 0.05
[7m  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND[0m
  392     1 admin    S    20588  8.5   0  0.0 watchdog
  361     1 admin    S    19168  7.9   0  0.0 /sbin/wanduck
 23:00:00 up 1 day,  4:12,  load average: 0.00, 0.00, 0.00
[7m  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND[0m
  392     1 admin    S    21240  8.8   0  0.0 watchdog
  361     1 admin    S    19768  8.2   0  0.0 /sbin/wanduck
 00:00:00 up 1 day,  5:12,  load average: 0.00, 0.00, 0.00
[7m  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND[0m
  392     1 admin    S    21892  9.0   0  0.0 watchdog
  361     1 admin    S    20368  8.4   0  0.0 /sbin/wanduck
 01:00:00 up 1 day,  6:12,  load average: 0.00, 0.00, 0.00
[7m  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND[0m
  392     1 admin    S    22544  9.3   0  0.0 watchdog
  361     1 admin    S    20972  8.7   0  0.0 /sbin/wanduck
 02:00:00 up 1 day,  7:12,  load average: 0.00, 0.00, 0.00
[7m  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND[0m
  392     1 admin    S    23196  9.6   0  0.0 watchdog
  361     1 admin    S    21572  8.9   0  0.0 /sbin/wanduck
 03:00:00 up 1 day,  8:12,  load average: 0.00, 0.00, 0.00
[7m  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND[0m
  392     1 admin    S    23848  9.9   0  0.0 watchdog
  361     1 admin    S    22172  9.2   0  0.0 /sbin/wanduck
 04:00:00 up 1 day,  9:12,  load average: 0.00, 0.00, 0.00
[7m  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND[0m
  392     1 admin    S    24504 10.1   0  0.0 watchdog
  361     1 admin    S    22772  9.4   0  0.0 /sbin/wanduck
 05:00:00 up 1 day, 10:12,  load average: 0.00, 0.00, 0.00
[7m  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND[0m
  392     1 admin    S    25156 10.4   0  0.0 watchdog
  361     1 admin    S    23372  9.7   0  0.0 /sbin/wanduck
 06:00:00 up 1 day, 11:12,  load average: 0.00, 0.00, 0.00
[7m  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND[0m
  392     1 admin    S    25808 10.7   0  0.0 watchdog
  361     1 admin    S    23976  9.9   0  0.0 /sbin/wanduck
 07:00:00 up 1 day, 12:12,  load average: 0.00, 0.00, 0.00
[7m  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND[0m
  392     1 admin    S    26460 10.9   0  0.0 watchdog
  361     1 admin    S    24576 10.2   0  0.0 /sbin/wanduck
 08:00:00 up 1 day, 13:12,  load average: 0.00, 0.00, 0.00
[7m  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND[0m
  392     1 admin    S    27116 11.2   0  0.0 watchdog
  361     1 admin    S    25176 10.4   0  0.0 /sbin/wanduck

 

[ColinTaylor]

Been running 50DA for about 37 hours now. It does not look promising...

wanduck and watchdog's memory consumption has been steadily rising as before:

I'm observing the same thing on my N66U running 50DA.

The screen shots below were taken ~24 hours apart. The N66U is disconnected from everything other than one WiFi client.

I did not see this behaviour on 47EB.



At first it was only watchdog that was creeping up by 4kB every 30-60 seconds. After I had left it overnight I saw that wanduck was also now increasing and at a slightly faster rate. Comparing the screenshots above we can see that the processes that increased in size were wanduck, watchdog, usbled and rstats. I think I'd dismiss rstats as normal behaviour, but the other three processes are soft links to rc (which may or may not be relevant).

EDIT: Added a third screenshot after another 24 hours. wanduck, watchdog, usbled and rstats are still the only processes that are steadily increasing in size.

 

[fiasko]

Last evening my AC66U with 50DA rebooted again after four days of uptime.
Firts log error was this.
Aug 19 19:49:32 watchdog02: no watchdog, restarting
After which all daemons stopped and router rebooted.

 

[domic]

@john9527 Pardon me for asking, which Linux kernel version is the latest release built on? I couldn't find any info in the changelogs or readme's in the download folder on one drive.

 

[ColinTaylor]

@john9527 Pardon me for asking, which Linux kernel version is the latest release built on? I couldn't find any info in the changelogs or readme's in the download folder on one drive.

If it's a MIPS model like the N66U or AC66U it's 2.6.22.19.