Issue
-
Imunify360 is installed on Cloudlinux 6 server.
-
Notifications such as the following appear in panel UI:
The service “imunify360” appears to be down.
The service “imunify360” is now operational.
-
Attempts to restart the service fail:
# service imunify360 restart
Shutting down imunify360-unified-access-logger: [FAILED]
Shutting down imunify-auditd-log-reader: [ OK ]
Shutting down imunify-realtime-av: [FAILED]
Shutting down imunify360: [FAILED]
Starting imunify360: Starting migrations
There is nothing to migrate
Sentry is attempting to send 1 pending error messages
Waiting up to 2.0 seconds
Press Ctrl-C to quit
[FAILED] -
Unable to save changes on the Settings tab.
-
The following error can be found in
/var/log/imunify360/error.log
:ERROR [2022-06-23 13:58:37,470] defence360agent.server: Instance of imunify360 is already running. Parent process "bash" with pid "7321". Sockets are in use by [(1725496, 'python3', 'parent process = init'), (7714, 'imunify-service', 'parent process = minidaemon'), (1735143, 'python3', 'parent process = python3')]. /var/run/imunify360.pid file contents None pid
Environment
- CentOS 6
- Cloudlinux 6
- Imunify360
- cPanel
Solution
This is a known problem that has already been fixed in Imunify since version 6.4. To fix it, it is enough to update Imunify to the latest current release.
For earlier versions, and in situations where updating is not the appropriate option, the minidaemon process can be killed with the following command:
# kill $(ps aux | grep minidaemon-av | grep -v grep | awk '{ print $2 }')
Cause
Software issue DEF-19290 which is fixed in the 6.4 release. During the update minidaemon process with minidaemon-av.cfg
stay running.
Comments
0 comments
Please sign in to leave a comment.