Rebooting every 1-2 minutes

Report problems and success stories with Gargoyle on various hardware platforms.

Moderator: Moderators

Post Reply
maphew
Posts: 22
Joined: Tue Oct 13, 2015 3:10 am

Rebooting every 1-2 minutes

Post by maphew »

I have a TP-Link Archer-C7 AC1750 running Gargoyle v1.9.1 since mid January. Outside of some issues in first week dropping WAN it's been running fine.

Today I tweaked the QoS Up/Down max rates and re-enabled a user quota. After applying settings the router began behaving strangely, dropping connections frequently. Watching the lights on the router it looks like it's rebooting about every 1 to 2 minutes.

From a wired Windows workstation I set a continuous ping to the router. There is a reply with <1ms delay for about 1minute, then 3 or 4 timeouts in a row, then "destination host unreachable", then a couple more timeouts, then a handful of reply, a few more timeouts, and then 1 or 2 minutes of continuous reply. And then repeat.

Code: Select all

{...}
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
{...}
Powering off the router for 1 minute does not change the pattern. Neither does rebooting from the web Admin panel.

Within the 1 or 2 minute time "it's on" time interval I've been able to login long enough to disable QoS and all but one active quota (there were 6), and issue controlled reboot. No change observed.

I also upgraded the firmware to v1.9.2, preserving settings. no change. (thanks for mobile interface!)

The ping behaviour and reboot cycle has not varied for at least the last 1.5 hrs.

[update] I tried to attach the ping log but the forum tells me .txt and .log are invalid extensions.

maphew
Posts: 22
Joined: Tue Oct 13, 2015 3:10 am

Re: Rebooting every 1-2 minutes

Post by maphew »

Repeatedly executed `logread` in ssh session until Putty freezes due to lost connection:

Code: Select all

login as: root
root@192.168.1.1's password:


BusyBox v1.23.2 (2017-02-09 15:24:42 EST) built-in shell (ash)

