I am facing an issue while installing INJI Certify, where the server CPU utilisation consistently reaches close to 100%.
Upon initial investigation, it appears that the process dnsmasq may be contributing to the high resource consumption. I monitored the system using the top command and observed unusually high CPU usage across multiple intervals. Relevant excerpts are shared below:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
89661 dnsmasq 20 0 521916 270136 3632 S 83.3 13.4 33:13.08 mysql
89661 dnsmasq 20 0 521916 270136 3632 S 91.7 13.4 9:46.46 mysql
It appears that this process intermittently consumes up to 90% of CPU resources, particularly during periods when application load is otherwise low (e.g., when Java processes are not heavily consuming resources). This behaviour suggests the presence of a potentially rogue or misconfigured process.
Request you to kindly review this issue and advise on the cause and possible resolution.
Could you share your machine specifications?
→ Please refer the logs.
Which virtual machines are you currently using?
→ Please refer the logs.
Apart from Injicertify, are there any other services deployed in your cluster?
→ only Inji Certify
Is your deployment managed via Docker Compose or Kubernetes?
→ Docker
OS we are using is:
Distributor ID: Ubuntu
Description: Ubuntu 24.04.3 LTS
Release: 24.04
Codename: noble
Based on the VM details you shared, it appears that your setup is running on a 1 vCPU and 2 GB RAM instance. On this single vCPU, multiple services such as Certify (Java), MySQL, and Redis are running concurrently.
With only 1 vCPU available, all these processes compete for CPU time. This can easily lead to situations where CPU utilisation reaches close to 100%, even under moderate load. From the top output, it looks like MySQL and Java processes are the primary contributors to CPU usage, rather than a rogue process.
Also, please note that dmidecode output in virtual environments may not always provide complete clarity, but it does confirm limited CPU and memory resources in this case.
As per the documentation, INJI Certify requires a minimum VM specification. I would recommend comparing your current VM configuration with the documented requirements and trying with the recommended specifications.
Our team will also review this behaviour and get back to you with further inputs. In the meantime, please try scaling the VM resources (CPU/RAM) as per the guidelines and observe if the issue persists.