In your syslog I see multiple instances of the httpd server not being available, and the last reboot was caused by the watchdog process going away....very strange.I was on 48E2 -> 49D6 -> 50D6 (have been updating in the hope something in a newer build fixes it, but its still happening...
Please let me know what data/info I can supply to help diagnose this. syslog attached.
Yes, do this. Arguably there's no point in restoring the JFFS files if you're not using any add-on scripts. The only files are likely to be old syslog files. You can look the the backup file with something like 7-Zip to see if there's anything you want restored.Would it help to save JFFS -> format JFFS on reboot -> restore JFFS?
Did you move any of the 'certs' to jffs to free nvram space? In the syslog I saw a variety of httpd check errors...a timeout and two different cert verification fails. If so, it may be worthwhile to restore those from a different backup if available.Would it help to save JFFS -> format JFFS on reboot -> restore JFFS? (although I seem to remember it being suggested that doing that is somewhat a 'last resort'?)
watchdog02: no watchdog, restarting
watchdog: restart httpd, error detected or process not responding (12)
This looks to be exactly the same problem reported by @frazor77 in the posts above yours. Can you upload your syslog to pastebin for us to look at?RT-AC66U here.
Recently, I’ve been experiencing spontaneous reboots every week or so. In syslog, I always see the reboot prefaced by:
Or other times, not necessarily resulting in a reboot but didn’t notice this before:Code:watchdog02: no watchdog, restarting
Code:watchdog: restart httpd, error detected or process not responding (12)
The last stable release for me was 46Ex, when it could go 2-3 months easily and remain stable. I don’t remember running 47Ex very long, but 48Ex and 49Ex have been giving me this issue. I have not changed any settings, and rolling back to 46E9 restores the stability. I always save jffs, format and restore with each FW update.
Can anyone offer any additional tips for me to troubleshoot this? Is it possible to get more clues from the log?
This looks to be exactly the same problem reported by @frazor77 in the posts above yours. Can you upload your syslog to pastebin for us to look at?
Thanks for that. FYI it's not restarting at 3 am, that's just the default date/time the router gives itself when it boots up. The reboot times in your log file were:Got exactly the same problem several months ago. Router keeps restarting (mostly on same 3 a.m.) on it's own. Model: RT-AC66U
sadfjwx - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.pastebin.com
Jul 6 04:51:23 watchdog02: no watchdog, restarting
Jul 9 11:36:34 watchdog02: no watchdog, restarting
Jul 12 15:11:45 watchdog02: no watchdog, restarting
For your case, I'd definitely start with a jffs reformat....Got exactly the same problem several months ago. Router keeps restarting
Jul 5 00:54:06 watchdog: restart httpd, error detected or process not responding (12)
Jul 5 00:54:06 rc_service: watchdog 387:notify_rc stop_httpd
Jul 5 00:54:06 rc_service: watchdog 387:notify_rc start_httpd
Jul 5 00:54:06 rc_service: waiting "stop_httpd" via watchdog ...
Jul 5 00:54:07 httpd: start httpd
Jul 5 00:54:07 kernel: jffs2_flush_wbuf(): Write failed with -5
Jul 5 00:54:07 kernel: Write of 622 bytes at 0x00da4680 failed. returned -5, retlen 0
Jul 5 00:54:07 kernel: Not marking the space at 0x00da4680 as dirty because the flash driver returned retlen zero
Here you go. Thank you for taking a look.This looks to be exactly the same problem reported by @frazor77 in the posts above yours. Can you upload your syslog to pastebin for us to look at?
Hi I just upgraded a AC56U from an old release to 49E4. How can I make a full reset? I did a factory restore from GUI + a "Format JFFS on next boot". Is there anything else I should do? I'd just like to start clean.
Count me in among those whose RT-AC66U running 3.0.0.4.374.43_49E4j9527 restarts every 56-60 hours due to "watchdog02: no watchdog, restarting". My router logs can be found https://pastebin.com/HmPceqbS . It's worth noting that when the router restarts, the 2 processes wanduck and watchdog both start off with memory consumption looking like this (using top-m):Here you go. Thank you for taking a look.
EDIT: [LINK REMOVED]
In my case, syslog captured the beginning of one spontaneous reboot, then there was another one on Jul 9.
PID^^^VSZ^VSZRW RSS (SHR) DIRTY (SHR) STACK COMMAND
361 3468 1072 1340 516 788 0 84 /sbin/wanduck
392 3464 1068 1332 532 776 0 84 watchdog
PID^^^VSZ^VSZRW RSS (SHR) DIRTY (SHR) STACK COMMAND
361 37288 34892 35160 516 34608 0 84 /sbin/wanduck
For your case, I'd definitely start with a jffs reformat....
Code:Jul 5 00:54:06 watchdog: restart httpd, error detected or process not responding (12) Jul 5 00:54:06 rc_service: watchdog 387:notify_rc stop_httpd Jul 5 00:54:06 rc_service: watchdog 387:notify_rc start_httpd Jul 5 00:54:06 rc_service: waiting "stop_httpd" via watchdog ... Jul 5 00:54:07 httpd: start httpd Jul 5 00:54:07 kernel: jffs2_flush_wbuf(): Write failed with -5 Jul 5 00:54:07 kernel: Write of 622 bytes at 0x00da4680 failed. returned -5, retlen 0 Jul 5 00:54:07 kernel: Not marking the space at 0x00da4680 as dirty because the flash driver returned retlen zero
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!