Excuse me, when vagrant up --parallel --provision came up, there was a lot of 
errors. How to solve it?

Unpack, print the following:

fiber@ubuntu:~/toni/csit-vagrant$ vagrant up --parallel --provision
Bringing machine 'tg' up with 'virtualbox' provider...
Bringing machine 'dut1' up with 'virtualbox' provider...
Bringing machine 'dut2' up with 'virtualbox' provider...
==> tg: Running provisioner: shell...
    tg: Running: inline script
    tg: Removing user `csit' ...
    tg: Warning: group `csit' has no more members.
    tg: Done.
    tg: Adding user `csit' ...
    tg: Adding new group `csit' (1001) ...
    tg: Adding new user `csit' (1001) with group `csit' ...
    tg: The home directory `/home/csit' already exists.  Not copying from 
`/etc/skel'.
    tg: Adding user `csit' to group `vagrant' ...
    tg: Adding user csit to group vagrant
    tg: Done.
    tg: uid=1001(csit) gid=1001(csit) groups=1001(csit),1000(vagrant)
    tg: csit ALL=(root) NOPASSWD:ALL
==> tg: Running provisioner: shell...
    tg: Running: inline script
    tg: Reading package lists...
    tg: Reading package lists...
    tg: Building dependency tree...
    tg: Reading state information...
    tg: 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
    tg: Reading package lists...
    tg: Building dependency tree...
    tg: Reading state information...
    tg: Package debhelper is not available, but is referred to by another 
package.
    tg: This may mean that the package is missing, has been obsoleted, or
    tg: is only available from another source
    tg: E
    tg: : 
    tg: Package 'debhelper' has no installation candidate
==> dut1: Running provisioner: shell...
    dut1: Running: inline script
    dut1: Removing user `csit' ...
    dut1: Warning: group `csit' has no more members.
    dut1: Done.
    dut1: Adding user `csit' ...
    dut1: Adding new group `csit' (1001) ...
    dut1: Adding new user `csit' (1001) with group `csit' ...
    dut1: The home directory `/home/csit' already exists.  Not copying from 
`/etc/skel'.
    dut1: Adding user `csit' to group `vagrant' ...
    dut1: Adding user csit to group vagrant
    dut1: Done.
    dut1: uid=1001(csit) gid=1001(csit) groups=1001(csit),1000(vagrant)
    dut1: csit ALL=(root) NOPASSWD:ALL
==> dut1: Running provisioner: shell...
    dut1: Running: inline script
    dut1: Reading package lists...
    dut1: Reading package lists...
    dut1: Building dependency tree...
    dut1: Reading state information...
    dut1: Correcting dependencies...
    dut1:  Done
    dut1: The following packages will be REMOVED:
    dut1:   vpp vpp-api-java vpp-api-lua vpp-api-python vpp-lib vpp-plugins
    dut1: 0 upgraded, 0 newly installed, 6 to remove and 0 not upgraded.
    dut1: 6 not fully installed or removed.
    dut1: After this operation, 85.7 MB disk space will be freed.
    dut1: (Reading database ... 93104 files and directories currently 
installed.)
    dut1: Removing vpp-api-lua (18.07-rc0~41-g410bcca) ...
    dut1: Removing vpp-plugins (18.07-rc0~41-g410bcca) ...
    dut1: Removing vpp (18.07-rc0~41-g410bcca) ...
    dut1: There weren't PCI devices binded
    dut1: Removing vpp-api-java (18.07-rc0~41-g410bcca) ...
    dut1: Removing vpp-api-python (18.07-rc0~41-g410bcca) ...
    dut1: Removing vpp-lib (18.07-rc0~41-g410bcca) ...
    dut1: Processing triggers for libc-bin (2.19-0ubuntu6.7) ...
    dut1: Reading package lists...
    dut1: Building dependency tree...
    dut1: Reading state information...
    dut1: Package debhelper is not available, but is referred to by another 
package.
    dut1: This may mean that the package is missing, has been obsoleted, or
    dut1: is only available from another source
    dut1: E
    dut1: : 
    dut1: Package 'debhelper' has no installation candidate
