Hi Hanlin,
Just to make sure, are you running master or some older VPP?
Regarding the issue you could be hitting lower, here’s [1] a patch that I have
not yet pushed for merging because it leads to api changes for applications
that directly use the session layer application interface instead
Hi Andrew,
Thanks, that looks promising. The issue
https://jira.fd.io/browse/VPP-1734 that the fix refers to seems like it
could be the same issue we are seeing.
We have just restarted vpp with the fix, it will be interesting to see
if it helps. Thanks again for your help!
/ Elias
On Fri,
Coverity run failed today.
Current number of outstanding issues are 5
Newly detected: 0
Eliminated: 0
More details can be found at
https://scan.coverity.com/projects/fd-io-vpp/view_defects
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#14607):
See
https://fd.io/docs/vpp/master/troubleshooting/reportingissues/reportingissues.html,
specifically:
“Before you press the Jira button to create a bug report - or email
vpp-dev@lists.fd.io - please ask yourself whether there’s enough information
for someone else to understand and to
Hi ,
We are seeing crash in vlib_worker_thread_barrier_sync_int() function as soon
as we send a CLI command to VPP.
We are sending CLI command to VPP via a script, which may not be waiting enough
for VPP initialization to settle.
I see that the crash is happening in the following piece of
Hi Elias,
Could you give a shot running a build with
https://gerrit.fd.io/r/#/c/vpp/+/23461/ in ?
I cherry-picked it from master today but it is not in 19.08 branch yet.
--a
> On 15 Nov 2019, at 11:05, Elias Rudberg wrote:
>
> We are using VPP 19.08 for NAT (nat44) and are struggling with
hi ALL,I accidentally got following crash stack when I used VCL with hoststack and memfd. But corresponding invalid rx_fifo address (0x2f42e2480) is valid in VPP process and also can be found in /proc/map. That is, shared memfd segment memory is not consistent between hoststack
We are using VPP 19.08 for NAT (nat44) and are struggling with the
following problem: it first works seemingly fine for a while, like
several days or weeks, but then suddenly VPP stops forwarding traffic.
Even ping to the "outside" IP address fails.
The VPP process is still running so we try to
