Re: [vpp-dev] Error during startup

2018-03-11 Thread Florin Coras 
Did you rebuild debs and reinstalled them? VPP looks to me to be post 18.01, 
given those errors. I’d do the following:

- switch to 18.01 branch
- make sure you have everything backed up
- git clean -fdx
- make bootstrap
- make pkg-deb
- install debs

Try everything again.

Florin

> On Mar 11, 2018, at 8:26 AM, Shashi Kant Singh <sksi...@altiostar.com> wrote:
> 
> I did a clean, switched to branch 18:01, and ran build command. It did move 
> ahead but does not work on running.
>
> When I run the following. I get:
>
> ON THE VPP SERVER:
> -
> DBGvpp# 0: application_verify_cfg:245: memfd seg: vpp's event qs IN binary 
> api svm region
> 0: vnet_application_attach: app init: -108
>
> DBGvpp# show interface
>
>
> ON RUNNING THE TEST SERVER
> ---
> build-tool-native/  build-vpp_debug-native/
> [root@vbbubng6-shashi-2 vpp]# 
> ./build-root/build-vpp_debug-native/vpp/vcl_test_server 5678
> vppcom_cfg_heapsize:1624: VCL<12013>: using default heapsize 268435456 
> (0x1000)
> vppcom_cfg_heapsize:1770: VCL<12013>: allocated VCL heap = 0x7f33a8115000, 
> size 268435456 (0x1000)
> vppcom_cfg_read:1790: VCL<12013>: using default configuration.
> vppcom_connect_to_vpp:512: VCL<12013>: app (vcl_test_server) connecting to 
> VPP api (/vpe-api)...
> vppcom_connect_to_vpp:528: VCL<12013>: app (vcl_test_server) is connected to 
> VPP!
> vppcom_app_create:2284: VCL<12013>: sending session enable
> vppcom_app_create:2295: VCL<12013>: sending app attach
> vl_api_application_attach_reply_t_handler:817: VCL<12013>: attach failed: 
> Unsupported application config (-108)
> ^C
> [root@vbbubng6-shashi-2 vpp]#
>
>
> This works fine for my old release but gives above error for 18:01
> When I try to ping, the TEST CLIENT machine from VPP SERVER and vice versa. 
> This also does not work now
>
> Regards
> Shashi
>
>
> From: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io> 
> [mailto:vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io>] On Behalf Of Dave 
> Barach
> Sent: 08 March 2018 18:21
> To: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io>
> Cc: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io>
> Subject: Re: [vpp-dev] Error during startup
>
> +1. Please be careful. This is a cockpit error.
>
> From: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io> <vpp-dev@lists.fd.io 
> <mailto:vpp-dev@lists.fd.io>> On Behalf Of Florin Coras
> Sent: Thursday, March 8, 2018 1:09 AM
> To: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io>
> Cc: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io>
> Subject: Re: [vpp-dev] Error during startup
>
> Hi Shashi, 
>
> This can’t possibly be part of 17.10 and 18.01 since it was only merged this 
> week on master. Probably you need to clean your repo, rebuild and reinstall 
> debs. 
>
> Florin
>
> 
> On Mar 7, 2018, at 7:44 PM, Shashi Kant Singh <sksi...@altiostar.com 
> <mailto:sksi...@altiostar.com>> wrote:
>
> Hi
>
> When I try to start vpp with release 17:10 and 18:01,. I am getting following 
> TLS error
>
> What could be the issue?
>
> Regards
> Shashi
> PS: This worked fine for previous releases.
>
> #  make run-release STARTUP_CONF=../startup.conf
> vlib_plugin_early_init:356: plugin path 
> /bng5/shashi-2/vpp2/vpp/build-root/install-vpp-native/sample-plugin/lib64/vpp_plugins:/bng5/shashi-2/vpp2/vpp/build-root/install-vpp-native/vpp/lib64/vpp_plugins
> load_one_plugin:184: Loaded plugin: acl_plugin.so (Access Control Lists)
> load_one_plugin:184: Loaded plugin: dpdk_plugin.so (Data Plane Development 
> Kit (DPDK))
> load_one_plugin:184: Loaded plugin: flowprobe_plugin.so (Flow per Packet)
> load_one_plugin:184: Loaded plugin: gbp_plugin.so (Group Based Policy)
> load_one_plugin:184: Loaded plugin: gtpu_plugin.so (GTPv1-U)
> load_one_plugin:184: Loaded plugin: ila_plugin.so (Identifier-locator 
> addressing for IPv6)
> load_one_plugin:184: Loaded plugin: ioam_plugin.so (Inbound OAM)
> load_one_plugin:114: Plugin disabled (default): ixge_plugin.so
> load_one_plugin:184: Loaded plugin: kubeproxy_plugin.so (kube-proxy data 
> plane)
> load_one_plugin:184: Loaded plugin: l2e_plugin.so (L2 Emulation)
> load_one_plugin:184: Loaded plugin: lb_plugin.so (Load Balancer)
> load_one_plugin:184: Loaded plugin: libsixrd_plugin.so (IPv6 Rapid Deployment 
> on IPv4 Infrastructure (RFC5969))
> load_one_plugin:184: Loaded plugin: memif_plugin.so (Packet Memory Interface 
> (experimetal))
> load_one_plugin:184: Loaded plugin: nat_plugin.so (Network Address 
> Translation)
> load_one_plugin:184: Loaded plugin: pppoe

