• 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.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • 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.

Issue InmunifyAV Job imunify-notifier.service/start failed with result 'dependency'.

IT Ufficio Key-One

Basic Pleskian
Server operating system version
Almalinux 8.10
Plesk version and microupdate number
Obsidian 18.0.64#1
Hi, we're changing old ImunifyAV with the new version on all our Plesk Servers.

New Imunify works fine on all servers and I was trying to enable the notifications.
On one server I was able to create the needed script and obtain the desired notification, while on other servers when saving the Notification panel I get a "System error".
Digging around, I have found that the imunify-notifier.service isn't starting due to a "Failed to create listening socket: Permission denied" and then a "dependency".

Uninstalling and re-installing does not fix.
Could you please help?
 
Hi @AWSolutions, I escalated the issue directly to imunify support. I've been asked to purchase at least a licence in order to have premium assistance by the Specialized support team.

My issue was related to selinux being enabled, and this prevented imunify services starting correctly. Disabling selinux, services were working correctly. Imunify should work with selinux both enabled and disabled. This was a bug in imunify installer, that was incorrectly applying some directives related to selinux on Almalinux 8.

The support provided me a temporary fix, that should then be deployed globally and documentation fixed with correct procedure. In case, you can check it out with imunify support, by mentioning the case id #236673, if your issue is the same as mine. Hope this helps.
 
Back
Top