Resolved Error installing Clamav in Plesk Email Security

[ErnestoSF]

Server operating system version

Almalinux 9.1

Plesk version and microupdate number

Obsidian 18.0.50

Hi, I am installing a new Plesk server with Almalinux 9.1. When I install Plesk Email Security, Clamav give an error:

Installing ClamAV
Execution filemng has failed with exit code 1, stdout: Last metadata expiration check: 0:07:43 ago on Fri 03 Feb 2023 01:08:27 PM CET.
No match for argument: clamsmtp
, stderr: Error: Unable to find a match: clamsmtp

Plesk is Obsidian 18.0.50 and all components are updated.

I tried to install clamsmtp manually but this package is not found.

Perhaps is there any incompatibility with Almalinux 9?

Thanks

 

[Peter Debik]

Hi @ErnestoSF , this can probably not be solved without an engineer checking it on your system. Please open a ticket with Plesk support and mention these two potentially matching IDs that I have already researched for them to get them started on it faster: article no. 7163410945682 and ID EXTPLESK-3847.

How to get support directly from Plesk?

Question How to get support directly from Plesk? Answer Lease-type Plesk licenses purchased directly from Plesk running on supported Plesk version include full free support. Perpetual-type license...

support.plesk.com

 

[ErnestoSF]

I have reinstalled again with Almalinux 8.7 and Plesk Email Security gives another error. It's new server, with new installation of Almalinux and new installation of Plesk usin 1Click install.

Execution pleskrc has failed with exit code 1, stdout: INFO: [Sun Feb 5 20:45:32 CET 2023]: Service: amavisd, Action: restart
Trying to restart service amavisd... active
Feb 05 20:45:32 xxxxxxx systemd[1]: amavisd.service: Control process exited, code=exited status=255
Feb 05 20:45:32 xxxxxxx systemd[1]: amavisd.service: Failed with result 'exit-code'.
Feb 05 20:45:32 xxxxxxx systemd[1]: Failed to start Amavis mail content checker.

***** problem report *****
Warning: restart service amavisd failed

, stderr: Job for amavisd.service failed because the control process exited with error code.
See "systemctl status amavisd.service" and "journalctl -xe" for details.


