Hello Dave,
There was needed to add third crc set with affected ip api crc values and
without change of tap api crc values...
Anyway, there is ready CSIT patch [0] that covers ip and tap api changes
but it cannot be merged until vpp tap api change [1] is merged.
After merge of these two patches
Hello,
Both patches mentioned below have been merged. Please, rebase your pending vpp
patches.
Let us know in case of any issue.
Thanks,
Jan
From: vpp-dev@lists.fd.io On Behalf Of Jan Gelety via
Lists.Fd.Io
Sent: Wednesday, December 11, 2019 10:33 AM
To: Dave Wallace ; Dave Barach (dbarach)
Make sure to check e.g. /var/log/syslog. Clib_warnings(...) are sent to syslog,
and end up in the system log. Search for “vnet”. Example:
Dec 11 07:37:56 vpp-n1 vnet[2977]: icmp6_router_solicitation:1811: Prefix
[REDACTED] valid 295722 preferred 295722
FWIW... Dave
From: vpp-dev@lists.fd.io O
Coverity run failed today.
Current number of outstanding issues are 2
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 (#14865): ht
Coverity run failed today.
Current number of outstanding issues are 2
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 (#14866): ht
Hi All & Nathan,
Thanks for your input.
I followed your steps, build release VPP with my plugin change and make
production image. In production image, I faced same issue like my sample.so
plugin is not loaded when launch the vpp.
Again, I followed development image steps, build release VPP with m
> Unfortunately when I pushed the patch [2], it failed to pass the crc check
Added explanations to gerrit: [3], [4].
Vratko.
[3]
https://gerrit.fd.io/r/c/csit/+/23926/1/resources/api/vpp/supported_crcs.yaml#34
[4]
https://gerrit.fd.io/r/c/csit/+/23926/1/resources/api/vpp/supported_crcs.yaml#27
Thanks Dave for the response.
But I don’t see the syslog getting generated under /var/log/.
I am running VPP process as below.
vpp -c /etc/vpp.conf
And I have the unix section of vpp.conf file as below.
unix {
nodaemon
log /var/log/vpp.log
full-coredump
gid vpp
cli-listen lo
Did you look in the default system logfile /var/log/syslog? That’s the first
place I would look for clib_warning output.
The unix { log } stanza concerns logging of debug CLI commands, not
clib_warnings...
Dave
From: Gudimetla, Leela Sankar
Sent: Wednesday, December 11, 2019 1:25 PM
To:
Dave, in my environment, VPP is running as a separate process in a container.
I see the below 3 lines in /var/log/messages.
vnet 1356 - - dpdk_ipsec_process:1026: not enough DPDK crypto resources,
default to OpenSSL
vnet 1356 - - received SIGTERM, exiting...
vnet 1356 - - unix_signal_handler:1
Hi Hanlin,
Thanks to Dave, we can now have per thread binary api connections to vpp. I’ve
updated the socket client and vcl to leverage this so, after [1] we have per
vcl worker thread binary api sockets that are used to exchange fds.
Let me know if you’re still hitting the issue.
Regards,
How about starting vpp under gdb and trying to debug the issue?
To level-set: community support for 18.07 ended a while ago. You’d probably do
yourself a favor by switching to 19.08 which we will support for a full year.
FWIW... Dave
From: Gudimetla, Leela Sankar
Sent: Wednesday, December 11,
That's great! I'll apply and check it soon.
Thanks & Regards,Hanlin
13 matches
Mail list logo