Agent consuming excessive CPU during / after IMA measurement
See original GitHub issueEnvironment
- OS / version: Fedora 31
- Processor architecture: VM
- TPM Manufacturer: Emulator
- Keylime version: master
Description
Some CPU spikes have been observed up to 100%
This continues even after changing the agents operation status to deleted. Only way to stop is to ctrl break the agent.
Steps to reproduce problem
- Provision with the following as an example:
keylime_tenant -t 127.0.0.1 -v 127.0.0.1 --cert /root/democa --exclude /root/excludes.txt --whitelist /root/whitelist.txt --include /root/payload -c add
Relevant logs
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (8 by maintainers)
Top Results From Across the Web
High %sys CPU usage an uptick in the load when 3rd party ...
The high CPU utilization in the kernel-space ( %system ) is due to spinlock contention caused by the Trend Micro Deep Security module...
Read more >High CPU usage on machines with Deep Security Agent
The CPU is being used for the cleanup of Integrity Monitoring baselines. This may cause a sudden increase in CPU usage. CPU usage...
Read more >Imperva´s Agent | Imperva Cyber Community
Agent CPU utilization is typically within 3% of the CPU of the DBs and it should not cause any degradation in normal operations....
Read more >High CPU and memory usage on some PCs after the ... - N-able
High CPU and memory usage on some PCs after the installation of N-able agent. Everything went back to normal after removing the N-able...
Read more >Common Causes for High CPU with the Windows OS Agent
An inefficiently written situation formula can also cause high CPU utilization. Using wildcard characters (*) and/or the MISSING function in situations is one ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Is that the whitelist for IMA verification? If yes, this is surprising to me, as I thought (based only on log interpretation) that the measurement/IMA matching was performed by the verifier and the agents simply sent the measurements. Did I get it wrong?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 7 days if no further activity occurs. Thank you for your contributions.