==> dut1: Running provisioner: shell...
    dut1: Running: inline script
    dut1: Reading package lists...
    dut1: Building dependency tree...
    dut1: Reading state information...
    dut1: Package 'vpp-lib' is not installed, so not removed
    dut1: The following packages will be REMOVED:
    dut1:   vpp* vpp-dbg* vpp-dev*
    dut1: 0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
    dut1: After this operation, 158 MB disk space will be freed.
    dut1: (Reading database ... 92876 files and directories currently 
installed.)
    dut1: Removing vpp (18.07-rc0~41-g410bcca) ...
    dut1: Purging configuration files for vpp (18.07-rc0~41-g410bcca) ...
    dut1: There weren't PCI devices binded
    dut1: Removing vpp-dbg (18.07-rc0~41-g410bcca) ...
    dut1: Removing vpp-dev (18.07-rc0~41-g410bcca) ...
    dut1: W
    dut1: : 
    dut1: Can not find PkgVer for 'vpp'
    dut1: Selecting previously unselected package vpp.
    dut1: (Reading database ... 91951 files and directories currently 
installed.)
    dut1: Preparing to unpack vpp_18.07-rc0~41-g410bcca_amd64.deb ...
    dut1: Unpacking vpp (18.07-rc0~41-g410bcca) ...
    dut1: Selecting previously unselected package vpp-api-java.
    dut1: Preparing to unpack vpp-api-java_18.07-rc0~41-g410bcca_amd64.deb ...
    dut1: Unpacking vpp-api-java (18.07-rc0~41-g410bcca) ...
    dut1: Selecting previously unselected package vpp-api-lua.
    dut1: Preparing to unpack vpp-api-lua_18.07-rc0~41-g410bcca_amd64.deb ...
    dut1: Unpacking vpp-api-lua (18.07-rc0~41-g410bcca) ...
    dut1: Selecting previously unselected package vpp-api-python.
    dut1: Preparing to unpack vpp-api-python_18.07-rc0~41-g410bcca_amd64.deb ...
    dut1: Unpacking vpp-api-python (18.07-rc0~41-g410bcca) ...
    dut1: Selecting previously unselected package vpp-dbg.
    dut1: Preparing to unpack vpp-dbg_18.07-rc0~41-g410bcca_amd64.deb ...
    dut1: Unpacking vpp-dbg (18.07-rc0~41-g410bcca) ...
    dut1: Selecting previously unselected package vpp-dev.
    dut1: Preparing to unpack vpp-dev_18.07-rc0~41-g410bcca_amd64.deb ...
    dut1: Unpacking vpp-dev (18.07-rc0~41-g410bcca) ...
    dut1: Selecting previously unselected package vpp-lib.
    dut1: Preparing to unpack vpp-lib_18.07-rc0~41-g410bcca_amd64.deb ...
    dut1: Unpacking vpp-lib (18.07-rc0~41-g410bcca) ...
    dut1: Selecting previously unselected package vpp-plugins.
    dut1: Preparing to unpack vpp-plugins_18.07-rc0~41-g410bcca_amd64.deb ...
    dut1: Unpacking vpp-plugins (18.07-rc0~41-g410bcca) ...
    dut1: dpkg: dependency problems prevent configuration of vpp:
    dut1:  vpp depends on init-system-helpers (>= 1.18~); however:
    dut1:   Version of init-system-helpers on system is 1.14.
    dut1:  vpp depends on lsb-base (>= 4.1+Debian11ubuntu7); however:
    dut1:   Version of lsb-base on system is 4.1+Debian11ubuntu6.1.
    dut1: dpkg: error processing package vpp (--install):
    dut1:  dependency problems - leaving unconfigured
    dut1: dpkg: dependency problems prevent configuration of vpp-api-java:
    dut1:  vpp-api-java depends on vpp (= 18.07-rc0~41-g410bcca); however:
    dut1:   Package vpp is not configured yet.
    dut1: dpkg: error processing package vpp-api-java (--install):
    dut1:  dependency problems - leaving unconfigured
    dut1: dpkg: dependency problems prevent configuration of vpp-api-lua:
    dut1:  vpp-api-lua depends on vpp (= 18.07-rc0~41-g410bcca); however:
    dut1:   Package vpp is not configured yet.
    dut1: dpkg: error processing package vpp-api-lua (--install):
    dut1:  dependency problems - leaving unconfigured
    dut1: dpkg: dependency problems prevent configuration of vpp-api-python:
    dut1:  vpp-api-python depends on python-cffi; however:
    dut1:   Package python-cffi is not installed.
    dut1:  vpp-api-python depends on vpp (= 18.07-rc0~41-g410bcca); however:
    dut1:   Package vpp is not configured yet.
    dut1: Setting up vpp-dbg (18.07-rc0~41-g410bcca) ...
    dut1: dpkg: error processing package vpp-api-python (--install):
    dut1:  dependency problems - leaving unconfigured
    dut1: Setting up vpp-dev (18.07-rc0~41-g410bcca) ...
    dut1: dpkg: dependency problems prevent configuration of vpp-lib:
    dut1:  vpp-lib depends on libstdc++6 (>= 5.2); however:
    dut1:   Version of libstdc++6:amd64 on system is 4.8.4-2ubuntu1~14.04.3.
    dut1: dpkg: error processing package vpp-lib (--install):
    dut1:  dependency problems - leaving unconfigured
    dut1: dpkg: dependency problems prevent configuration of vpp-plugins:
    dut1:  vpp-plugins depends on vpp (= 18.07-rc0~41-g410bcca); however:
    dut1:   Package vpp is not configured yet.
    dut1:  vpp-plugins depends on libmbedcrypto0 (>= 2.0); however:
    dut1:   Package libmbedcrypto0 is not installed.
    dut1:  vpp-plugins depends on libmbedtls10 (>= 2.0); however:
    dut1:   Package libmbedtls10 is not installed.
    dut1:  vpp-plugins depends on libmbedx509-0 (>= 2.0); however:
    dut1:   Package libmbedx509-0 is not installed.
    dut1:  vpp-plugins depends on libssl1.0.0 (>= 1.0.2~beta3); however:
    dut1:   Version of libssl1.0.0:amd64 on system is 1.0.1f-1ubuntu2.19.
    dut1: dpkg: error processing package vpp-plugins (--install):
    dut1:  dependency problems - leaving unconfigured
    dut1: Processing triggers for ureadahead (0.100.0-16) ...
    dut1: ureadahead will be reprofiled on next reboot
    dut1: Processing triggers for libc-bin (2.19-0ubuntu6.7) ...
    dut1: Errors were encountered while processing:
    dut1:  vpp
    dut1:  vpp-api-java
    dut1:  vpp-api-lua
    dut1:  vpp-api-python
    dut1:  vpp-lib
    dut1:  vpp-plugins
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.



nwnj...@fiberhome.com
 
发件人: 汤超
发送时间: 2018-04-17 10:59
收件人: csit-dev
主题: [csit-dev] I need some help.Please help me.
Hello, everyone, 

I have installed the framework of CSIT in accordance with the official network 
tutorial, but after the vagrant SSH dut1 in, sudo start VPP this command knocks 
invalid. How to solve it, is it necessary to set up some settings in dut1?

Tutorials web site:
https://wiki.fd.io/view/CSIT/Tutorials/Vagrant/Virtualbox/Ubuntu 
         Vagrant will download base disk images and install the VPP debian 
packages to bring those machines to required state. VPP will NOT be started 
automatically.
        Optionally, verify that VPP successfully starts on one of the dut VMs:
vagrant ssh dut1
sudo service vpp start
sudo vppctl sh int
sudo cat /var/log/upstart/vpp.log
sudo service vpp stop
exit

vagrant@dut1:~$ sudo service vpp start
vpp: unrecognized service
vagrant@dut1:~$  sudo start vpp
start: Unknown job: vpp
vagrant@dut1:~$ 


The tutorial of official website is not clear. Is there any step missing?

Please help me.   Thank you



nwnj...@fiberhome.com

Reply via email to