Re: Based on the VPP to Nginx testing #vpp #ngnix

Florin Coras
 

Hi Amit, 

Here’s a minimal example [1] that’s based on some of the scripts I’m using. Note that I haven’t tested this in isolation, so do let me know if you hit any issues. 

Regards, 
Florin

On Feb 12, 2020, at 11:43 PM, Amit Mehra <amito2in@...> wrote:

Hi,

I am also curious to know how to run nginx with VPP using LD_PRELOAD option. I have installed nginx and able to run it successfully without VPP. Now, i want to try nginx with vpp using LD_PRELOAD option, can someone provide me the steps for the same?

Regards,
Amit

On Fri, Dec 27, 2019 at 11:57 AM Florin Coras <fcoras.lists@...> wrote:
Hi Yang.L,

I suspect you may need to do a “git pull” and rebuild because the lines don’t match, i.e., vcl_session_accepted_handler:377 is now just an assignment. Let me know if that solves the issue.

Regards,
Florin

> On Dec 26, 2019, at 10:11 PM, lin.yang13@... wrote:
>
> Hi Florin,
> I have tried the latest master.The problem is not resolved.
> Here's the nginx error linformation:
>
> epoll_ctl:2203: ldp<269924>: epfd 33 ep_vlsh 1, fd 61 vlsh 29, op 1
> ldp_accept4:2043: ldp<269924>: listen fd 32: calling vppcom_session_accept: listen sid 0, ep 0x0, flags 0xffffdc50
> vppcom_session_accept:1521: vcl<269924:1>: listener 16777216 [0x0] accepted 30 [0x1e] peer: 192.168.3.66:47672 local: 192.168.3.65:8080
> epoll_ctl:2203: ldp<269924>: epfd 33 ep_vlsh 1, fd 62 vlsh 30, op 1
> ldp_accept4:2043: ldp<269924>: listen fd 32: calling vppcom_session_accept: listen sid 0, ep 0x0, flags 0xffffdc50
> vppcom_session_accept:1521: vcl<269924:1>: listener 16777216 [0x0] accepted 31 [0x1f] peer: 192.168.3.66:47674 local: 192.168.3.65:8080
> epoll_ctl:2203: ldp<269924>: epfd 33 ep_vlsh 1, fd 63 vlsh 31, op 1
> ldp_accept4:2043: ldp<269924>: listen fd 32: calling vppcom_session_accept: listen sid 0, ep 0x0, flags 0xffffdc50
> vcl_session_accepted_handler:377: vcl<269924:1>: ERROR: segment for session 32 couldn't be mounted!
> 2019/12/28 11:06:44 [error] 269924#0: accept4() failed (103: Software caused connection abort)
> ldp_accept4:2043: ldp<269924>: listen fd 32: calling vppcom_session_accept: listen sid 0, ep 0x0, flags 0xffffdc50
> vcl_session_accepted_handler:377: vcl<269924:1>: ERROR: segment for session 32 couldn't be mounted!
> 2019/12/28 11:06:44 [error] 269924#0: accept4() failed (103: Software caused connection abort)
> ldp_accept4:2043: ldp<269924>: listen fd 32: calling vppcom_session_accept: listen sid 0, ep 0x0, flags 0xffffdc50
> vcl_session_accepted_handler:377: vcl<269924:1>: ERROR: segment for session 32 couldn't be mounted!
> 2019/12/28 11:06:44 [error] 269924#0: accept4() failed (103: Software caused connection abort)
> ldp_accept4:2043: ldp<269924>: listen fd 32: calling vppcom_session_accept: listen sid 0, ep 0x0, flags 0xffffdc50
> vcl_session_accepted_handler:377: vcl<269924:1>: ERROR: segment for session 32 couldn't be mounted!
> 2019/12/28 11:06:44 [error] 269924#0: accept4() failed (103: Software caused connection abort)
> ldp_accept4:2043: ldp<269924>: listen fd 32: calling vppcom_session_accept: listen sid 0, ep 0x0, flags 0xffffdc50
> vcl_session_accepted_handler:377: vcl<269924:1>: ERROR: segment for session 32 couldn't be mounted!
> 2019/12/28 11:06:44 [error] 269924#0: accept4() failed (103: Software caused connection abort)
>
> Can you help me analyze it?
> Thanks,
> Yang.L

>

Join vpp-dev@lists.fd.io to automatically receive all group messages.