------------------------------------------------------------------
|            _____                             _                 |
|           |  __ \                           | |                |
|           | |  \/ __ _ _ __ __ _  ___  _   _| | ___            |
|           | | __ / _` | '__/ _` |/ _ \| | | | |/ _ \           |
|           | |_\ \ (_| | | | (_| | (_) | |_| | |  __/           |
|            \____/\__,_|_|  \__, |\___/ \__, |_|\___|           |
|                             __/ |       __/ |                  |
|                            |___/       |___/                   |
|                                                                |
|----------------------------------------------------------------|
| Gargoyle version 1.9.2    | OpenWrt Chaos Calmer branch        |
| Gargoyle revision ecc1da74| OpenWrt commit 03d52cf             |
| Built February 10, 2017   | Target  ar71xx/ath10k-large        |
------------------------------------------------------------------

~~~
...snip...
repeatedly executed `logread` until Putty freezes due to lost connection
~~~

root@gateway:~# logread
Fri Mar 31 22:14:06 2017 daemon.notice netifd: Interface 'wan' is setting up now
Fri Mar 31 22:14:06 2017 daemon.notice netifd: Interface 'wan6' has link connectivity
Fri Mar 31 22:14:06 2017 daemon.notice netifd: Interface 'wan6' is setting up now
Fri Mar 31 22:14:06 2017 daemon.notice netifd: Interface 'wan6' is now up
Fri Mar 31 22:14:06 2017 daemon.notice netifd: wan (1871): udhcpc (v1.23.2) started
Fri Mar 31 22:14:06 2017 daemon.notice netifd: radio1 (1678): Configuration file: /var/run/hostapd-phy1.conf
Fri Mar 31 22:14:07 2017 kern.info kernel: [   31.760000] device wlan1 entered promiscuous mode
Fri Mar 31 22:14:07 2017 kern.info kernel: [   31.760000] br-lan: port 2(wlan1) entered forwarding state
Fri Mar 31 22:14:07 2017 kern.info kernel: [   31.770000] br-lan: port 2(wlan1) entered forwarding state
Fri Mar 31 22:14:07 2017 daemon.notice netifd: radio1 (1678): Using interface wlan1 with hwaddr 18:a6:f7:78:5b:3d and ssid "Blue-raven"
Fri Mar 31 22:14:07 2017 daemon.notice netifd: radio0 (1677): Configuration file: /var/run/hostapd-phy0.conf
Fri Mar 31 22:14:07 2017 daemon.notice netifd: wan (1871): Sending discover...
Fri Mar 31 22:14:07 2017 user.err syslog: error starting threads: errno 89 (Function not implemented)
Fri Mar 31 22:14:08 2017 user.emerg syslog: exportfs: could not open /var/lib/nfs/.etab.lock for locking: errno 2 (No such file or directory)
Fri Mar 31 22:14:08 2017 user.emerg syslog: exportfs: can't lock /var/lib/nfs/etab for writing
Fri Mar 31 22:14:08 2017 user.emerg syslog: exportfs: could not open /var/lib/nfs/.xtab.lock for locking: errno 2 (No such file or directory)
Fri Mar 31 22:14:08 2017 user.emerg syslog: exportfs: can't lock /var/lib/nfs/xtab for writing
Fri Mar 31 22:14:08 2017 kern.info kernel: [   32.690000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 1 is up
Fri Mar 31 22:14:08 2017 kern.info kernel: [   32.690000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 3 is up
Fri Mar 31 22:14:08 2017 kern.info kernel: [   32.700000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 4 is up
Fri Mar 31 22:14:08 2017 user.emerg syslog: Command failed: Not found
Fri Mar 31 22:14:08 2017 daemon.notice netifd: wan (1871): Sending select for 205.234.61.225...
Fri Mar 31 22:14:08 2017 daemon.notice netifd: wan (1871): Lease of 205.234.61.225 obtained, lease time 432000
Fri Mar 31 22:14:09 2017 kern.info kernel: [   33.770000] br-lan: port 2(wlan1) entered forwarding state
Fri Mar 31 22:14:10 2017 authpriv.info dropbear[2105]: Child connection from 192.168.1.99:5267
Fri Mar 31 22:14:10 2017 user.emerg syslog: ERROR: No valid dynamic DNS service configurations defined
Fri Mar 31 22:14:10 2017 user.emerg syslog: (Did you specify correct configuration file path?)
Fri Mar 31 22:14:11 2017 kern.info kernel: [   36.420000] br-lan: port 2(wlan1) entered disabled state
Fri Mar 31 22:14:11 2017 kern.info kernel: [   36.450000] br-lan: port 2(wlan1) entered forwarding state
Fri Mar 31 22:14:11 2017 kern.info kernel: [   36.450000] br-lan: port 2(wlan1) entered forwarding state
Fri Mar 31 22:14:11 2017 daemon.notice netifd: Interface 'wan' is now up
Fri Mar 31 22:14:11 2017 daemon.notice netifd: radio1 (1678): wlan1: interface state UNINITIALIZED->ENABLED
Fri Mar 31 22:14:11 2017 daemon.notice netifd: radio1 (1678): wlan1: AP-ENABLED
Fri Mar 31 22:14:11 2017 daemon.notice netifd: radio0 (1677): wlan0: interface state UNINITIALIZED->HT_SCAN
Fri Mar 31 22:14:11 2017 kern.info kernel: [   36.490000] device wlan0 entered promiscuous mode
Fri Mar 31 22:14:12 2017 daemon.notice netifd: Network device 'wlan1' link is up
Fri Mar 31 22:14:12 2017 daemon.notice netifd: radio0 (1677): Using interface wlan0 with hwaddr 18:a6:f7:78:5b:3c and ssid "Blue-raven-5g"
Fri Mar 31 22:14:13 2017 kern.info kernel: [   37.800000] br-lan: port 3(wlan0) entered forwarding state
Fri Mar 31 22:14:13 2017 kern.info kernel: [   37.810000] br-lan: port 3(wlan0) entered forwarding state
Fri Mar 31 22:14:13 2017 daemon.notice netifd: radio0 (1677): wlan0: interface state HT_SCAN->ENABLED
Fri Mar 31 22:14:13 2017 daemon.notice netifd: radio0 (1677): wlan0: AP-ENABLED
Fri Mar 31 22:14:13 2017 daemon.notice netifd: Network device 'wlan0' link is up
Fri Mar 31 22:14:13 2017 kern.info kernel: [   38.450000] br-lan: port 2(wlan1) entered forwarding state
Fri Mar 31 22:14:15 2017 kern.info kernel: [   39.810000] br-lan: port 3(wlan0) entered forwarding state
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: started, version 2.73 cachesize 150
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: compile time options: no-IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC loop-detect inotify
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: DNS service limited to local subnets
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq-dhcp[2462]: DHCP, IP range 192.168.1.100 -- 192.168.1.249, lease time 12h
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.142.171.235#53 for domain micro
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.211.32.162#53 for domain micro
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 66.244.95.20#53 for domain micro
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.142.171.235#53 for domain oss
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.211.32.162#53 for domain oss
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 66.244.95.20#53 for domain oss
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.142.171.235#53 for domain null
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.211.32.162#53 for domain null
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 66.244.95.20#53 for domain null
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.142.171.235#53 for domain ing
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.211.32.162#53 for domain ing
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 66.244.95.20#53 for domain ing
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.142.171.235#53 for domain indy
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.211.32.162#53 for domain indy
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 66.244.95.20#53 for domain indy
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.142.171.235#53 for domain gopher
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.211.32.162#53 for domain gopher
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 66.244.95.20#53 for domain gopher
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.142.171.235#53 for domain geek
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.211.32.162#53 for domain geek
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 66.244.95.20#53 for domain geek
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.142.171.235#53 for domain fur
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.211.32.162#53 for domain fur
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 66.244.95.20#53 for domain fur
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.142.171.235#53 for domain free
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.211.32.162#53 for domain free
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 66.244.95.20#53 for domain free
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.142.171.235#53 for domain bbs
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.211.32.162#53 for domain bbs
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 66.244.95.20#53 for domain bbs
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.142.171.235#53 for domain dyn
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.211.32.162#53 for domain dyn
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 66.244.95.20#53 for domain dyn
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.142.171.235#53 for domain parody
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.211.32.162#53 for domain parody
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 66.244.95.20#53 for domain parody
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.142.171.235#53 for domain glue
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.211.32.162#53 for domain glue
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 66.244.95.20#53 for domain glue
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 176.58.118.172#53 for domain bit
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 106.187.47.17#53 for domain bit
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 178.32.31.41#53 for domain bit
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using local addresses only for domain lan
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: reading /tmp/resolv.conf.auto
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.142.171.235#53 for domain micro
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.211.32.162#53 for domain micro
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 66.244.95.20#53 for domain micro
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.142.171.235#53 for domain oss
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.211.32.162#53 for domain oss
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 66.244.95.20#53 for domain oss
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.142.171.235#53 for domain null
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.211.32.162#53 for domain null
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 66.244.95.20#53 for domain null
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.142.171.235#53 for domain ing
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.211.32.162#53 for domain ing
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 66.244.95.20#53 for domain ing
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.142.171.235#53 for domain indy
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.211.32.162#53 for domain indy
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 66.244.95.20#53 for domain indy
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.142.171.235#53 for domain gopher
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.211.32.162#53 for domain gopher
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 66.244.95.20#53 for domain gopher
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.142.171.235#53 for domain geek
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.211.32.162#53 for domain geek
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 66.244.95.20#53 for domain geek
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.142.171.235#53 for domain fur
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.211.32.162#53 for domain fur
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 66.244.95.20#53 for domain fur
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.142.171.235#53 for domain free
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.211.32.162#53 for domain free
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 66.244.95.20#53 for domain free
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.142.171.235#53 for domain bbs
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.211.32.162#53 for domain bbs
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 66.244.95.20#53 for domain bbs
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.142.171.235#53 for domain dyn
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.211.32.162#53 for domain dyn
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 66.244.95.20#53 for domain dyn
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.142.171.235#53 for domain parody
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.211.32.162#53 for domain parody
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 66.244.95.20#53 for domain parody
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.142.171.235#53 for domain glue
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 95.211.32.162#53 for domain glue
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 66.244.95.20#53 for domain glue
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 176.58.118.172#53 for domain bit
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 106.187.47.17#53 for domain bit
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 178.32.31.41#53 for domain bit
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using local addresses only for domain lan
Fri Mar 31 22:14:17 2017 daemon.warn dnsmasq[2462]: ignoring nameserver 192.168.1.1 - local interface
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 199.85.229.82#53
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 198.135.216.162#53
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 199.85.225.226#53
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: using nameserver 205.234.56.46#53
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: read /etc/hosts - 21 addresses
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq[2462]: read /tmp/hosts/dhcp - 1 addresses
Fri Mar 31 22:14:17 2017 daemon.info dnsmasq-dhcp[2462]: read /etc/ethers - 12 addresses
Fri Mar 31 22:14:17 2017 kern.notice kernel: [   42.460000] random: nonblocking pool is initialized
Fri Mar 31 22:14:19 2017 daemon.info hostapd: wlan0: STA a8:47:4a:ba:e0:37 IEEE 802.11: authenticated
Fri Mar 31 22:14:19 2017 daemon.info hostapd: wlan0: STA a8:47:4a:ba:e0:37 IEEE 802.11: associated (aid 1)
Fri Mar 31 22:14:19 2017 daemon.info hostapd: wlan0: STA a8:47:4a:ba:e0:37 RADIUS: starting accounting session 58DF3725-00000000
Fri Mar 31 22:14:19 2017 daemon.info hostapd: wlan0: STA a8:47:4a:ba:e0:37 WPA: pairwise key handshake completed (RSN)
Fri Mar 31 22:14:19 2017 daemon.info dnsmasq-dhcp[2462]: DHCPDISCOVER(br-lan) 192.168.1.162 a8:47:4a:ba:e0:37
Fri Mar 31 22:14:19 2017 daemon.info dnsmasq-dhcp[2462]: DHCPOFFER(br-lan) 192.168.1.162 a8:47:4a:ba:e0:37
Fri Mar 31 22:14:19 2017 daemon.info dnsmasq-dhcp[2462]: DHCPREQUEST(br-lan) 192.168.1.162 a8:47:4a:ba:e0:37
Fri Mar 31 22:14:19 2017 daemon.info dnsmasq-dhcp[2462]: DHCPACK(br-lan) 192.168.1.162 a8:47:4a:ba:e0:37 Coles-PS4
Fri Mar 31 22:14:19 2017 daemon.info dnsmasq-dhcp[2462]: DHCPINFORM(br-lan) 192.168.1.99 bc:5f:f4:e9:fc:10
Fri Mar 31 22:14:19 2017 daemon.info dnsmasq-dhcp[2462]: DHCPACK(br-lan) 192.168.1.99 bc:5f:f4:e9:fc:10 server
Fri Mar 31 22:14:21 2017 authpriv.notice dropbear[2105]: Password auth succeeded for 'root' from 192.168.1.99:5267
Fri Mar 31 22:14:29 2017 authpriv.info dropbear[2511]: Child connection from 116.31.116.25:46248
Fri Mar 31 22:14:29 2017 daemon.info hostapd: wlan1: STA b0:34:95:d3:1d:0c IEEE 802.11: authenticated
Fri Mar 31 22:14:29 2017 daemon.info hostapd: wlan1: STA b0:34:95:d3:1d:0c IEEE 802.11: associated (aid 1)
Fri Mar 31 22:14:30 2017 daemon.info hostapd: wlan1: STA b0:34:95:d3:1d:0c RADIUS: starting accounting session 58DF3720-00000000
Fri Mar 31 22:14:30 2017 daemon.info hostapd: wlan1: STA b0:34:95:d3:1d:0c WPA: pairwise key handshake completed (RSN)
Fri Mar 31 22:14:30 2017 daemon.info dnsmasq-dhcp[2462]: DHCPREQUEST(br-lan) 192.168.1.160 b0:34:95:d3:1d:0c
Fri Mar 31 22:14:30 2017 daemon.info dnsmasq-dhcp[2462]: DHCPACK(br-lan) 192.168.1.160 b0:34:95:d3:1d:0c Coles-Ipod
Fri Mar 31 22:14:32 2017 authpriv.info dropbear[2511]: Exit before auth: Disconnect received
Fri Mar 31 22:14:36 2017 user.notice root: vsftpd init: mounted = 0
Fri Mar 31 22:14:36 2017 user.emerg syslog: ERROR: No drives attached, no directories to share!
Fri Mar 31 22:14:36 2017 user.emerg syslog: setting up led USB1
Fri Mar 31 22:14:36 2017 user.emerg syslog: setting up led USB2
Fri Mar 31 22:14:36 2017 user.emerg syslog: setting up led WLAN2G
Fri Mar 31 22:14:36 2017 user.emerg syslog: setting up led WLAN5G
Fri Mar 31 22:14:36 2017 daemon.info procd: - init complete -
Fri Mar 31 22:15:25 2017 daemon.err miniupnpd[2645]: could not open lease file: /var/upnp.leases
Fri Mar 31 22:15:25 2017 daemon.notice miniupnpd[2645]: HTTP listening on port 5000
Fri Mar 31 22:15:25 2017 daemon.notice miniupnpd[2645]: Listening for NAT-PMP/PCP traffic on port 5351
Fri Mar 31 22:15:26 2017 user.notice firewall: Reloading firewall due to ifup of wan6 (eth0)
Fri Mar 31 22:15:29 2017 user.notice firewall: Reloading firewall due to ifup of wan (eth0)
Fri Mar 31 22:15:30 2017 daemon.info hostapd: wlan1: STA 74:e5:0b:af:f8:10 IEEE 802.11: authenticated
Fri Mar 31 22:15:30 2017 daemon.info hostapd: wlan1: STA 74:e5:0b:af:f8:10 IEEE 802.11: associated (aid 2)
Fri Mar 31 22:15:30 2017 daemon.info hostapd: wlan1: STA 74:e5:0b:af:f8:10 RADIUS: starting accounting session 58DF3720-00000001
Fri Mar 31 22:15:30 2017 daemon.info hostapd: wlan1: STA 74:e5:0b:af:f8:10 WPA: pairwise key handshake completed (RSN)
Fri Mar 31 22:15:34 2017 kern.warn kernel: [   82.520000] ipt_bandwidth: timezone shift of 420 minutes detected, adjusting
Fri Mar 31 22:15:34 2017 kern.warn kernel: [   82.530000]                old minutes west=0, new minutes west=420
root@gateway:~#
Last edited by maphew on Sat Apr 01, 2017 1:05 pm, edited 2 times in total.

maphew
Posts: 22
Joined: Tue Oct 13, 2015 3:10 am

[SOLVED]: Rebooting every 1-2 minutes

Post by maphew »

Solved, provisionally.

Following a hint in "Gargoyle CLI" viewtopic.php?f=8&t=8505 thread:

"/usr/data/bwmon - where graph data is stored (and can occasionally cause boot loops)"

I used WinSCP to delete contents of `/usr/data/bwmon` and `/usr/data/quotas` (after copying to local machine). Router has been stable for 20 minutes now, which makes me and my family happy! :) ...but now we've lost our usage stats, which is the reason we're using Gargoyle and not factory firmware. :?
Last edited by maphew on Sat Apr 01, 2017 1:06 pm, edited 1 time in total.

maphew
Posts: 22
Joined: Tue Oct 13, 2015 3:10 am

[SOLVED]: Rebooting every 1-2 minutes

Post by maphew »

Removing 'provisional' from Solved claim. It's been stable for >12 hours.

Now the question becomes: how to avoid this in future?

d3fz
Posts: 277
Joined: Sun Aug 28, 2016 7:34 pm

Re: Rebooting every 1-2 minutes

Post by d3fz »

Same problem here:
viewtopic.php?f=12&t=10912

Also here (with a possible "cause" for the problem)
viewtopic.php?f=6&t=5528

If think that's kind of a known bug. I got affected by it too, about 3 months ago, for no apparent reason. The bwmon data gets corrupted, and that's when the reboot loops starts.

Deleting all data from "/usr/data/bwmon" solves the problem, but now you already know that. :)

But for those who use quotas, or simply likes to monitor the network, losing track of consumed bandwidth is definitely not a good thing..

Also, make sure you don't use any "Layer 7 Protocol" in your QoS rules, as it may also lead to unexpected behavior.

(Questions to the devs)
Since there's no "easy way" to remove layer7 completely, wouldn't be better to simply remove the respective layer7 controls (checkbox, dropdown, etc) from the interface for now? That would keep the user from "shooting himself in the foot".

By the way, is it "safe" to restore backup bwmon data ?
TP-Link Archer C7 v2 - Gargoyle 1.12.X
TP-Link WR842ND v2 - Gargoyle 1.10.X
TP-Link RE450 AC v2 - Stock FW 1.0.4
TP-Link WA850RE v1.2 - LEDE 17.01.1

User avatar
CBx86
Posts: 157
Joined: Sun Jan 05, 2014 5:43 pm
Location: Brazil

Re: Rebooting every 1-2 minutes

Post by CBx86 »

Same!
I have this issue 1 time per year. :cry:

Post Reply