Skip to content

[VPP-474] VPP could not start, because huge pages config file location was changed #1724

@vvalderrv

Description

@vvalderrv

Description

i have 3 builds (deb packages), one from 28.sep, second from 4.oct and third from 7.oct

when i uninstalled vpp with:

sudo dpkg --purge vpp vpp-dbg vpp-dev vpp-dpdk-dev vpp-dpdk-dkms vpp-lib vpp-plugins

and have installed second or third build, vpp could not start because huge pages config file is here:

<li>Applying /usr/lib/sysctl.d/80-vpp.conf ...

instead of /etc as was in first build

if i check hugepages (after reboot), they are not set:

vagrant@localhost:~$ cat /proc/meminfo | grep Huge

AnonHugePages: 0 kB

HugePages_Total: 0

HugePages_Free: 0

HugePages_Rsvd: 0

HugePages_Surp: 0

Hugepagesize: 2048 kB

and vpp is not starting:

Oct 7 05:07:39 localhost kernel: [ 4278.641325] init: vpp main process ended, respawning

Oct 7 05:07:39 localhost vpp[1519]: dpdk_config: not enough free huge pages

Oct 7 05:07:39 localhost kernel: [ 4278.670617] init: vpp main process ended, respawning

Oct 7 05:07:39 localhost vpp[1526]: dpdk_config: not enough free huge pages

Oct 7 05:07:39 localhost kernel: [ 4278.700084] init: vpp respawning too fast, stopped

also inside deb file, path was changed:

rw-rr- root/root 548 2016-08-24 23:58 ./usr/lib/sysctl.d/80-vpp.conf

workaround for this is just reinstalling old one (first) build with some newer build (without uninstalling previous), then path is not changed to /usr/lib and file stays in /etc/sysctl.d:

- Applying /etc/sysctl.d/80-vpp.conf ...

i have:

Linux localhost 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Assignee

Andrej Marcinek

Reporter

Andrej Marcinek

Comments

  • amarcine (Wed, 26 Oct 2016 10:55:21 +0000): workaround was sufficient to fix this
  • mmiklus (Tue, 11 Oct 2016 10:13:20 +0000):

    There is a bug in Ubuntu procps upstart script:

https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1632269

  • mmiklus (Tue, 11 Oct 2016 09:21:10 +0000): workaround for Ubuntu 14.04:
sudo ln -s /usr/lib/sysctl.d/80-vpp.conf /etc/sysctl.d/80-vpp.conf
- **amarcine (Tue, 11 Oct 2016 07:16:12 +0000)**: clean install of both builds (uninstalled previous, then installed new)

**build (28.sep):**

vagrant@localhost:~/vpp_hc/vpp_pbb_6$ cat /usr/lib/sysctl.d/80-vpp.conf

cat: /usr/lib/sysctl.d/80-vpp.conf: No such file or directory

vagrant@localhost:~/vpp_hc/vpp_pbb_6$ cat /etc/sysctl.d/80-vpp.conf

  1. Number of 2MB hugepages desired

    vm.nr_hugepages=1024

  1. Must be greater than or equal to (2 * vm.nr_hugepages).

    vm.max_map_count=3096

  1. All groups allowed to access hugepages

    vm.hugetlb_shm_group=0

    - Shared Memory Max must be greator or equal to the total size of hugepages. - For 2MB pages, TotalHugepageSize = vm.nr_hugepages * 2 * 1024 * 1024 - If the existing kernel.shmmax setting (cat /sys/proc/kernel/shmmax) - is greater than the calculated TotalHugepageSize then set this parameter
  1. to current shmmax value.

    kernel.shmmax=2147483648

**build (4.oct):**

vagrant@localhost:~/vpp_hc/vpp_pbb_7$ cat /usr/lib/sysctl.d/80-vpp.conf

  1. Number of 2MB hugepages desired

    vm.nr_hugepages=1024

  1. Must be greater than or equal to (2 * vm.nr_hugepages).

    vm.max_map_count=3096

  1. All groups allowed to access hugepages

    vm.hugetlb_shm_group=0

    - Shared Memory Max must be greator or equal to the total size of hugepages. - For 2MB pages, TotalHugepageSize = vm.nr_hugepages * 2 * 1024 * 1024 - If the existing kernel.shmmax setting (cat /sys/proc/kernel/shmmax) - is greater than the calculated TotalHugepageSize then set this parameter
  1. to current shmmax value.

    kernel.shmmax=2147483648

vagrant@localhost:~/vpp_hc/vpp_pbb_7$ cat /etc/sysctl.d/80-vpp.conf

cat: /etc/sysctl.d/80-vpp.conf: No such file or directory

  • mmiklus (Mon, 10 Oct 2016 14:48:56 +0000): Could you please paste output of:
cat /usr/lib/sysctl.d/80-vpp.conf
cat /etc/sysctl.d/80-vpp.conf
- **dmarion (Mon, 10 Oct 2016 09:14:00 +0000)**: Miro, Can you take a look as you did this change?

Original issue: https://jira.fd.io/browse/VPP-474

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions