Some more info in this issue: None of the periodic threads execute when this happens, for example the suspended count of fib-walk remains at 316497 for 180 seconds. Same for other threads too.
Please see the output of following command to get the full picture. date; vppctl sh run | grep -E 'neig|walk' ; sleep 61 ; date ; vppctl sh run | grep -E 'neig|walk' ; sleep 61 ; date ; vppctl sh run | grep -E 'neig|walk' Thu Apr 15 13:17:04 IST 2021 fib-walk any wait 0 0 316497 6.82e3 0.00 flowprobe-walker interrupt wa 2516563610 0 0 5.23e2 0.00 ip-neighbor-scan-process any wait 0 0 1369413 1.89e4 0.00 ip4-reassembly-expire-walk any wait 0 0 63303 4.87e3 0.00 ip6-icmp-neighbor-discovery-ev any wait 0 0 280067 3.61e3 0.00 ip6-reassembly-expire-walk any wait 0 0 63303 4.11e3 0.00 nat-det-expire-walk any wait 0 0 63303 1.16e8 0.00 nat64-expire-walk event wait 0 0 1 8.47e3 0.00 Thu Apr 15 13:18:07 IST 2021 fib-walk any wait 0 0 316497 6.82e3 0.00 flowprobe-walker interrupt wa 2516563610 0 0 5.23e2 0.00 ip-neighbor-scan-process any wait 0 0 1369413 1.89e4 0.00 ip4-reassembly-expire-walk any wait 0 0 63303 4.87e3 0.00 ip6-icmp-neighbor-discovery-ev any wait 0 0 280067 3.61e3 0.00 ip6-reassembly-expire-walk any wait 0 0 63303 4.11e3 0.00 nat-det-expire-walk any wait 0 0 63303 1.16e8 0.00 nat64-expire-walk event wait 0 0 1 8.47e3 0.00 Thu Apr 15 13:19:09 IST 2021 fib-walk any wait 0 0 316497 6.82e3 0.00 flowprobe-walker interrupt wa 2516563610 0 0 5.23e2 0.00 ip-neighbor-scan-process any wait 0 0 1369413 1.89e4 0.00 ip4-reassembly-expire-walk any wait 0 0 63303 4.87e3 0.00 ip6-icmp-neighbor-discovery-ev any wait 0 0 280067 3.61e3 0.00 ip6-reassembly-expire-walk any wait 0 0 63303 4.11e3 0.00 nat-det-expire-walk any wait 0 0 63303 1.16e8 0.00 nat64-expire-walk event wait 0 0 1 8.47e3 0.00 Checking to understand why this happens and if some thing could be done to restart the threads? X. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Monday, March 29, 2021 10:47 AM, Xuo Guoto via lists.fd.io <xuoguoto=protonmail....@lists.fd.io> wrote: > Hello all, > > While running vpp 19.01(on ubuntu 18.04), I have observed that occasionally > nat-det-expire-walk which is supposed to run every 10 sec, does not run. This > causes the expired sessions to pile up. > > I am checking it by running the following command: > > vppctl sh run | grep -E 'Name|nat-det-expire-walk' ; sleep 10 ; vppctl sh run > | grep nat-det-expire-walk > Name State Calls Vectors Suspends Clocks Vectors/Call Perf Ticks > nat-det-expire-walk any wait 0 0 102683 1.15e8 0.00 > nat-det-expire-walk any wait 0 0 102683 1.15e8 0.00 > > Usually, Suspends count will go up, as the nat-det-expire-walk runs and > suspends itself, but if it stops running, this count will not increase. > > I understand this version is no longer supported, and while upgrading might > solve this issue, that's immediately not an option, but certainly on the > cards. > > Just checking if this is a known issue and if there is any fix. If not is > there any means to manually restart or run this job? Any debug tip or command > to understand why its not running is also most welcome and I can do it when > it happens next. > > X.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#19207): https://lists.fd.io/g/vpp-dev/message/19207 Mute This Topic: https://lists.fd.io/mt/81689754/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
