JohnSmith
Senior Member
Any issues for the following message on an RT-AX88U with latest RMerlin version?
Just switched over to V1.5.7-beta1c, wish I would of had it for Friday August 26th with debug logs on (only notice logs), as I had my ISP01 go down for real, and with V1.5.6 Final, it switched automatically to ISP02, and all services worked great.
ISP01(1GB Symmetrical) was down for almost 8 hours, but ISP02(650DL/100UL) just kept chugging along. When ISP01 finally came back, it did switch back over to ISP01 from ISP02, but the weird thing is ISP02 was then considered in a down state for almost 8 hours before my RT-AX88U sent out this message in the V1.5.6 Final notice logs:
Otherwise it failed over like it should and failed back like it should. Unfortunately no WFH was going on at the time, streaming, gaming, or VPN connections, to see any real time disconnects/reconnects.
Code:
Aug 27 16:44:00 wan-failover.sh: System Check - ***386.8 is not supported, issues may occur from running this version***Just switched over to V1.5.7-beta1c, wish I would of had it for Friday August 26th with debug logs on (only notice logs), as I had my ISP01 go down for real, and with V1.5.6 Final, it switched automatically to ISP02, and all services worked great.
ISP01(1GB Symmetrical) was down for almost 8 hours, but ISP02(650DL/100UL) just kept chugging along. When ISP01 finally came back, it did switch back over to ISP01 from ISP02, but the weird thing is ISP02 was then considered in a down state for almost 8 hours before my RT-AX88U sent out this message in the V1.5.6 Final notice logs:
Code:
Aug 27 03:12:42 kernel: CPU: 0 PID: 19540 Comm: wan-failover.sh Tainted: P O 4.1.51 #2
Aug 27 03:12:42 kernel: Hardware name: Broadcom-v8A (DT)
Aug 27 03:12:42 kernel: task: ffffffc02c4f4100 ti: ffffffc0277ec000 task.ti: ffffffc0277ec000
Aug 27 03:12:42 kernel: PC is at 0x3b4e0
Aug 27 03:12:42 kernel: LR is at 0x391f8
Aug 27 03:12:42 kernel: pc : [<000000000003b4e0>] lr : [<00000000000391f8>] pstate: 20010010
Aug 27 03:12:42 kernel: sp : 00000000ffbdc018
Aug 27 03:12:42 kernel: x12: 00000000ffbdc0a0
Aug 27 03:12:42 kernel: x11: 000000000051b4f4 x10: 0000000000000001
Aug 27 03:12:42 kernel: x9 : 00000000004eef44 x8 : 00000000ffffffff
Aug 27 03:12:42 kernel: x7 : 00000000004b9150 x6 : 0000000000000000
Aug 27 03:12:42 kernel: x5 : 00000000004b9540 x4 : 0000000000000002
Aug 27 03:12:42 kernel: x3 : 000000000003b4e0 x2 : 0000000000000000
Aug 27 03:12:42 kernel: x1 : 0000000000000002 x0 : 00000000004f3e14
Aug 27 03:12:42 ovpn-server1[21236]: event_wait : Interrupted system call (code=4)
Aug 27 03:12:42 ovpn-server1[21236]: PLUGIN AUTH-PAM: Error signaling background process to exit: Connection refused (errno=111)
Aug 27 03:12:42 YazFi: Firewall restarted - sleeping 10s before running YazFi
Aug 27 03:12:42 FlexQoS: /jffs/addons/flexqos/flexqos.sh (pid=31711) called in unattended mode with 1 args: -start
Aug 27 03:12:42 ovpn-server1[31884]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Aug 27 03:12:42 FlexQoS: iptables rules already present
Aug 27 03:12:43 FlexQoS: No TC modifications necessary
Aug 27 03:12:52 YazFi: YazFi v4.4.2 starting up
Aug 27 03:12:53 YazFi: wl0.1 (SSID: xxxxxxx) - sending all interface internet traffic over WAN interface
Aug 27 03:12:55 YazFi: wl0.2 (SSID: xxxxx) - sending all interface internet traffic over WAN interface
Aug 27 03:12:59 YazFi: Forcing YazFi Guest WiFi clients to reauthenticate
Aug 27 03:13:00 wan-failover.sh: System Check - ***386.8 is not supported, issues may occur from running this version***
Aug 27 03:13:00 wan-failover.sh: System Check - ***386.8 is not supported, issues may occur from running this version***
Aug 27 03:13:00 wan-failover.sh: WAN Status - Added default route for wan0 Routing Table via X.X.X.X dev eth0
Aug 27 03:13:00 wan-failover.sh: WAN Status - Added IP Rule for 8.8.8.8 to monitor wan0
Aug 27 03:13:04 wan-failover.sh: WAN Status - Added default route for wan1 Routing Table via X.X.X.X dev eth4
Aug 27 03:13:05 wan-failover.sh: WAN Status - Added IP Rule for 8.8.4.4 to monitor wan1
Aug 27 03:13:15 wan-failover.sh: WAN Status - Added IP Rule for 8.8.4.4 to monitor wan1 without specifying Outbound Interface
Aug 27 03:13:15 YazFi: YazFi v4.4.2 completed successfully
Aug 27 03:13:19 wan-failover.sh: WAN Status - ***Warning*** Compatibility issues with 8.8.4.4 may occur without specifying Outbound Interface
Aug 27 03:13:19 wan-failover.sh: DNS Switch - Removed wan1 DNS1 Server: X.X.X.X
Aug 27 03:13:19 wan-failover.sh: DNS Switch - Removed wan1 DNS2 Server: X.X.X.X
Aug 27 03:13:19 wan-failover.sh: WAN0 Failover Monitor - Monitoring wan0 via 8.8.8.8 for Failure
Aug 27 03:13:19 wan-failover.sh: WAN0 Failover Monitor - Monitoring wan1 via 8.8.4.4 for FailureOtherwise it failed over like it should and failed back like it should. Unfortunately no WFH was going on at the time, streaming, gaming, or VPN connections, to see any real time disconnects/reconnects.
Last edited:
