Need Assistance?

In only two hours, with an average response time of 15 minutes, our expert will have your problem sorted out.

Server Trouble?

For a single, all-inclusive fee, we guarantee the continuous reliability, safety, and blazing speed of your servers.

How to Fix “Imunify360 Agent Not Running” in Panel UI and Migration Error in Logs

Table of Contents

If you are managing Linux servers with Imunify360 installed, you might occasionally encounter a situation where the Panel UI reports the “Imunify360 Agent Not Running” message. This Imunify360 agent not running fix issue can be frustrating, but it is usually resolvable with a few commands executed from the terminal.

Understanding the Issue

The problem typically appears in the Panel UI when the Imunify360 agent fails to start. Upon checking the logs, we could see that entries like the following:

tail -f /var/log/imunify360/error.log

This warning indicates that the Imunify360 agent attempted to start, but the necessary database migrations were not applied. As a result, the service cannot fully initialize, leading to the “not running” status in the panel.

Workaround

We can resolve this issue by restarting the Imunify360 services in a specific sequence. Follow these steps from the root account:

  1. Stop Imunify360 Agent
systemctl stop imunify360-agent

Stops the Imunify360 agent process if it is partially running.

1.Stop Imunify360 Service

systemctl stop imunify360

Stops the main Imunify360 service to ensure a clean restart.

3.Reset Failed State

systemctl reset-failed imunify360-agent

Clears any failed systemd state that may prevent the agent from starting.

4.Start Imunify360 Service

systemctl start imunify360

Starts the main service first to ensure database migrations can be applied.

5. Pause for 5 Seconds
Gives the service a short buffer to initialize before starting the agent.

6. Start Imunify360 Agent

systemctl start imunify360-agent

Finally, starts the agent successfully after migrations are applied.

Conclusion

The “Imunify360 Agent Not Running” warning is typically related to pending migrations that prevent the service from initializing properly. By following the sequence above, you can quickly restore full functionality without needing to reboot your server or perform complex troubleshooting.

Keep an eye on /var/log/imunify360/error.log after performing this fix to ensure that no further warnings appear. For long-term stability, ensure your Imunify360 installation is fully updated and properly maintained.

If you’re still facing issues after trying these steps for the Imunify360 agent not running fix, our experts can help.we specialize in Server Management Services and Linux Server Support Services, providing 24×7 assistance to diagnose, secure, and optimize your server environment. Contact our team today to get your Imunify360 and server panel running smoothly again!

Liked!! Share the post.

Get Support right now!

Start server management with our 24x7 monitoring and active support team

Subscribe and get your first issue fixed for Free!

Looking for server support and 24x7 monitoring?

Have doubts? Connect with us now.