Marek,
Please check the vpp startup configuration (/etc/vpp/startup.conf) to
ensure that "unix { cli-listen /run/vpp/cli.sock }" is present. This is
the default socket used by the 'c' implementation of vppctl.
I'm going to fix the error message to output the socket file name to
make this easier to debug.
Thanks,
-daw-
On 09/06/2017 05:55 AM, Marek Gradzki -X (mgradzki - PANTHEON
TECHNOLOGIES at Cisco) wrote:
Dave,
please find replies inline.
*From:*Dave Wallace [mailto:dwallac...@gmail.com]
*Sent:* 5 września 2017 16:41
*To:* Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco)
<mgrad...@cisco.com>; vpp-dev@lists.fd.io
*Subject:* Re: [vpp-dev] Running CLI against named vpp instance
Marek,
What is the uid/gid of /dev/shm/vpe-api ?
root/vpp
Is the user a member of the vpp group?
yes
Does your VPP workspace include the patch c900ccc34 "Enabled gid vpp
in startup.conf to allow non-root vppctl access" ?
yes (I’ve built master with HEAD @ 809bc74, also tested corresponding
package from nexus)
Thanks,
-daw-
On 09/05/2017 06:08 AM, Marek Gradzki -X (mgradzki - PANTHEON
TECHNOLOGIES at Cisco) wrote:
Hi,
I am having problems with running CLI against named vpp instance
(g809bc74):
sudo vpp api-segment { prefix vpp0 }
sudo vppctl -p vpp0 show int
clib_socket_init: connect: Connection refused
But ps shows vpp process is running.
It worked with 17.07.
Is it no longer supported or I need some additional configuration?
Regards,
Marek
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io>
https://lists.fd.io/mailman/listinfo/vpp-dev
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
