What's new

WAN Dropout with errors in the system log

  • 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!

Harold_Boom

New Around Here
Hi all,

Since upgrading my GT-AX11000 to Merlin 386.3 I have been getting random WAN dropouts (router is bridged to a VDSL modem) and it always has the same message in the logs. The modem never loses sync however the WAN light on the AX11000 will go red for a few minutes and then it will fix itself. It does this a few times a day and I don't believe this was happening with 386.2.

Has anyone else had this problem or can interpret the log? Thanks

Aug 12 06:51:49 wlceventd: wlceventd_proc_event(556): eth6: Assoc 4C:A1:61:04:6A:93, status: Successful (0), rssi:0
Aug 12 07:02:05 kernel: ^[[0;33;41m[ERROR pktrunner] runnerL2Ucast_refresh_pathstat,301: runnerL2Ucast_refresh_pathstat: Could not get pathIdx<4> stats, rc -5^[[0m
Aug 12 07:02:05 kernel: ^[[0;33;41m[ERROR pktrunner] runnerRefreshPathStat,336: Could not get pathIdx<4> stats, rc -5^[[0m
Aug 12 07:02:05 kernel: ^[[0;33;41m[ERROR pktrunner] runnerL2Ucast_refresh_pathstat,301: runnerL2Ucast_refresh_pathstat: Could not get pathIdx<3> stats, rc -5^[[0m
Aug 12 07:02:05 kernel: ^[[0;33;41m[ERROR pktrunner] runnerRefreshPathStat,336: Could not get pathIdx<3> stats, rc -5^[[0m
Aug 12 07:02:05 kernel: ^[[0;33;41m[ERROR pktrunner] runnerL2Ucast_refresh_pathstat,301: runnerL2Ucast_refresh_pathstat: Could not get pathIdx<8> stats, rc -5^[[0m
Aug 12 07:02:05 kernel: ^[[0;33;41m[ERROR pktrunner] runnerRefreshPathStat,336: Could not get pathIdx<8> stats, rc -5^[[0m
Aug 12 07:02:05 kernel: ^[[0;33;41m[ERROR pktrunner] runnerL2Ucast_refresh_pathstat,301: runnerL2Ucast_refresh_pathstat: Could not get pathIdx<13> stats, rc -5^[[0m
Aug 12 07:02:05 kernel: ^[[0;33;41m[ERROR pktrunner] runnerRefreshPathStat,336: Could not get pathIdx<13> stats, rc -5^[[0m
Aug 12 07:02:06 kernel: ^[[0;33;41m[ERROR pktrunner] runnerL2Ucast_refresh_pathstat,301: runnerL2Ucast_refresh_pathstat: Could not get pathIdx<2> stats, rc -5^[[0m
Aug 12 07:02:06 kernel: ^[[0;33;41m[ERROR pktrunner] runnerRefreshPathStat,336: Could not get pathIdx<2> stats, rc -5^[[0m
Aug 12 07:02:06 kernel: ^[[0;33;41m[ERROR pktrunner] runnerL2Ucast_refresh_pathstat,301: runnerL2Ucast_refresh_pathstat: Could not get pathIdx<7> stats, rc -5^[[0m
Aug 12 07:02:06 kernel: ^[[0;33;41m[ERROR pktrunner] runnerRefreshPathStat,336: Could not get pathIdx<7> stats, rc -5^[[0m
Aug 12 07:02:06 kernel: ^[[0;33;41m[ERROR pktrunner] runnerL2Ucast_refresh_pathstat,301: runnerL2Ucast_refresh_pathstat: Could not get pathIdx<12> stats, rc -5^[[0m
Aug 12 07:02:06 kernel: ^[[0;33;41m[ERROR pktrunner] runnerRefreshPathStat,336: Could not get pathIdx<12> stats, rc -5^[[0m
Aug 12 07:02:06 kernel: ^[[0;33;41m[ERROR pktrunner] runnerL2Ucast_refresh_pathstat,301: runnerL2Ucast_refresh_pathstat: Could not get pathIdx<17> stats, rc -5^[[0m
Aug 12 07:02:06 kernel: ^[[0;33;41m[ERROR pktrunner] runnerRefreshPathStat,336: Could not get pathIdx<17> stats, rc -5^[[0m
Aug 12 07:02:06 kernel: ^[[0;33;41m[ERROR pktrunner] runnerL2Ucast_refresh_pathstat,301: runnerL2Ucast_refresh_pathstat: Could not get pathIdx<11> stats, rc -5^[[0m
Aug 12 07:02:06 kernel: ^[[0;33;41m[ERROR pktrunner] runnerRefreshPathStat,336: Could not get pathIdx<11> stats, rc -5^[[0m
Aug 12 07:02:06 kernel: ^[[0;33;41m[ERROR pktrunner] runnerL2Ucast_refresh_pathstat,301: runnerL2Ucast_refresh_pathstat: Could not get pathIdx<1> stats, rc -5^[[0m
Aug 12 07:02:06 kernel: ^[[0;33;41m[ERROR pktrunner] runnerRefreshPathStat,336: Could not get pathIdx<1> stats, rc -5^[[0m
Aug 12 07:02:06 kernel: ^[[0;33;41m[ERROR pktrunner] runnerL2Ucast_refresh_pathstat,301: runnerL2Ucast_refresh_pathstat: Could not get pathIdx<5> stats, rc -5^[[0m
 
Did you do a "dirty" upgrade? Dirty upgrades are always a roll of the dice. I always recommend upgrading, resetting to defaults, and manually reapplying your changes.
 
Did you do a "dirty" upgrade? Dirty upgrades are always a roll of the dice. I always recommend upgrading, resetting to defaults, and manually reapplying your changes.
I did yeah, could that cause this error? Its a real pain in the neck for me to redo settings, VPNs etc
 

Latest threads

Sign Up For SNBForums Daily Digest

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