Sorry for spamming, but using strace I noticed that vppctl tried to connect to a socket file in */run/vpp*
This folder didn't exist, but when I created it, vpp could start successfully. There's no such folder in my Ubuntu install, so is this exclusive to RHEL based distros? /Tomas On 28 June 2017 at 13:21, Tomas Brännström <tomas.a.brannst...@tieto.com> wrote: > We targeted CentOS instead and there it works fine to build and install. > > However, there's some other issue now. When I start the VPP service, it > looks like it immediately dies: > > $ sudo service vpp start > Redirecting to /bin/systemctl start vpp.service > $ sudo service vpp status > Redirecting to /bin/systemctl status vpp.service > ● vpp.service - Vector Packet Processing Process > Loaded: loaded (/usr/lib/systemd/system/vpp.service; disabled; vendor > preset: disabled) > Active: inactive (dead) > > This error message is printed: > vpp[5859]: clib_socket_init: bind: No such file or directory > > This is in a Virtualbox VM. Not sure how to proceed since usually a better > error message is printed when it fails (for example missing drivers and > whatnot). > > /Tomas > > On 27 June 2017 at 21:17, Klement Sekera -X (ksekera - PANTHEON > TECHNOLOGIES at Cisco) <ksek...@cisco.com> wrote: > >> Unfortunately, I'm no rpm packaging expert, somebody else will have to >> chime in... >> >> Thanks, >> Klement >> >> Quoting Tomas Brännström (2017-06-27 17:18:40) >> > I got the same error :-( >> > make bootstrap and build works, but building rpg packages fail... >> > /Tomas >> > On 27 June 2017 at 16:25, Klement Sekera -X (ksekera - PANTHEON >> > TECHNOLOGIES at Cisco) <[1]ksek...@cisco.com> wrote: >> > >> > Hi Tomas, >> > >> > could you please take a look at the main Makefile: >> > >> > 57 ifeq ($(OS_ID)-$(OS_VERSION_ID),fedora-25) >> > 58 RPM_DEPENDS += python2-virtualenv >> > 59 RPM_DEPENDS_GROUPS = 'C Development Tools and Libraries' >> > 60 else >> > 61 RPM_DEPENDS += python-virtualenv >> > 62 RPM_DEPENDS_GROUPS = 'Development Tools' >> > 63 endif >> > >> > see how the fedora-25 is the version which uses python2-virtualenv >> > while all others use python-virtualenv? Could you please change >> > fedora-25 >> > to fedora-24 on line 57 and let us know if this smooths things out? >> > Maybe the fix is a simple one-liner... >> > >> > Thanks, >> > Klement >> > >> > Quoting Tomas Brännström (2017-06-27 16:08:31) >> > > Hello >> > > I'm having some troubles building VPP (latest master) from >> source >> > on >> > > Fedora 24. >> > > At first when doing `make bootstrap' it complained about not >> > finding >> > > python-virtualenv. I could get around this by changing >> changing the >> > > Makefile to look for "python2-virtualenv" which was the >> version >> > that got >> > > installed. >> > > But when doing `make pgk-rpm' I get the following errors: >> > > make[2]: Entering directory >> > '/home/fedora/git/vpp/extras/rpm/vpp-17.10' >> > > Please install missing RPMs: \npackage python-virtualenv is >> not >> > > installed\n >> > > by executing "make install-dep"\n >> > > Makefile:175: recipe for target >> > > >> > '/home/fedora/git/vpp/extras/rpm/vpp-17.10/build-root/.boots >> trap.ok' >> > > failed >> > > make[2]: *** >> > > >> > [/home/fedora/git/vpp/extras/rpm/vpp-17.10/build-root/.boots >> trap.ok] >> > Error >> > > 1 >> > > make[2]: Leaving directory >> > '/home/fedora/git/vpp/extras/rpm/vpp-17.10' >> > > error: Bad exit status from /var/tmp/rpm-tmp.qSFuzD (%build) >> > > RPM build errors: >> > > Macro %python2_minor_version defined but not used within >> scope >> > > Bad exit status from /var/tmp/rpm-tmp.qSFuzD (%build) >> > > Makefile:22: recipe for target 'all' failed >> > > make[1]: *** [all] Error 1 >> > > make[1]: Leaving directory '/home/fedora/git/vpp/extras/rpm' >> > > Makefile:397: recipe for target 'pkg-rpm' failed >> > > make: *** [pkg-rpm] Error 2 >> > > I tried changing to python2-virtualenv in that Makefile as >> well but >> > it >> > > seems to change back into python-virtualenv, and besides, >> there >> > seems to >> > > be other problems here as well. >> > > Is there a workaround for this or is Fedora 24 simply not >> > supported? >> > > /Tomas >> > >> > References >> > >> > Visible links >> > 1. mailto:ksek...@cisco.com > > >
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