Re: [vpp-dev] Error during startup

2018-03-11 Thread Shashi Kant Singh 
I did a clean, switched to branch 18:01, and ran build command. It did move 
ahead but does not work on running.

When I run the following. I get:

ON THE VPP SERVER:
-
DBGvpp# 0: application_verify_cfg:245: memfd seg: vpp's event qs IN binary api 
svm region
0: vnet_application_attach: app init: -108

DBGvpp# show interface


ON RUNNING THE TEST SERVER
---
build-tool-native/  build-vpp_debug-native/
[root@vbbubng6-shashi-2 vpp]# 
./build-root/build-vpp_debug-native/vpp/vcl_test_server 5678
vppcom_cfg_heapsize:1624: VCL<12013>: using default heapsize 268435456 
(0x1000)
vppcom_cfg_heapsize:1770: VCL<12013>: allocated VCL heap = 0x7f33a8115000, size 
268435456 (0x1000)
vppcom_cfg_read:1790: VCL<12013>: using default configuration.
vppcom_connect_to_vpp:512: VCL<12013>: app (vcl_test_server) connecting to VPP 
api (/vpe-api)...
vppcom_connect_to_vpp:528: VCL<12013>: app (vcl_test_server) is connected to 
VPP!
vppcom_app_create:2284: VCL<12013>: sending session enable
vppcom_app_create:2295: VCL<12013>: sending app attach
vl_api_application_attach_reply_t_handler:817: VCL<12013>: attach failed: 
Unsupported application config (-108)
^C
[root@vbbubng6-shashi-2 vpp]#


This works fine for my old release but gives above error for 18:01
When I try to ping, the TEST CLIENT machine from VPP SERVER and vice versa. 
This also does not work now

Regards
Shashi


From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Dave Barach
Sent: 08 March 2018 18:21
To: vpp-dev@lists.fd.io
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Error during startup

+1. Please be careful. This is a cockpit error.

From: vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io> 
<vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>> On Behalf Of Florin Coras
Sent: Thursday, March 8, 2018 1:09 AM
To: vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>
Cc: vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>
Subject: Re: [vpp-dev] Error during startup

Hi Shashi,

This can’t possibly be part of 17.10 and 18.01 since it was only merged this 
week on master. Probably you need to clean your repo, rebuild and reinstall 
debs.

Florin

On Mar 7, 2018, at 7:44 PM, Shashi Kant Singh 
<sksi...@altiostar.com<mailto:sksi...@altiostar.com>> wrote:

Hi

When I try to start vpp with release 17:10 and 18:01,. I am getting following 
TLS error

What could be the issue?

Regards
Shashi
PS: This worked fine for previous releases.

