Menu
What's new
By:
Filters Better Search

Random timeouts on Firmware:3004.388.8_4

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

D

dineshgyl

New Around Here
Hi,

I see this in the logs:

So we can see WAN connection had some issues, then I chkwan script restarted the WAN which could not get the pppd connection up. But later chkwan rebooted the router then it was able to get WAN IP.

Code: 
Dec 15 20:57:22 WAN(0)_Connection: Fail to connect with some issues.
Dec 15 20:57:57 pppd[2577]: Serial link appears to be disconnected.
Dec 15 20:58:03 pppd[2577]: Connection terminated.
Dec 15 20:58:03 pppd[2577]: Modem hangup
Dec 15 20:58:04 (ChkWAN.sh): 5763 v1.17 Monitoring WAN connection using PING method to 206.80.253.250 check FAILED
Dec 15 20:58:07 (ChkWAN.sh): 5763 v1.17 Monitoring WAN connection using PING method to 209.197.128.2 check FAILED
Dec 15 20:58:10 (ChkWAN.sh): 5763 v1.17 Monitoring WAN connection using PING method to 209.197.128.5 check FAILED
Dec 15 20:58:13 (ChkWAN.sh): 5763 v1.17 Monitoring WAN connection using PING method to 9.9.9.9 check FAILED
Dec 15 20:58:16 (ChkWAN.sh): 5763 v1.17 Monitoring WAN connection using PING method to 1.1.1.1 check FAILED
Dec 15 20:58:26 (ChkWAN.sh): 5763 Monitoring pass 2 out of 3
Dec 15 20:58:29 (ChkWAN.sh): 5763 v1.17 Monitoring WAN connection using PING method to 206.80.253.250 check FAILED
Dec 15 20:58:32 (ChkWAN.sh): 5763 v1.17 Monitoring WAN connection using PING method to 209.197.128.2 check FAILED
Dec 15 20:58:35 (ChkWAN.sh): 5763 v1.17 Monitoring WAN connection using PING method to 209.197.128.5 check FAILED
Dec 15 20:58:38 (ChkWAN.sh): 5763 v1.17 Monitoring WAN connection using PING method to 9.9.9.9 check FAILED
Dec 15 20:58:41 (ChkWAN.sh): 5763 v1.17 Monitoring WAN connection using PING method to 1.1.1.1 check FAILED
Dec 15 20:58:48 pppd[2577]: Timeout waiting for PADO packets
Dec 15 20:58:51 (ChkWAN.sh): 5763 Monitoring pass 3 out of 3
Dec 15 20:58:54 (ChkWAN.sh): 5763 v1.17 Monitoring WAN connection using PING method to 206.80.253.250 check FAILED
Dec 15 20:58:58 (ChkWAN.sh): 5763 v1.17 Monitoring WAN connection using PING method to 209.197.128.2 check FAILED
Dec 15 20:59:01 (ChkWAN.sh): 5763 v1.17 Monitoring WAN connection using PING method to 209.197.128.5 check FAILED
Dec 15 20:59:04 (ChkWAN.sh): 5763 v1.17 Monitoring WAN connection using PING method to 9.9.9.9 check FAILED
Dec 15 20:59:07 (ChkWAN.sh): 5763 v1.17 Monitoring WAN connection using PING method to 1.1.1.1 check FAILED
Dec 15 20:59:07 (ChkWAN.sh): 5763 Renewing DHCP and restarting WAN (Action=WANONLY)
Dec 15 20:59:17 rc_service: service 6962:notify_rc restart_wan
Dec 15 20:59:17 custom_script: Running /jffs/scripts/wan-event (args: 0 stopping)
Dec 15 20:59:17 pppd[2577]: Unable to complete PPPoE Discovery
Dec 15 20:59:17 custom_script: Running /jffs/scripts/wan-event (args: 0 stopped)
Dec 15 20:59:17 custom_script: Running /jffs/scripts/wan-event (args: 1 stopping)
Dec 15 20:59:17 custom_script: Running /jffs/scripts/wan-event (args: 1 stopped)
Dec 15 20:59:17 custom_script: Running /jffs/scripts/wan-event (args: 0 init)
Dec 15 20:59:17 custom_script: Running /jffs/scripts/wan-event (args: 0 connecting)
Dec 15 20:59:17 pppd[7107]: pppd 2.4.7 started by admin, uid 0
Dec 15 20:59:17 (ChkWAN.sh): 7079 ChkWAN scheduled by cron
*/2 * * * * /jffs/scripts/ChkWAN.sh wan nowait #WAN_Check#
Dec 15 20:59:17 (ChkWAN.sh): 7079 v1.17 WAN connection status monitoring will begin in 10 seconds.....
Dec 15 20:59:28 (ChkWAN.sh): 7079 v1.17 Monitoring WAN connection using 3 target PING hosts (0.0.0.0 9.9.9.9 1.1.1.1) (Tries=3)
Dec 15 20:59:28 (ChkWAN.sh): 7079 Private LAN 0.0.0.0 will be skipped for WAN PING check!
Dec 15 20:59:31 (ChkWAN.sh): 7079 v1.17 Monitoring WAN connection using PING method to 9.9.9.9 check FAILED
Dec 15 20:59:34 (ChkWAN.sh): 7079 v1.17 Monitoring WAN connection using PING method to 1.1.1.1 check FAILED
Dec 15 20:59:36 services: apply rules error(19665)
Dec 15 20:59:37 zcip_client: configured 169.254.220.65
Dec 15 20:59:37 services: apply rules error(19707)
Dec 15 20:59:40 services: apply rules error(19707)
Dec 15 20:59:43 services: apply rules error(19707)
Dec 15 20:59:44 (ChkWAN.sh): 7079 Monitoring pass 2 out of 3
Dec 15 20:59:44 (ChkWAN.sh): 7079 Private LAN 0.0.0.0 will be skipped for WAN PING check!
Dec 15 20:59:47 services: apply rules error(19707)
Dec 15 20:59:47 (ChkWAN.sh): 7079 v1.17 Monitoring WAN connection using PING method to 9.9.9.9 check FAILED
Dec 15 20:59:49 services: apply rules error(19707)
Dec 15 20:59:50 (ChkWAN.sh): 7079 v1.17 Monitoring WAN connection using PING method to 1.1.1.1 check FAILED
Dec 15 20:59:52 pppd[7107]: Timeout waiting for PADO packets
Dec 15 20:59:53 services: apply rules error(19707)
Dec 15 20:59:55 services: apply rules error(19707)
Dec 15 20:59:58 services: apply rules error(19707)
Dec 15 21:00:00 (ChkWAN.sh): 7794 v1.17 Check WAN monitor ALREADY running...ABORTing
Dec 15 21:00:00 (ChkWAN.sh): 7079 Monitoring pass 3 out of 3
Dec 15 21:00:00 (ChkWAN.sh): 7079 Private LAN 0.0.0.0 will be skipped for WAN PING check!
Dec 15 21:00:01 services: apply rules error(19707)
Dec 15 21:00:03 (ChkWAN.sh): 7079 v1.17 Monitoring WAN connection using PING method to 9.9.9.9 check FAILED
Dec 15 21:00:04 services: apply rules error(19707)
Dec 15 21:00:07 (ChkWAN.sh): 7079 v1.17 Monitoring WAN connection using PING method to 1.1.1.1 check FAILED
Dec 15 21:00:07 (ChkWAN.sh): 7079 Rebooting..... (Action=REBOOT)
.
.
.
May  5 01:05:12 haveged: haveged starting up
May  5 01:05:13 rc_service: service 2267:notify_rc restart_firewall
May  5 01:05:15 WAN(0)_Connection: WAN(0) link down.
May  5 01:05:21 openvpn-routing: Initializing killswitch
May  5 01:05:22 httpd: Succeed to init SSL certificate...8443
May  5 01:05:22 disk_monitor: be idle
May  5 01:05:22 hour_monitor: daemon is starting
May  5 01:05:22 avahi-daemon[2363]: Alias name "RT-AX86U_Pro" successfully established.
May  5 01:05:22 Samba_Server: daemon is started
May  5 01:05:25 custom_script: Running /jffs/scripts/wan-event (args: 0 init)
May  5 01:05:25 custom_script: Running /jffs/scripts/wan-event (args: 0 connecting)
May  5 01:05:25 pppd[2603]: pppd 2.4.7 started by admin, uid 0
May  5 01:05:25 (ChkWAN.sh): 2564 ChkWAN scheduled by cron
*/2 * * * * /jffs/scripts/ChkWAN.sh wan nowait #WAN_Check#
May  5 01:05:25 (ChkWAN.sh): 2564 v1.17 WAN connection status monitoring will begin in 10 seconds.....
May  5 01:05:26 : fwver: 3.0.0.4_388.8_4 (sn:S7IG5Q20XXXXXXX /ha:XX:XX:XX:XX:XX:XX )
May  5 01:05:26 rc_service: cfg_server 2517:notify_rc update_nbr
May  5 01:05:26 rc_service: waitting "restart_firewall" via  ...
May  5 01:05:32 BONDING: option disabled
May  5 01:05:32 roamast: ROAMING Start...
May  5 01:05:33 WAN(0)_Connection: Fail to connect with some issues.
May  5 01:05:36 (ChkWAN.sh): 2564 v1.17 Monitoring WAN connection using 3 target PING hosts (0.0.0.0 9.9.9.9 1.1.1.1) (Tries=3)
May  5 01:05:36 (ChkWAN.sh): 2564 Private LAN 0.0.0.0 will be skipped for WAN PING check!
May  5 01:05:39 (ChkWAN.sh): 2564 v1.17 Monitoring WAN connection using PING method to 9.9.9.9 check FAILED
May  5 01:05:40 pppd[2603]: Connected to XX:XX:XX:XX:XX:XX via interface vlan40
May  5 01:05:40 pppd[2603]: Connect: ppp0 <--> vlan40
May  5 01:05:40 pppd[2603]: PAP authentication succeeded
May  5 01:05:40 pppd[2603]: peer from calling number XX:XX:XX:XX:XX:XX authorized
May  5 01:05:40 pppd[2603]: local  IP address 17X.2X6.X4.X2
May  5 01:05:40 pppd[2603]: remote IP address 2XX.X0.2XX.XX9
May  5 01:05:40 pppd[2603]: primary   DNS address 2XX.1XX.128.2
May  5 01:05:40 pppd[2603]: secondary DNS address 2XX.1XX.128.5
May  5 01:05:42 ntpd: Started ntpd
May  5 01:05:42 WAN(0)_Connection: WAN was restored.
Dec 15 21:01:33 ntpd: Initial clock set
Dec 15 21:01:33 rc_service: ntpd_synced 3255:notify_rc restart_diskmon
Dec 15 21:01:33 disk_monitor: Finish
 
