Critical fix for Imunify 4.8.x?

[samy.janson]

Is it possible to downgrade to version 4.7.x ?
Or do we have to remove Imunify completely until the critical bug is fixed? Do you have any eta for the fix?

[skhristich]

Hello Morten,
We are really sorry about your experience. Our support team is working on this issue right now. Get back to you later with a fix. Thank you.

[morten]

Ok, thanks. Hope we can get this fixed today so we dont have to uninstall it on all servers!

[skhristich]

Hi Morten,
Thanks for waiting. Presumably this is happening due to the fact that sometimes the number of running PHP processes spikes enough to make imunify360-php-daemon hit the maximum number of open files threshold.
That maximum number of open files is specified on a service level and defaults to 1024.
The imunify360-php-daemon version 1.1.3-1 that has been installed along with the latest update has this limit increased to 4096 by default through the system unit.
As a workaround, the limit can be increased by executing

systemctl edit imunify360-php-daemon

and saving the following:

[Service]

LimitNOFILE=4096

After that, please execute

systemctl restart imunify360-php-daemon

If the above doe not resolves the problem, please get back to us with a ticket https://cloudlinux.zendesk.com/hc/en-us/requests/new so that we can take a closer look at the problem.
We are still working on a permanent fix, it will take several days.
Thank you for understanding.