Kemp Support, how can we help?

The latest application delivery knowledge and expertise at your fingertips.

LoadMaster error log: kernel: L7: Being too busy

 

Information

 

Summary:

LoadMaster error log: kernel: L7: Being too busy

Environment:

Product: LoadMaster

Version: Any

Platform: Virtual

Application: Any

Question/Problem Description:

Seeing more notifications with the message "kernel: L7: Being too busy" Is this a concern that should be addressed?

Steps to Reproduce:  
Error Message:  
Defect Number:  
Enhancement Number:  
Cause: This message can occur when even one thread on one CPU core is busy for more than one second. Not all CPU cores have to be fully busy for this log to occur, so it does not mean the system is maxed out.
Resolution: If this error is occurring frequently in the logs of the virtual LoadMaster (VLM), then it would be advised to add additional vCPUs to the virtual machine via the respective Hypervisor console (resource limits may be imposed by the Hypervisor platform). This would require the LoadMaster to be powered down, the additional vCPUs added and then powered back on again. This change will automatically take effect once the LoadMaster boots up.
Workaround:  
Notes:

VMware Virtual LoadMaster:

https://support.kemptechnologies.com/hc/en-us/articles/10112393403277-VMware

Hyper-V Virtual LoadMaster:

https://support.kemptechnologies.com/hc/en-us/articles/10112195077133-Microsoft-Hyper-V

Nutanix/Xen Virtual LoadMaster:

https://support.kemptechnologies.com/hc/en-us/articles/10112240137357-Nutanix

https://support.kemptechnologies.com/hc/en-us/articles/10112396757901-XEN-Fully-Virtualized

Cloud Virtual LoadMaster:

https://support.kemptechnologies.com/hc/en-us/articles/10112012175117-LoadMaster-for-Azure

https://support.kemptechnologies.com/hc/en-us/articles/10111785949965-LoadMaster-for-AWS


Comments