#  make run-release STARTUP_CONF=../startup.conf
vlib_plugin_early_init:356: plugin path 
/bng5/shashi-2/vpp2/vpp/build-root/install-vpp-native/sample-plugin/lib64/vpp_plugins:/bng5/shashi-2/vpp2/vpp/build-root/install-vpp-native/vpp/lib64/vpp_plugins
load_one_plugin:184: Loaded plugin: acl_plugin.so (Access Control Lists)
load_one_plugin:184: Loaded plugin: dpdk_plugin.so (Data Plane Development Kit 
(DPDK))
load_one_plugin:184: Loaded plugin: flowprobe_plugin.so (Flow per Packet)
load_one_plugin:184: Loaded plugin: gbp_plugin.so (Group Based Policy)
load_one_plugin:184: Loaded plugin: gtpu_plugin.so (GTPv1-U)
load_one_plugin:184: Loaded plugin: ila_plugin.so (Identifier-locator 
addressing for IPv6)
load_one_plugin:184: Loaded plugin: ioam_plugin.so (Inbound OAM)
load_one_plugin:114: Plugin disabled (default): ixge_plugin.so
load_one_plugin:184: Loaded plugin: kubeproxy_plugin.so (kube-proxy data plane)
load_one_plugin:184: Loaded plugin: l2e_plugin.so (L2 Emulation)
load_one_plugin:184: Loaded plugin: lb_plugin.so (Load Balancer)
load_one_plugin:184: Loaded plugin: libsixrd_plugin.so (IPv6 Rapid Deployment 
on IPv4 Infrastructure (RFC5969))
load_one_plugin:184: Loaded plugin: memif_plugin.so (Packet Memory Interface 
(experimetal))
load_one_plugin:184: Loaded plugin: nat_plugin.so (Network Address Translation)
load_one_plugin:184: Loaded plugin: pppoe_plugin.so (PPPoE)
load_one_plugin:184: Loaded plugin: sample_plugin.so (Sample of VPP Plugin)
load_one_plugin:184: Loaded plugin: srv6ad_plugin.so (Dynamic SRv6 proxy)
load_one_plugin:184: Loaded plugin: srv6am_plugin.so (Masquerading SRv6 proxy)
load_one_plugin:184: Loaded plugin: srv6as_plugin.so (Static SRv6 proxy)
load_one_plugin:184: Loaded plugin: stn_plugin.so (VPP Steals the NIC for 
Container integration)
tls_init_ca_chain:1125: Could not initialize TLS CA certificates
tls_init:1168: failed to initialize TLS CA chain
tls_init: failed to initalize TLS CA chain

Re: [vpp-dev] Error during startup

2018-03-08 Thread Dave Barach 
+1. Please be careful. This is a cockpit error.

From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of Florin Coras
Sent: Thursday, March 8, 2018 1:09 AM
To: vpp-dev@lists.fd.io
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Error during startup

Hi Shashi,

This can’t possibly be part of 17.10 and 18.01 since it was only merged this 
week on master. Probably you need to clean your repo, rebuild and reinstall 
debs.

Florin


On Mar 7, 2018, at 7:44 PM, Shashi Kant Singh 
<sksi...@altiostar.com<mailto:sksi...@altiostar.com>> wrote:

Hi

When I try to start vpp with release 17:10 and 18:01,. I am getting following 
TLS error

What could be the issue?

Regards
Shashi
PS: This worked fine for previous releases.

#  make run-release STARTUP_CONF=../startup.conf
vlib_plugin_early_init:356: plugin path 
/bng5/shashi-2/vpp2/vpp/build-root/install-vpp-native/sample-plugin/lib64/vpp_plugins:/bng5/shashi-2/vpp2/vpp/build-root/install-vpp-native/vpp/lib64/vpp_plugins
load_one_plugin:184: Loaded plugin: acl_plugin.so (Access Control Lists)
load_one_plugin:184: Loaded plugin: dpdk_plugin.so (Data Plane Development Kit 
(DPDK))
load_one_plugin:184: Loaded plugin: flowprobe_plugin.so (Flow per Packet)
load_one_plugin:184: Loaded plugin: gbp_plugin.so (Group Based Policy)
load_one_plugin:184: Loaded plugin: gtpu_plugin.so (GTPv1-U)
load_one_plugin:184: Loaded plugin: ila_plugin.so (Identifier-locator 
addressing for IPv6)
load_one_plugin:184: Loaded plugin: ioam_plugin.so (Inbound OAM)
load_one_plugin:114: Plugin disabled (default): ixge_plugin.so
load_one_plugin:184: Loaded plugin: kubeproxy_plugin.so (kube-proxy data plane)
load_one_plugin:184: Loaded plugin: l2e_plugin.so (L2 Emulation)
load_one_plugin:184: Loaded plugin: lb_plugin.so (Load Balancer)
load_one_plugin:184: Loaded plugin: libsixrd_plugin.so (IPv6 Rapid Deployment 
on IPv4 Infrastructure (RFC5969))
load_one_plugin:184: Loaded plugin: memif_plugin.so (Packet Memory Interface 
(experimetal))
load_one_plugin:184: Loaded plugin: nat_plugin.so (Network Address Translation)
load_one_plugin:184: Loaded plugin: pppoe_plugin.so (PPPoE)
load_one_plugin:184: Loaded plugin: sample_plugin.so (Sample of VPP Plugin)
load_one_plugin:184: Loaded plugin: srv6ad_plugin.so (Dynamic SRv6 proxy)
load_one_plugin:184: Loaded plugin: srv6am_plugin.so (Masquerading SRv6 proxy)
load_one_plugin:184: Loaded plugin: srv6as_plugin.so (Static SRv6 proxy)
load_one_plugin:184: Loaded plugin: stn_plugin.so (VPP Steals the NIC for 
Container integration)
tls_init_ca_chain:1125: Could not initialize TLS CA certificates
tls_init:1168: failed to initialize TLS CA chain
tls_init: failed to initalize TLS CA chain

Re: [vpp-dev] Error during startup

2018-03-07 Thread Florin Coras 
Hi Shashi, 

This can’t possibly be part of 17.10 and 18.01 since it was only merged this 
week on master. Probably you need to clean your repo, rebuild and reinstall 
debs. 

Florin

> On Mar 7, 2018, at 7:44 PM, Shashi Kant Singh  wrote:
> 
> Hi
>
> When I try to start vpp with release 17:10 and 18:01,. I am getting following 
> TLS error
>
> What could be the issue?
>
> Regards
> Shashi
> PS: This worked fine for previous releases.
>
> #  make run-release STARTUP_CONF=../startup.conf
> vlib_plugin_early_init:356: plugin path 
> /bng5/shashi-2/vpp2/vpp/build-root/install-vpp-native/sample-plugin/lib64/vpp_plugins:/bng5/shashi-2/vpp2/vpp/build-root/install-vpp-native/vpp/lib64/vpp_plugins
> load_one_plugin:184: Loaded plugin: acl_plugin.so (Access Control Lists)
> load_one_plugin:184: Loaded plugin: dpdk_plugin.so (Data Plane Development 
> Kit (DPDK))
> load_one_plugin:184: Loaded plugin: flowprobe_plugin.so (Flow per Packet)
> load_one_plugin:184: Loaded plugin: gbp_plugin.so (Group Based Policy)
> load_one_plugin:184: Loaded plugin: gtpu_plugin.so (GTPv1-U)
> load_one_plugin:184: Loaded plugin: ila_plugin.so (Identifier-locator 
> addressing for IPv6)
> load_one_plugin:184: Loaded plugin: ioam_plugin.so (Inbound OAM)
> load_one_plugin:114: Plugin disabled (default): ixge_plugin.so
> load_one_plugin:184: Loaded plugin: kubeproxy_plugin.so (kube-proxy data 
> plane)
> load_one_plugin:184: Loaded plugin: l2e_plugin.so (L2 Emulation)
> load_one_plugin:184: Loaded plugin: lb_plugin.so (Load Balancer)
> load_one_plugin:184: Loaded plugin: libsixrd_plugin.so (IPv6 Rapid Deployment 
> on IPv4 Infrastructure (RFC5969))
> load_one_plugin:184: Loaded plugin: memif_plugin.so (Packet Memory Interface 
> (experimetal))
> load_one_plugin:184: Loaded plugin: nat_plugin.so (Network Address 
> Translation)
> load_one_plugin:184: Loaded plugin: pppoe_plugin.so (PPPoE)
> load_one_plugin:184: Loaded plugin: sample_plugin.so (Sample of VPP Plugin)
> load_one_plugin:184: Loaded plugin: srv6ad_plugin.so (Dynamic SRv6 proxy)
> load_one_plugin:184: Loaded plugin: srv6am_plugin.so (Masquerading SRv6 proxy)
> load_one_plugin:184: Loaded plugin: srv6as_plugin.so (Static SRv6 proxy)
> load_one_plugin:184: Loaded plugin: stn_plugin.so (VPP Steals the NIC for 
> Container integration)
> tls_init_ca_chain:1125: Could not initialize TLS CA certificates
> tls_init:1168: failed to initialize TLS CA chain
> tls_init: failed to initalize TLS CA chain
>
>

