Bug ID 446187: Manual start of a BIG-IP APM service may trigger 100 percent CPU utilization.

Last Modified: Apr 10, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP APM(all modules)

Opened: Jan 24, 2014
Severity: 2-Critical
Related AskF5 Article:
K15309

Symptoms

As a result of this issue, you may encounter the following symptoms: -- BIG-IP iHealth lists Heuristic H465125 on the Diagnostics :: Identified :: High screen. -- The BIG-IP APM service that you started causes system CPU utilization to increases over time, and eventually to consume all available CPU. -- Users may be unable to access the BIG-IP APM access profiles. -- When you view the Configuration utility, dashboard CPU consumption continually increases. -- In the /var/log/ltm log file, you may observe log messages similar to the following examples. notice chmand[6792]: 012a0005:5: Cpu utilization over 300 seconds is 100%, exceeded log level 80% notice chmand[6792]: 012a0005:5: Cpu utilization over 300 seconds is 100%, exceeded log level 80%

Impact

The user may be unable to access the system, and the BIG-IP APM system may stop responding.

Conditions

This issue occurs when all of the following conditions are met: -- The BIG-IP service is already running. -- You manually start the BIG-IP service from the command line either directly or by using bigstart. -- The BIG-IP service is running one of the following services: aced, acctd, apd, eam, rba, or websso

Workaround

Never start any daemon manually. The proper way to start, stop, and restart daemons on the BIG-IP system is to use the bigstart utility: bigstart start daemonname bigstart stop daemonname bigstart restart daemonname

Fix Information

None

Behavior Change