imunify360-resident running at high CPU speed

Issue

• The `imunify360-resident` process running at high CPU speed:

root     1056263 95.4  0.4 1834424 16960 ?       Ssl  11:52  17:35 /usr/bin/imunify-resident

• The Imunify360's console log has the following entries:

:~# grep "AuditLog path" /var/log/imunify360/console.log

2024-10-27T06:13:06.521+0100 INFO ModsecSensor AuditLog path: /var/log/httpd/modsec_audit.log
2024-10-27T13:13:05.582+0100 INFO ModsecSensor AuditLog path: /var/log/httpd/modsec_audit.log
2024-10-27T20:13:05.893+0100 INFO ModsecSensor AuditLog path: /var/log/httpd/modsec_audit.log
2024-10-28T03:13:05.712+0100 INFO ModsecSensor AuditLog path: /var/log/httpd/modsec_audit.log
2024-10-28T10:13:05.778+0100 INFO ModsecSensor AuditLog path: /var/log/httpd/modsec_audit.log
2024-10-29T10:54:42.309+0100 INFO ModsecSensor AuditLog path: /var/log/httpd/modsec_audit.log
2024-10-29T12:08:24.598+0100 INFO ModsecSensor modsec/processor.go:147 AuditLog path: /var/log/modsec_audit.log

• The log file mentioned in the entries does not exist:

~# stat /var/log/httpd/modsec_audit.log
stat: cannot statx '/var/log/httpd/modsec_audit.log': No such file or directory

Environment

• Imunify360 stand-alone
• Ubuntu

Solution

1. Ensure that`/etc/sysconfig/imunify360/integration.conf` contains the correct path to the `modsec_audit.log` file.

2. Make the necessary corrections.

3. Restart the Imunify360 service.

Cause

The issue is that in `/etc/sysconfig/imunify360/integration.conf`, the path to `modsec_audit.log` points to the wrong path ([web_server]modsec_audit_log).