• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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