• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • The ImunifyAV extension is now deprecated and no longer available for installation.
    Existing ImunifyAV installations will continue operating for three months, and after that will automatically be replaced with the new Imunify extension. We recommend that you manually replace any existing ImunifyAV installations with Imunify at your earliest convenience.

Resolved Imunify upgrade failed!

LionKing

Regular Pleskian
Server operating system version
Ubuntu 24.04.1
Plesk version and microupdate number
Version 18.0.66 Update #2
Hello fellas.
I just attempted to run and upgrade Imunify as per announced recommendation but it fails and will not start the Imunify service.

Here is the error when I tried to start it in the command prompt:

1738367671130.png

I have no clue what to do from here....
Thoughts?

Thanks in advance!
 
Here is the installation log on Pastebin:
imunify-installation-log - Pastebin.com
The main issue seems to be this (?):
Code:
[2025-02-01 01:02:04] [2025-02-01 01:02:04] Waiting for ImunifyAV to start...[2025-02-01 01:02:05] [2025-02-01 01:02:05] ERROR: imunify360 service is stopped.

Thanks again.
Kind regards
 
Well...
I solved it myself (Cheating a bit with the help of ChatGPT :cool:) .

So I will post the solution for others that might run into the same issue:

In systemd (which Plesk uses on most Linux distributions), a "masked" service means it has been explicitly disabled and cannot be started or enabled until it is "unmasked."

To check the status and fix it, follow these steps:

1. Check if the service is masked​

Run this command in SSH:

bash

Code:
systemctl is-enabled imunify-antivirus

If it returns masked, then the service is indeed disabled.

2. Unmask the service​

Run the following command to unmask it:

bash

Code:
systemctl unmask imunify-antivirus

3. Enable and Start the Service​

After unmasking, try enabling and starting the service:

bash

Code:
systemctl enable imunify-antivirus --now

4. Verify the Service Status​

Check if it’s running correctly:

Bash

Code:
systemctl status imunify-antivirus

If the issue persists, try reinstalling ImunifyAV:

bash

Code:
plesk installer --select-release-current --install-component imunify-antivirus

Result:
1738369562420.png

Hope this helps other people here on the forums! ;)
Kind regards
 
Back
Top