Time Warp: Crash 1 minute after boot from bwmon_gargoyle
Posted: Mon Mar 27, 2017 10:31 pm
Hello folks.
Yesterday I started getting yelled at by my loving family because their internet was going up and down. (mostly down) The webui showed no uptime more than one minute before it went away and I had to log in again.
Using ssh, I got into the box and looked around. Logs up to about the 43 second mark, then it worked for a while, then a silent reboot.
I ran top with a one-second delay for a few reboot cycles. In every case, when it died the process on top was bwmon_gargoyle. After some googling I tried /etc/init.d/bwmon_gargoyle stop (and disable).
Stability returned.
Archer C7 v2 running 1.9.1. QoS enabled for download and upload - although upload may have enabled itself as I don't remember doing it.
The router gets a daily 4am reboot. Nothing had changed in my config in weeks. The only thing I can think of is that the qos/bandwidth logs had grown to some critical level that instantly killed the box when bwmon_gargoyle was started.
I took the opportunity to update to 1.9.2 with a fresh config. However, I did a backup of my config, so I have a copy of everything in /usr/data/bwmon in the crash scenario.
Has anyone seen this before? Any data I can share to help track this down?
And thanks for everything you do!
Yesterday I started getting yelled at by my loving family because their internet was going up and down. (mostly down) The webui showed no uptime more than one minute before it went away and I had to log in again.
Using ssh, I got into the box and looked around. Logs up to about the 43 second mark, then it worked for a while, then a silent reboot.
I ran top with a one-second delay for a few reboot cycles. In every case, when it died the process on top was bwmon_gargoyle. After some googling I tried /etc/init.d/bwmon_gargoyle stop (and disable).
Stability returned.
Archer C7 v2 running 1.9.1. QoS enabled for download and upload - although upload may have enabled itself as I don't remember doing it.
The router gets a daily 4am reboot. Nothing had changed in my config in weeks. The only thing I can think of is that the qos/bandwidth logs had grown to some critical level that instantly killed the box when bwmon_gargoyle was started.
I took the opportunity to update to 1.9.2 with a fresh config. However, I did a backup of my config, so I have a copy of everything in /usr/data/bwmon in the crash scenario.
Has anyone seen this before? Any data I can share to help track this down?
And thanks for everything you do!