Viktor Jaep
Part of the Furniture
Can't say I've run across this kind of behavior before. Anything look weird on screen by chance? Any errors or whatnot? I'm going to have you try something. Gimme a few.Haha, that's funny--true, at least the internet complaints have stopped.
So here's the deal, it looks like the script is unable to recover from WAN downtime. It started today at 1930 AST and hasn't yet stopped at 2200 AST:
Thu Sep 22 19:31:19 AST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED
Thu Sep 22 19:31:24 AST 2022 - VPNMON-R2 - WAN Link Detected -- Trying to reconnect/Reset VPN
Thu Sep 22 19:32:28 AST 2022 - VPNMON-R2 - Executing VPN Reset
Thu Sep 22 19:32:32 AST 2022 - VPNMON-R2 - Killed all VPN Client Connections
Thu Sep 22 19:33:32 AST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED
Thu Sep 22 19:33:32 AST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED. VPN RESET TERMINATED.
<SNIP>
Thu Sep 22 21:59:08 AST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED
Thu Sep 22 21:59:08 AST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED. VPN RESET TERMINATED.
Thu Sep 22 21:59:14 AST 2022 - VPNMON-R2 - WAN Link Detected -- Trying to reconnect/Reset VPN
Thu Sep 22 22:00:18 AST 2022 - VPNMON-R2 - Executing VPN Reset
Thu Sep 22 22:00:22 AST 2022 - VPNMON-R2 - Killed all VPN Client Connections
Thu Sep 22 22:01:22 AST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED
Thu Sep 22 22:01:22 AST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED. VPN RESET TERMINATED.
Thu Sep 22 22:01:28 AST 2022 - VPNMON-R2 - WAN Link Detected -- Trying to reconnect/Reset VPN
Thu Sep 22 22:02:33 AST 2022 - VPNMON-R2 - Executing VPN Reset
Thu Sep 22 22:02:37 AST 2022 - VPNMON-R2 - Killed all VPN Client Connections
Thu Sep 22 22:03:37 AST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED
Thu Sep 22 22:03:37 AST 2022 - VPNMON-R2 ----------> ERROR: WAN CONNECTIVITY ISSUE DETECTED. VPN RESET TERMINATED.
Thu Sep 22 22:03:43 AST 2022 - VPNMON-R2 - WAN Link Detected -- Trying to reconnect/Reset VPN
Thu Sep 22 22:04:47 AST 2022 - VPNMON-R2 - Executing VPN Reset
Thu Sep 22 22:04:51 AST 2022 - VPNMON-R2 - Killed all VPN Client Connections
<SNIP>
Thu Sep 22 22:08:42 AST 2022 - VPNMON-R2 - Executing VPN Reset
Thu Sep 22 22:08:46 AST 2022 - VPNMON-R2 - Killed all VPN Client Connections
Thu Sep 22 22:09:17 AST 2022 - VPNMON-R2 - Updated Skynet Whitelist
Thu Sep 22 22:09:25 AST 2022 - VPNMON-R2 - Refreshed VPN Slots 1 - 5 from 2244 SuperRandom NordVPN Server Locations
Thu Sep 22 22:09:26 AST 2022 - VPNMON-R2 - Randomly selected VPN3 Client ON
Thu Sep 22 22:09:31 AST 2022 - VPNMON-R2 - VPN Reset Finished
Thu Sep 22 22:09:34 AST 2022 - VPNMON-R2 - Resuming normal operations
Thu Sep 22 22:10:03 AST 2022 - VPNMON-R2 - API call made to update WAN0 city to New York
Thu Sep 22 22:10:25 AST 2022 - VPNMON-R2 - API call made to update VPN city to New York
I got busy and wasn't paying attention until just before bedtime :/ Fixed it by killing the screen session and restarting the script through amtm. If it were a ping-related issue it wouldn't work now either after two and half hours. It's something else, the script is somehow unable to detect when the WAN comes back up when it goes down in the same session. Kill the session and restart the script and all goes well. For the heck of it, I'll change the ping to 1000 and see what happens next.