Hi Praveen, Inline.
> On Nov 19, 2025, at 9:19 PM, Praveen Singh via lists.fd.io > <[email protected]> wrote: > > Hi Florin, > Thank you for your reply. Here is the additional log which I printed. > VCL<2105>: configured namespace_id vcl > VCL<2105>: configured namespace_secret 123456 (0x1e240) > VCL<2105>: completed parsing vppcom config! > vppcom_app_create:1503: vcl<0:-1>: Allocate default worker > vcl_worker_alloc_and_init:287: vcl<2105:0>: Praveen: worker index 0, worker > mqs_epfd 5, wrk->app_api_sock.fd > clib_socket_init:639: Praveen: socket (fd 6, '/var/run/pw/vpp-api.sock') > vcl_bapi_connect_to_vpp:558: vcl<2105:0>: app (test-wrk-0) is connected to > VPP! > vcl_bapi_init:663: vcl<2105:0>: sending session enable > vcl_mq_epoll_add_api_sock:54: vcl<2105:0>: created cs->fd=0 wrk->mqs_epfd 5 > errno=1 (Operation not permitted) rv -1 This is used to track vpp’s status. So not critical unless you want vcl to reattach after vpp restarts. > vcl_mq_epoll_add_evfd:93: vcl<2105:0>: created mqs_epfd=10 wrk->mqs_epfd 5 > errno=1 (Operation not permitted) This is used by vpp to signal the presence of new events in the message queue to vcl. If “mqs_epfd” is actually “mq_fd” in that function, the value looks reasonable. Maybe this is really a permission problem. Have you tried running the app as root? Regards, Florin > vppcom_app_create:1513: vcl<2105:0>: app_name 'test', my_client_index 1280 > (0x500) > DEBUG: vcl_app_create_wrapper: VCL app creation - app_name=test, ret=0 > vppcom_session_create:1572: vcl<2105:0>: created session 0 > DEBUG: vcl_socket_wrapper: VCL socket created - domain=2, type=2, proto=17, > options=2, sockfd=0, errno=0 (Success) > DEBUG: vcl_bind_wrapper: === BIND OPERATION START === > DEBUG: vcl_bind_wrapper: sockfd=0, addrlen=16 > vppcom_session_bind:1767: vcl<2105:0>: session 0 handle 0: binding to local > IPv4 address 10.166.220.80 port 862, proto UDP > vppcom_session_listen:1796: vcl<2105:0>: session 0: sending vpp listen > request... > vcl_send_session_listen:75: vcl_send_session_listen: vnode id:0 thread id:0 > clt:1280 wrk:0 port:24067 proto:1 > vcl_session_app_add_segment_handler:992: vcl<2105:0>: mapped new segment > 'seg-5-6-52' size 134230016 > vcl_session_bound_handler:602: vcl<2105:0>: session 0 [0xf]: listen succeeded! > DEBUG: vcl_bind_wrapper: VCL bind result - sockfd=0, ret=0, errno=0 (Success) > DEBUG: vcl_bind_wrapper: VCL bind successful - sockfd=0 > > One more question, What is the impact of the below error? > vcl_mq_epoll_add_evfd:90: vcl<118:0>: failed to add mq socket to mq epoll fd > > Thanks, > Praveen > > On Thu, Nov 20, 2025 at 1:19 AM Florin Coras via lists.fd.io > <http://lists.fd.io/> <[email protected] > <mailto:[email protected]>> wrote: >> Hi Praveen, >> >> You’d probably have to check the exact reason why epoll_ctl fails. But some >> quick comments: >> - we’re moving away from binary api in vcl. We’re still building it but it’s >> slowly being deprecated. I’d recommend switching to sapi api. >> - maybe check vl_api_app_attach_reply_t_handler and confirm that >> wrk->app_event_queue fd we got from vl_socket_client_recv_fd_msg2 is >> reasonable. >> >> Regards, >> Florin >> >> > On Nov 18, 2025, at 7:59 PM, Praveen Singh via lists.fd.io >> > <http://lists.fd.io/> <[email protected] >> > <mailto:[email protected]>> wrote: >> > >> > Hi All, >> > When i connected my vcl app, i got below error. any input on below error? >> > <inline.0.part> >> > >> > >> > >> >> >> >> > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#26534): https://lists.fd.io/g/vpp-dev/message/26534 Mute This Topic: https://lists.fd.io/mt/116369201/21656 Group Owner: [email protected] Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/14379924/21656/631435203/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
