• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!

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