modprobe: ERROR: could not insert 'kmodlve': Cannot allocate memory Print

  • 0

Symptoms

CloudLinux Manager in WHM shows that the server needs to be rebooted after rebooting, and an error similar to the following can be found in the system log.

modprobe: ERROR: could not insert 'kmodlve': Cannot allocate memory

 

Description

The issue occurs due to the systemd.unified_cgroup_hierarchy value set to 1 at boot. The value should be 0.

 

Workaround

  1. Access the server's command line as the 'root' user via SSH or "Terminal" in WHM.
  2. Open the /etc/default/grub file in your preferred text editor.
  3. On the GRUB_CMDLINE_LINUX line, change systemd.unified_cgroup_hierarchy=1 to systemd.unified_cgroup_hierarchy=0.
  4. Save the changes and exit the text editor.
  5. Rebuild the GRUB configuration.
    grub2-mkconfig -o /etc/grub2.cfg
    grub2-mkconfig -o /etc/grub2-efi.cfg
    grub2-mkconfig -o /boot/grub2/grub.cfg
    grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg
    grub2-mkconfig -o /boot/efi/EFI/almalinux/grub.cfg
  6. Reboot the server.

 

Additional resources

LVE load fail: could not insert 'kmodlve': Cannot allocate memory


Was this answer helpful?
Back

Send Message