Hi,

if you have two vpp instances running with same shm prefix, conflicts are to be 
expected. It’s possible that the second instance mangled file system entries 
for the first one. When running more than one vpp instance, you need to ensure 
that every one of those has a unique shared memory prefix. You can take a look 
at how the test framework does this.

Regards,
Klement

> On 12 Dec 2022, at 16:59, Chinmaya Aggarwal via lists.fd.io 
> <chinmaya.agarwal=hsc....@lists.fd.io> wrote:
> 
> Hi,
> 
> We have a main VPP process running and we have IPIP tunnels configured in VPP 
> which we try to fetch using VAPI API calls. It works fine in normal scenarios 
> but when we by mistake executed the command "vpp" from linux command line, we 
> saw that an additional VPP daemon started running and also that VAPI API call 
> is not able to fetch IPIP tunnel data anymore. On killing this daemon 
> manually, we observed that VAPI connections could not be established anymore 
> and VPP's main process also got into a bad state. Restarting VPP fixed the 
> issue and we were able to fetch IPIP tunnel data through VAPI APIs.
> 
> What is the purpose of this command "vpp" and is it a valid use case to run 
> multiple vpp daemons? Also, how can we restrict the additional daemon from 
> starting if VPP's main process is already running?
> 
> Thanks and Regards,
> Chinmaya Agarwal. 
> 
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22328): https://lists.fd.io/g/vpp-dev/message/22328
Mute This Topic: https://lists.fd.io/mt/95624233/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to