[vpp-dev] Error during startup

2018-03-07 Thread Shashi Kant Singh 
Hi

When I try to start vpp with release 17:10 and 18:01,. I am getting following 
TLS error

What could be the issue?

Regards
Shashi
PS: This worked fine for previous releases.

#  make run-release STARTUP_CONF=../startup.conf
vlib_plugin_early_init:356: plugin path 
/bng5/shashi-2/vpp2/vpp/build-root/install-vpp-native/sample-plugin/lib64/vpp_plugins:/bng5/shashi-2/vpp2/vpp/build-root/install-vpp-native/vpp/lib64/vpp_plugins
load_one_plugin:184: Loaded plugin: acl_plugin.so (Access Control Lists)
load_one_plugin:184: Loaded plugin: dpdk_plugin.so (Data Plane Development Kit 
(DPDK))
load_one_plugin:184: Loaded plugin: flowprobe_plugin.so (Flow per Packet)
load_one_plugin:184: Loaded plugin: gbp_plugin.so (Group Based Policy)
load_one_plugin:184: Loaded plugin: gtpu_plugin.so (GTPv1-U)
load_one_plugin:184: Loaded plugin: ila_plugin.so (Identifier-locator 
addressing for IPv6)
load_one_plugin:184: Loaded plugin: ioam_plugin.so (Inbound OAM)
load_one_plugin:114: Plugin disabled (default): ixge_plugin.so
load_one_plugin:184: Loaded plugin: kubeproxy_plugin.so (kube-proxy data plane)
load_one_plugin:184: Loaded plugin: l2e_plugin.so (L2 Emulation)
load_one_plugin:184: Loaded plugin: lb_plugin.so (Load Balancer)
load_one_plugin:184: Loaded plugin: libsixrd_plugin.so (IPv6 Rapid Deployment 
on IPv4 Infrastructure (RFC5969))
load_one_plugin:184: Loaded plugin: memif_plugin.so (Packet Memory Interface 
(experimetal))
load_one_plugin:184: Loaded plugin: nat_plugin.so (Network Address Translation)
load_one_plugin:184: Loaded plugin: pppoe_plugin.so (PPPoE)
load_one_plugin:184: Loaded plugin: sample_plugin.so (Sample of VPP Plugin)
load_one_plugin:184: Loaded plugin: srv6ad_plugin.so (Dynamic SRv6 proxy)
load_one_plugin:184: Loaded plugin: srv6am_plugin.so (Masquerading SRv6 proxy)
load_one_plugin:184: Loaded plugin: srv6as_plugin.so (Static SRv6 proxy)
load_one_plugin:184: Loaded plugin: stn_plugin.so (VPP Steals the NIC for 
Container integration)
tls_init_ca_chain:1125: Could not initialize TLS CA certificates
tls_init:1168: failed to initialize TLS CA chain
tls_init: failed to initalize TLS CA chain