NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Enable Email Logging and Router Reboots
NOTICE:
For ANY users seeing mysterious reboots of there 7 or 8 series RBR routers rebooting at random or at specific time frames, we'd like to ask you to enable Email Logging of the RBR and config...
Ok, enabling email logs seems to help stop the RBR mysterious rebooting. Mines been online for 4+ days:
Uptime would have been more however we had a brown out last Wednesday.
Good to hear.
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
How many RBS do you have deployed?
How many devices do you have connected?
d700 wrote:
FYI, my 753 system has been up for 10 days since installing V4.6.8.5_2.1.9. I do NOT have email logging turned on.
Tack on another week for me. So interesting how the logs appear to be the source of the issue, I suspect the email logging has a house cleaning process that happens to prevent some kind of system process leak that occurs with the log process?
Hopefully this is located and fixed long term, but the work around has made my Orbi experience like it was when I'd purchased the RBK753 over a year ago.
I solved all my Orbi problems, firmware and otherwise. Now using an ASUS mesh. It's been real NetGear, and it's been fun, but it hasn't been real fun....
You can disable mail logging if you don't wan't to received emails and system should keep going. It's only when a factory reset and setup from scratch and don't re-enable email logging does the problem re-appear.
SeaRefractor wrote:
Tack on another week for me. So interesting how the logs appear to be the source of the issue, I suspect the email logging has a house cleaning process that happens to prevent some kind of system process leak that occurs with the log process?
Hopefully this is located and fixed long term, but the work around has made my Orbi experience like it was when I'd purchased the RBK753 over a year ago.
OK, the email logging does help immensely, but there's clearly something in addition that causes a reboot.
After several weeks, just had one minutes ago and when I check Debug.htm:
Basic Information
Firmware Version: V4.6.8.5_2.1.9
dumaos: v3.0.410
seal: v2.1.5.37-2
seal_services: v2.1.5.12-0
armor-bd: v2.2.100.3
spc-circle: v3.25.0.2
CPU Load: 39.67%
Memory Usage(Used/Total): 362 MB/874 MB
System Uptime: 0 days 00:12:16
Too bad no logs are provided that I have access to that shows whatever process or system either stalled or whatever.