A one-off in the logs or something that happens all the time? Maybe something caused by your ISP.
 
dineshgyl said:
Hi,

I see this in the logs:

So we can see WAN connection had some issues, then I chkwan script restarted the WAN which could not get the pppd connection up. But later chkwan rebooted the router then it was able to get WAN IP.

Code: 
Dec 15 20:57:22 WAN(0)_Connection: Fail to connect with some issues.
Dec 15 20:57:57 pppd[2577]: Serial link appears to be disconnected.
Dec 15 20:58:03 pppd[2577]: Connection terminated.
Dec 15 20:58:03 pppd[2577]: Modem hangup
Dec 15 20:58:04 (ChkWAN.sh): 5763 v1.17 Monitoring WAN connection using PING method to 206.80.253.250 check FAILED
Dec 15 20:58:07 (ChkWAN.sh): 5763 v1.17 Monitoring WAN connection using PING method to 209.197.128.2 check FAILED
Dec 15 20:58:10 (ChkWAN.sh): 5763 v1.17 Monitoring WAN connection using PING method to 209.197.128.5 check FAILED
Dec 15 20:58:13 (ChkWAN.sh): 5763 v1.17 Monitoring WAN connection using PING method to 9.9.9.9 check FAILED
Dec 15 20:58:16 (ChkWAN.sh): 5763 v1.17 Monitoring WAN connection using PING method to 1.1.1.1 check FAILED
Dec 15 20:58:26 (ChkWAN.sh): 5763 Monitoring pass 2 out of 3
Dec 15 20:58:29 (ChkWAN.sh): 5763 v1.17 Monitoring WAN connection using PING method to 206.80.253.250 check FAILED
Dec 15 20:58:32 (ChkWAN.sh): 5763 v1.17 Monitoring WAN connection using PING method to 209.197.128.2 check FAILED
Dec 15 20:58:35 (ChkWAN.sh): 5763 v1.17 Monitoring WAN connection using PING method to 209.197.128.5 check FAILED
Dec 15 20:58:38 (ChkWAN.sh): 5763 v1.17 Monitoring WAN connection using PING method to 9.9.9.9 check FAILED
Dec 15 20:58:41 (ChkWAN.sh): 5763 v1.17 Monitoring WAN connection using PING method to 1.1.1.1 check FAILED
Dec 15 20:58:48 pppd[2577]: Timeout waiting for PADO packets
Dec 15 20:58:51 (ChkWAN.sh): 5763 Monitoring pass 3 out of 3
Dec 15 20:58:54 (ChkWAN.sh): 5763 v1.17 Monitoring WAN connection using PING method to 206.80.253.250 check FAILED
Dec 15 20:58:58 (ChkWAN.sh): 5763 v1.17 Monitoring WAN connection using PING method to 209.197.128.2 check FAILED
Dec 15 20:59:01 (ChkWAN.sh): 5763 v1.17 Monitoring WAN connection using PING method to 209.197.128.5 check FAILED
Dec 15 20:59:04 (ChkWAN.sh): 5763 v1.17 Monitoring WAN connection using PING method to 9.9.9.9 check FAILED
Dec 15 20:59:07 (ChkWAN.sh): 5763 v1.17 Monitoring WAN connection using PING method to 1.1.1.1 check FAILED
Dec 15 20:59:07 (ChkWAN.sh): 5763 Renewing DHCP and restarting WAN (Action=WANONLY)
Dec 15 20:59:17 rc_service: service 6962:notify_rc restart_wan
Dec 15 20:59:17 custom_script: Running /jffs/scripts/wan-event (args: 0 stopping)
Dec 15 20:59:17 pppd[2577]: Unable to complete PPPoE Discovery
Dec 15 20:59:17 custom_script: Running /jffs/scripts/wan-event (args: 0 stopped)
Dec 15 20:59:17 custom_script: Running /jffs/scripts/wan-event (args: 1 stopping)
Dec 15 20:59:17 custom_script: Running /jffs/scripts/wan-event (args: 1 stopped)
Dec 15 20:59:17 custom_script: Running /jffs/scripts/wan-event (args: 0 init)
Dec 15 20:59:17 custom_script: Running /jffs/scripts/wan-event (args: 0 connecting)
Dec 15 20:59:17 pppd[7107]: pppd 2.4.7 started by admin, uid 0
Dec 15 20:59:17 (ChkWAN.sh): 7079 ChkWAN scheduled by cron
*/2 * * * * /jffs/scripts/ChkWAN.sh wan nowait #WAN_Check#
Dec 15 20:59:17 (ChkWAN.sh): 7079 v1.17 WAN connection status monitoring will begin in 10 seconds.....
Dec 15 20:59:28 (ChkWAN.sh): 7079 v1.17 Monitoring WAN connection using 3 target PING hosts (0.0.0.0 9.9.9.9 1.1.1.1) (Tries=3)
Dec 15 20:59:28 (ChkWAN.sh): 7079 Private LAN 0.0.0.0 will be skipped for WAN PING check!
Dec 15 20:59:31 (ChkWAN.sh): 7079 v1.17 Monitoring WAN connection using PING method to 9.9.9.9 check FAILED
Dec 15 20:59:34 (ChkWAN.sh): 7079 v1.17 Monitoring WAN connection using PING method to 1.1.1.1 check FAILED
Dec 15 20:59:36 services: apply rules error(19665)
Dec 15 20:59:37 zcip_client: configured 169.254.220.65
Dec 15 20:59:37 services: apply rules error(19707)
Dec 15 20:59:40 services: apply rules error(19707)
Dec 15 20:59:43 services: apply rules error(19707)
Dec 15 20:59:44 (ChkWAN.sh): 7079 Monitoring pass 2 out of 3
Dec 15 20:59:44 (ChkWAN.sh): 7079 Private LAN 0.0.0.0 will be skipped for WAN PING check!
Dec 15 20:59:47 services: apply rules error(19707)
Dec 15 20:59:47 (ChkWAN.sh): 7079 v1.17 Monitoring WAN connection using PING method to 9.9.9.9 check FAILED
Dec 15 20:59:49 services: apply rules error(19707)
Dec 15 20:59:50 (ChkWAN.sh): 7079 v1.17 Monitoring WAN connection using PING method to 1.1.1.1 check FAILED
Dec 15 20:59:52 pppd[7107]: Timeout waiting for PADO packets
Dec 15 20:59:53 services: apply rules error(19707)
Dec 15 20:59:55 services: apply rules error(19707)
Dec 15 20:59:58 services: apply rules error(19707)
Dec 15 21:00:00 (ChkWAN.sh): 7794 v1.17 Check WAN monitor ALREADY running...ABORTing
Dec 15 21:00:00 (ChkWAN.sh): 7079 Monitoring pass 3 out of 3
Dec 15 21:00:00 (ChkWAN.sh): 7079 Private LAN 0.0.0.0 will be skipped for WAN PING check!
Dec 15 21:00:01 services: apply rules error(19707)
Dec 15 21:00:03 (ChkWAN.sh): 7079 v1.17 Monitoring WAN connection using PING method to 9.9.9.9 check FAILED
Dec 15 21:00:04 services: apply rules error(19707)
Dec 15 21:00:07 (ChkWAN.sh): 7079 v1.17 Monitoring WAN connection using PING method to 1.1.1.1 check FAILED
Dec 15 21:00:07 (ChkWAN.sh): 7079 Rebooting..... (Action=REBOOT)
.
.
.
May  5 01:05:12 haveged: haveged starting up
May  5 01:05:13 rc_service: service 2267:notify_rc restart_firewall
May  5 01:05:15 WAN(0)_Connection: WAN(0) link down.
May  5 01:05:21 openvpn-routing: Initializing killswitch
May  5 01:05:22 httpd: Succeed to init SSL certificate...8443
May  5 01:05:22 disk_monitor: be idle
May  5 01:05:22 hour_monitor: daemon is starting
May  5 01:05:22 avahi-daemon[2363]: Alias name "RT-AX86U_Pro" successfully established.
May  5 01:05:22 Samba_Server: daemon is started
May  5 01:05:25 custom_script: Running /jffs/scripts/wan-event (args: 0 init)
May  5 01:05:25 custom_script: Running /jffs/scripts/wan-event (args: 0 connecting)
May  5 01:05:25 pppd[2603]: pppd 2.4.7 started by admin, uid 0
May  5 01:05:25 (ChkWAN.sh): 2564 ChkWAN scheduled by cron
*/2 * * * * /jffs/scripts/ChkWAN.sh wan nowait #WAN_Check#
May  5 01:05:25 (ChkWAN.sh): 2564 v1.17 WAN connection status monitoring will begin in 10 seconds.....
May  5 01:05:26 : fwver: 3.0.0.4_388.8_4 (sn:S7IG5Q20XXXXXXX /ha:XX:XX:XX:XX:XX:XX )
May  5 01:05:26 rc_service: cfg_server 2517:notify_rc update_nbr
May  5 01:05:26 rc_service: waitting "restart_firewall" via  ...
May  5 01:05:32 BONDING: option disabled
May  5 01:05:32 roamast: ROAMING Start...
May  5 01:05:33 WAN(0)_Connection: Fail to connect with some issues.
May  5 01:05:36 (ChkWAN.sh): 2564 v1.17 Monitoring WAN connection using 3 target PING hosts (0.0.0.0 9.9.9.9 1.1.1.1) (Tries=3)
May  5 01:05:36 (ChkWAN.sh): 2564 Private LAN 0.0.0.0 will be skipped for WAN PING check!
May  5 01:05:39 (ChkWAN.sh): 2564 v1.17 Monitoring WAN connection using PING method to 9.9.9.9 check FAILED
May  5 01:05:40 pppd[2603]: Connected to XX:XX:XX:XX:XX:XX via interface vlan40
May  5 01:05:40 pppd[2603]: Connect: ppp0 <--> vlan40
May  5 01:05:40 pppd[2603]: PAP authentication succeeded
May  5 01:05:40 pppd[2603]: peer from calling number XX:XX:XX:XX:XX:XX authorized
May  5 01:05:40 pppd[2603]: local  IP address 17X.2X6.X4.X2
May  5 01:05:40 pppd[2603]: remote IP address 2XX.X0.2XX.XX9
May  5 01:05:40 pppd[2603]: primary   DNS address 2XX.1XX.128.2
May  5 01:05:40 pppd[2603]: secondary DNS address 2XX.1XX.128.5
May  5 01:05:42 ntpd: Started ntpd
May  5 01:05:42 WAN(0)_Connection: WAN was restored.
Dec 15 21:01:33 ntpd: Initial clock set
Dec 15 21:01:33 rc_service: ntpd_synced 3255:notify_rc restart_diskmon
Dec 15 21:01:33 disk_monitor: Finish
Click to expand...
You seem to be having a few different problems but the cause may be the same - the chkwan script. Either a bad setting or the script is not fully compatible.
 