The logs:
systemctl status amavisd.service
● amavisd.service - Amavis mail content checker
Loaded: loaded (/usr/lib/systemd/system/amavisd.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2023-02-05 20:45:34 CET; 1min 40s ago
Docs: amavisd-new
Process: 139662 ExecStart=/usr/sbin/amavisd -c /etc/amavisd/amavisd.conf (code=exited, status=255)
Main PID: 139445 (code=exited, status=0/SUCCESS)

Feb 05 20:45:34 systemd[1]: amavisd.service: Control process exited, code=exited status=255
Feb 05 20:45:34 systemd[1]: amavisd.service: Failed with result 'exit-code'.
Feb 05 20:45:34 systemd[1]: Failed to start Amavis mail content checker.
Feb 05 20:45:34 systemd[1]: amavisd.service: Service RestartSec=100ms expired, scheduling restart.
Feb 05 20:45:34 systemd[1]: amavisd.service: Scheduled restart job, restart counter is at 4.
Feb 05 20:45:34 systemd[1]: Stopped Amavis mail content checker.
Feb 05 20:45:34 systemd[1]: amavisd.service: Start request repeated too quickly.
Feb 05 20:45:34 systemd[1]: amavisd.service: Failed with result 'exit-code'.
Feb 05 20:45:34 systemd[1]: Failed to start Amavis mail content checker.

journalctl -xe
-- the configured Restart= setting for the unit.
Feb 05 20:49:53 xxxxxx systemd[1]: Stopped Amavis mail content checker.
-- Subject: Unit amavisd.service has finished shutting down
-- Defined-By: systemd
-- Support: Red Hat Customer Experience & Engagement - Red Hat Customer Portal
--
-- Unit amavisd.service has finished shutting down.
Feb 05 20:49:53 xxxxxxx systemd[1]: amavisd.service: Start request repeated too quickly.
Feb 05 20:49:53 xxxxxxx systemd[1]: amavisd.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: Red Hat Customer Experience & Engagement - Red Hat Customer Portal
--
-- The unit amavisd.service has entered the 'failed' state with result 'exit-code'.
Feb 05 20:49:53 xxxxxxx systemd[1]: Failed to start Amavis mail content checker.
-- Subject: Unit amavisd.service has failed
-- Defined-By: systemd
-- Support: Red Hat Customer Experience & Engagement - Red Hat Customer Portal
--
-- Unit amavisd.service has failed.
--
-- The result is failed.



Previous Plesk installation with Almalinux 8, did not had this errors with Plesk Email Security.
I don't know if may be a bug with the las version of Plesk, the last verion of the extension or the las version of Almalinux.

 

[ErnestoSF]

Investigating a bit more, I found that Amavis installation give that error because one module of perl was missing and may be installed manually:

yum install perl-DBD-MySQL

Once installed, the extension ends installation without errors.

So with Almalinux 8 this extension works fine but with Almalinux 9 gives the error of Clamav installation

 

[johnrdorazio]

Along these same lines, I tried installing the Plesk Email Security extension a few days ago, after I had already installed ClamAv on my system. The Plesk Email Security dashboard is showing that ClamAv is not installed. Maybe because it was already installed and running as a service, so Plesk Email Security wasn't able to register it as installed? Should I have stopped the service before installing Plesk Email Security?

 

[johnrdorazio]

Along these same lines, I tried installing the Plesk Email Security extension a few days ago, after I had already installed ClamAv on my system. The Plesk Email Security dashboard is showing that ClamAv is not installed. Maybe because it was already installed and running as a service, so Plesk Email Security wasn't able to register it as installed? Should I have stopped the service before installing Plesk Email Security?

 

[grizlyadams]

View attachment 24614

View attachment 24613

I have this same issue - did you get it resolved?

 

[hermano.correia]

I have the same problem, any solution?

OS: AlmaLinux 9.4 (Seafoam Ocelot)
Product: Plesk Obsidian Version 18.0.63, last update on 2024/08/9 13:22
Plesk Email Security Version 1.5.9-3779

Thanks

 

[Sebahat.hadzhi]

Hello, @hermano.correia. The issue is caused by a known bug with ID EXTPLESK-3847 that is affecting the Plesk Email Security extension functions on AlmaLinux 9.x. The permanent fix for the bug will be released in one of the upcoming Plesk releases. In the meantime, the alternative we can suggest is a possible workaround described in the article about the issue:

• https://support.plesk.com/hc/en-us/...maLinux-server-No-match-for-argument-clamsmtp

I hope that helps.

 

[hermano.correia]

Hello, @hermano.correia. The issue is caused by a known bug with ID EXTPLESK-3847 that is affecting the Plesk Email Security extension functions on AlmaLinux 9.x. The permanent fix for the bug will be released in one of the upcoming Plesk releases. In the meantime, the alternative we can suggest is a possible workaround described in the article about the issue:

• https://support.plesk.com/hc/en-us/...maLinux-server-No-match-for-argument-clamsmtp

I hope that helps.

Thank you

It helped!

Regards
Hermano Correia

 

[grizlyadams]

that workaround didn't help for me, it still shows as not installed.

 

[Sebahat.hadzhi]

Could you please provide more details on the steps you performed and the failure message?

 

[grizlyadams]

Hi,

I did exactly the steps outlined in the workaround - downloaded the clamav.php file, backed up the existing php file in the loaction specified in the workaround and put the new clamav.php file in to that loaction.

The error is exactly the same as in post #6 above

 

[Raul A.]

Hi,

I encountered an issue installing PES ClamAV when ClamAV was already installed on the system from other sources.

Remove all ClamAV packages then install it again from the PES interface.

 

[Sebahat.hadzhi]

There is no actual error mentioned in post 6 in this thread. As far as I understand, you see ClamAV as 'Not Installed', but I am wondering what's the actual error/failure you encounter during the installation.

 

[Raul A.]

As for the Amavis service, reset the failed count restart the service and see what error is logged in journalctl

systemctl reset-failed amavisd
systemctl restart amavisd
journalctl -xeu amavisd

 

[grizlyadams]

There is no actual error mentioned in post 6 in this thread. As far as I understand, you see ClamAV as 'Not Installed', but I am wondering what's the actual error/failure you encounter during the installation.

No there isn't, and neither is there an errorr during the PES install, but it shows the symptom/result.

 

[grizlyadams]

Hi,

I encountered an issue installing PES ClamAV when ClamAV was already installed on the system from other sources.

Remove all ClamAV packages then install it again from the PES interface.

when you say "install it again from the PES interface" - do you mean remove clamav (with dnf remove clamav*) then remove PES and install it again?

 

[grizlyadams]

I have removed Clam AV with dnf remove clamav*
then removed PES
then added the PES extension
then did the fix (replace the Clamav.php file)
then opened the PES extension which installed PES /clamav etc.

same problem - still says "not installed" in the PES extension.

 

[Sebahat.hadzhi]

No there isn't, and neither is there an errorr during the PES install, but it shows the symptom/result.

Sorry for not clarifying that earlier, I was referring to the error/failure you see during the installation of ClamAV through Plesk Email Security rather than the installation of the extension itself.

Please note that ClamAV is not included in the free version of Plesk Email Security. Therefore, if you are not using the premium version it is normal to see the ClamAV as not installed. Alternatively, please try installing it, and provide the output, so we can attempt to further address the issue.