I have a WRT1900ACS with OpenWrt 18.06.2 r7676-cddd7b4c77 / LuCI openwrt-18.06 branch (git-19.020.41695-6f6641d) which is generally working great but once per few days/weeks it goes down and only power cycling it helps. It happens few times in series and then again few days/weeks without any problems.
When it happens I have no ping to the router (192.168.0.1) and cannot access the Internet via Eth or WiFi. Can you help me debug this problem? Can I somehow generate logs even if I have to power cycle the Router?
Yeah, run a syslogger on your pc... for starters....
Jot notes in times durations... see status pages for any correlations.....
Down setting wireless if plausible for a while.... Sounds like some sort of heap buffer leak... You might be better places trying another release for a while... master or 06.1
On the router? Is logd logging to local file is enough or which other logger should I set up?
I cannot down my wireless network, my home automation is based on it 18.06.01 more stable than 18.06.02? What about master? Should I go with master?
It just happened again. Logs from logd don't show anything just before restart
Mon Mar 25 22:15:35 2019 daemon.notice hostapd: handle_probe_req: send failed
Mon Mar 25 22:15:35 2019 daemon.notice hostapd: handle_probe_req: send failed
Mon Mar 25 22:15:35 2019 daemon.notice hostapd: handle_probe_req: send failed
Mon Mar 25 22:15:35 2019 daemon.notice hostapd: handle_probe_req: send failed
Mon Mar 25 22:15:35 2019 daemon.notice hostapd: handle_probe_req: send failed
Mon Mar 25 22:15:35 2019 daemon.info procd: - init complete -
Mon Mar 25 22:15:35 2019 daemon.notice hostapd: handle_probe_req: send failed
Mon Mar 25 22:15:35 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:49 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:49 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:49 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:49 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.notice hostapd: handle_probe_req: send failed
Tue Mar 26 18:31:50 2019 daemon.info dnsmasq[1617]: exiting on receipt of SIGTERM
Tue Mar 26 18:31:50 2019 daemon.info dnsmasq[3838]: started, version 2.80 cachesize 150
Tue Mar 26 18:31:50 2019 daemon.info dnsmasq[3838]: DNS service limited to local subnets
Does it help @anon50098793 ?
^ any correlation with previous times? aka hour of the day it occurs?
post output of;
cat /tmp/run/hostapd-phy0.conf | grep -v bssid | grep -v passph
tell us a little more about
-number of clients, protocols, etc. etc.
Tell us about any additions your running other than stock ( qos, sqm, offload, etc. etc. )
Thank you all. I returned my router to the seller, Linksys did a hardware fix and not it works perfectly.
system
June 18, 2019, 1:18pm
7
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.
Is the 
I cycled the power around 18:31:31.