You must log in or register to reply here.

Similar threads

R
Asus Tuf AX6000 disconnections
Replies
3
Views
114
ronins
R
W
RT-AX86U with latest version 3004.388.8_2 always crash and reboot
2 3
Replies
41
Views
5K
bennor
B
R
Configuring Chk-WAN
Replies
2
Views
789
RRands
R
L
ASUS RT-AX58U - devices kicked-off wifi over 60 times a day
2
Replies
21
Views
999
ColinTaylor
C
Neo-ST
Can't get AX86U to work with bridged router (Link DOWN)
Replies
18
Views
2K
Neo-ST
Neo-ST
Similar threads
Thread starter Title Forum Replies Date
fafot Solved Constant Apple Home random disconnections Asuswrt-Merlin 2
B FYI: AM 386.12 on AC86u - how to decrease # of random reboots Asuswrt-Merlin 4
P GPL firmware 3.0.0.6.102_33340 for RT-AX88U Pro Released Asuswrt-Merlin 4
R Revert ASUS RT-AX86U Pro Back to Stock Firmware Asuswrt-Merlin 1
G RT-AC2900 supported by Merlin firmware? Asuswrt-Merlin 9
inakaya RT-AX86U_PRO_3004_388.8_4 firmware MD5 checksum mismatch Asuswrt-Merlin 4
R Missing ROG version of firmware 388.8 Asuswrt-Merlin 1
D CVSS High 8.1 - CVE-2015-8960 with firmware 3004.388.8_2 Asuswrt-Merlin 6
D L2TP client on ax88U pro running latest merlin firmware how to add device Asuswrt-Merlin 0
P Accessing remotly Server While Using VPN on Asus Router with Merlin Firmware Asuswrt-Merlin 9

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Total: 569 (members: 22, guests: 547)
Top