Issue ai-bolit not able to run as on-demand service in container server environment

[Liwindo]

Server operating system version

Ubuntu 20.04 ESM

Plesk version and microupdate number

18.0.72

Hi,
I have since the rework of Imunify the issue that ai-bolt will not run as expected. Due to the latest Plesk patch I decided to perform finally some analysis and according to ChatGPT it's related how the tool is designed:

Ah, now it’s clear why the service won’t start:
Failed to create cgroup /Imunify.slice/Imunify-Scan.slice/Imunify-Scan-aibolit.slice/aibolit-resident.service: Permission denied
status=219/CGROUP

The issue is not with ai-bolit itself, but with the cgroup slices that the service tries to use.
The path /Imunify.slice/Imunify-Scan.slice/Imunify-Scan-aibolit.slice is normally created by systemd with root privileges, but in your environment (likely shared hosting or a restrictive container/VM), even root services are not allowed to create their own slices under /Imunify.slice.
That’s why the service immediately fails with 219/CGROUP.

---

Consequences​

• As long as the slice Imunify-Scan-aibolit.slice cannot be created, the resident service cannot run.
• Even if you create the slice under /etc/systemd/system, systemd will block it if you don’t have permission to create sub-slices.
• This is typical in shared hosting or restrictive container environments.

Is it possible to fix that?

 

[Sebahat.hadzhi]

Hello, @Liwindo . Could you please confirm where you see the error/how we can attempt to replicate it? Can you also confirm if the Imunify extension is version 8.5.1-2? Lastly, does that happen on VPS/dedicated server, container or shared hosting environment.

Thank you in advance.

 

[Liwindo]

Hi @Sebahat.hadzhi,
the error message comes from "journalctl -u aibolit-resident.service -n 30 --no-pager". It was a long way I turned with ChatGPT and therefore hard to replicate it here completely. The origin of that issue comes from error messages related to ai-bolit either with patching it manually (apt upgrade) or a warning message before the Plesk upgrade. All attempts fixing it with the known methods led to messages like "A dependency job for aibolit-resident.service failed. See 'journalctl -xe' for details.".

The extension is up-to-date = 8.5.1-2.

It happens on a VPS based on Virtuozzo.

 

[Sebahat.hadzhi]

Thank you for your update. I would suggest opening a ticket with Plesk support for further investigation on your server and involvement of Cloudlinux if necessary. To sign-in and open a ticket please go to:

• https://support.plesk.com

If you got your license from a reseller, your reseller is in charge of providing you with support. You can raise the inquiry with them and they can forward it to our team for further processing.If the reseller does not provide support, here is an alternative to get support directly from Plesk:

• How to get support directly from Plesk?