Re: [vpp-dev] Facing issue with cli-listen option in vpp.conf
Hi Ben, Thank you for your response. Actually in one of the usecase I was trying to execute few vpp command from host using vppctl and not really want to go to vpp terminal with telnet and execute the command. I see it was working earlier and the below check in change the behavior. I am not sure why... " https://github.com/FDio/vpp/commit/31f192434660a6fe71663fd62172cb82fc79ede1 " Thanks, Amaresh On Mon, Jul 18, 2022, 18:28 Benoit Ganne (bganne) via lists.fd.io wrote: > Not sure if that is what you are looking for, but in that case, I just use > plain telnet to connect to VPP, as "telnet localhost 5002". > No need for vppctl in that case. > > ben > > > -Original Message- > > From: vpp-dev@lists.fd.io On Behalf Of Amaresh > > Parida > > Sent: Saturday, July 16, 2022 4:32 > > To: vpp-dev@lists.fd.io > > Subject: Re: [vpp-dev] Facing issue with cli-listen option in vpp.conf > > > > Hi All, > > Any inputs on the below query will be very helpful. > > > > Thanks, > > Amaresh > > > > On Fri, Jul 15, 2022, 14:42 Amaresh Parida via lists.fd.io > > <http://lists.fd.io> > <mailto:gmail@lists.fd.io> > wrote: > > > > > > Hi All > > > > This is regarding the cli-listen option in vpp.conf. > > I want to use cli-listen localhost:5002 instead of cli-listen > > /run/vpp/cli.sock > > After VPP start when I execute vppctl command, I see following > > error in VPP > > > > CLI# vppctl -s localhost:5002 > > connect: No such file or directory > > > > When I do a stack trace I found even if I gave localhost:5002 > > meaning to connect to TCP socket listen on 5002 for cli, > > it consider it as unix socket and takes the input as unix file (It > > should have been connected to TCP socket) > > I can see the port 5002 is opened and in listen mode and I could > > able to do a telnet. > > > > But vppctl fails > > > > > > > > > > > > Any suggestions? > > > > Thanks, > > Amaresh > > > > > > > > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#21679): https://lists.fd.io/g/vpp-dev/message/21679 Mute This Topic: https://lists.fd.io/mt/92397125/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] -=-=-=-=-=-=-=-=-=-=-=-
Re: [vpp-dev] Facing issue with cli-listen option in vpp.conf
Hi All, Any inputs on the below query will be very helpful. Thanks, Amaresh On Fri, Jul 15, 2022, 14:42 Amaresh Parida via lists.fd.io wrote: > Hi All > > This is regarding the cli-listen option in vpp.conf. > I want to use* cli-listen localhost:5002* instead of *cli-listen > /run/vpp/cli.sock* > After VPP start when I execute vppctl command, I see following error in > VPP > > > *CLI# vppctl -s localhost:5002connect: No such file or directory* > > When I do a stack trace I found even if I gave localhost:5002 meaning to > connect to TCP socket listen on 5002 for cli, > it consider it as unix socket and takes the input as unix file (It should > have been connected to TCP socket) > I can see the port 5002 is opened and in listen mode and I could able to > do a telnet. > > But vppctl fails > > [image: image.png] > > Any suggestions? > > Thanks, > Amaresh > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#21669): https://lists.fd.io/g/vpp-dev/message/21669 Mute This Topic: https://lists.fd.io/mt/92397125/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] -=-=-=-=-=-=-=-=-=-=-=-
[vpp-dev] Facing issue with cli-listen option in vpp.conf
Hi All This is regarding the cli-listen option in vpp.conf. I want to use* cli-listen localhost:5002* instead of *cli-listen /run/vpp/cli.sock* After VPP start when I execute vppctl command, I see following error in VPP *CLI# vppctl -s localhost:5002connect: No such file or directory* When I do a stack trace I found even if I gave localhost:5002 meaning to connect to TCP socket listen on 5002 for cli, it consider it as unix socket and takes the input as unix file (It should have been connected to TCP socket) I can see the port 5002 is opened and in listen mode and I could able to do a telnet. But vppctl fails [image: image.png] Any suggestions? Thanks, Amaresh -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#21663): https://lists.fd.io/g/vpp-dev/message/21663 Mute This Topic: https://lists.fd.io/mt/92397125/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] -=-=-=-=-=-=-=-=-=-=-=-
Re: [vpp-dev] Need suggestion to understand LCP failure on VPP restart
Hi Matt, Sorry for the late reply. Please find the response inline In what way are the logs misleading? The call to the TUNSETIFF ioctl in tap_create_if() is returning an error code. The message "Argument list too long" corresponds to the error number E2BIG, which is being set by the kernel's tun driver. AFAICT the tun driver only returns that error here - https://github.com/torvalds/linux/blob/a175eca0f3d747599f1fdfac04cc9195b71ec996/drivers/net/tun.c#L771. The condition that causes it is 'tun->numqueues + tun->numdisabled == MAX_TAP_QUEUES'. So too many queues are being allocated on the tap. That's from the current upstream linux kernel source code. It's possible that some older version returned that error code for some other reason. >>>>Amaresh>> I was hoping when we stop the docker where vpp is running the queue would have been free and should have been reallocated. I understood your point. I was just trying to mention that docker restart doesn't add any new config, it's the old config as previous vpp instance so why the E2BIG error. However, I can understand your explanation here. I will investigate in that area w.r.to docker and driver functioning. What version of kernel are you running when this error happens? The current value of MAX_TAP_QUEUES is 256. On older versions of the kernel it was 8. Your screenshot showed that DPDK initialization detected 20 lcores. How many worker threads does VPP have configured? >>>Amaresh>>>> Kernel version: 5.13.0-51-generic #58~20.04.1-Ubuntu SMP Tue Jun 14 11:29:12 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux. I did not configured any specific. Currently just 1 main core [image: image.png] I don't ever run VPP in a docker container, so I don't know why this would happen intermittently. Could your container be getting migrated to a different host system when it restarts? Or could it be getting started with a different number of CPU cores allocated or worker threads configured in VPP's startup.conf? >>>Amaresh: No Its the same host and with the same configuration Thanks, Amaresh Thanks, Amaresh On Fri, Jul 1, 2022 at 7:00 PM Matthew Smith via lists.fd.io wrote: > > On Wed, Jun 29, 2022 at 10:23 PM Amaresh Parida > wrote: > >> Hi Dave, >> >> Thanks for the response. >> The initial run is ok. The issue just happen on vpp restart. >> >> I think that won't change any args. >> >> Its appears to me may be the logs are misleading and probably a side >> effect of corrupted memory or so. >> >> Let me know if you think otherwise. >> >> > In what way are the logs misleading? The call to the TUNSETIFF ioctl in > tap_create_if() is returning an error code. The message "Argument list too > long" corresponds to the error number E2BIG, which is being set by the > kernel's tun driver. AFAICT the tun driver only returns that error here - > https://github.com/torvalds/linux/blob/a175eca0f3d747599f1fdfac04cc9195b71ec996/drivers/net/tun.c#L771. > The condition that causes it is 'tun->numqueues + tun->numdisabled == > MAX_TAP_QUEUES'. So too many queues are being allocated on the tap. That's > from the current upstream linux kernel source code. It's possible that some > older version returned that error code for some other reason. > > What version of kernel are you running when this error happens? The > current value of MAX_TAP_QUEUES is 256. On older versions of the kernel it > was 8. Your screenshot showed that DPDK initialization detected 20 lcores. > How many worker threads does VPP have configured? > > I don't ever run VPP in a docker container, so I don't know why this would > happen intermittently. Could your container be getting migrated to a > different host system when it restarts? Or could it be getting started with > a different number of CPU cores allocated or worker threads configured in > VPP's startup.conf? > > -Matt > > > >> >> On Wed, Jun 29, 2022, 18:17 Dave Barach wrote: >> >>> You might try adding additional debugs to print the arg list length and >>> args. >>> >>> Comparing the success and failure cases should give at least a hint. >>> >>> HTH... Dave >>> >>> On Jun 29, 2022, at 7:55 AM, Amaresh Parida >>> wrote: >>> >>> >>> Hi All, >>> Any inputs on the below query will be very helpful. >>> >>> Thanks, >>> Amaresh >>> >>> On Fri, Jun 24, 2022 at 6:09 PM Amaresh Parida >>> wrote: >>> >>>> Hi All, >>>> >>>> I am facing an issue on restarting VPP where sometimes LinuxCP >>>> tap interface is not getting created. >>>> >>>> Here is the complete probl
