Issue resctrl failed: Connection timed out

[B4c4rd1]

Meanwhile, I have the problem that it takes a long time before a new domain was created. Partially the process is interrupted and I get the following error message:

resctrl failed: /bin/systemctl execution failed: Failed to execute operation: Connection timed out

The domain is created partially. So that I can create the domain again, I must first delete in the database psa different entries and on fileiebene the folder.

Apache config: gracefull restart

Can you give me tips on how to prevent a time out?

Thanks!

 

[IgorG]

Try to disable cgroups feature with

# plesk sbin resctrl --disable

Does this solve your issue?

 

[B4c4rd1]

Yes. But I'm not quite sure. Sometimes it worked, sometimes not. I will tentatively test whether the error occurs again if I deactivate cgroups before.

Edit: cgroups reloads very long. Over 2 Minutes....

 

[B4c4rd1]

The following error appears in the syslog log file:

Plesk_resctrl [1188]: move_to_cgroup (): pam_open_session () failed 6: Permission denied

 

[IgorG]

Is this Ubuntu 16.04? Have you installed upstart-sysv and removed systemd-sysv?

 

[B4c4rd1]

Is this Ubuntu 16.04? Have you installed upstart-sysv and removed systemd-sysv?

No. systemd-sysv is installed and yes, ubuntu 16.04!

Next problem:
If I am running plesk sbin resctrl --disable and then resctrl plesk sbin --enable all service packages must be re-synced, so that the settings are taken over by cgroups.

This is easy to test by running a test with apachebench. The CPU limit does not work after a restart or --disable and -enable

 

[B4c4rd1]

@IgorG

can you confirm this as a bug?

In addition, I can create new domains only with great difficulty. It takes several minutes. So far, 95 domains/subdomains have been created in the system. The more it will be all the worse it gets. Do you have a tip as I can improve the problem? Or do I disable cgroups?

 

[IgorG]

We have the corresponding request in our bugtracker. But after deep developer's investigation, it was closed as invalid because there were problems with customized/broken systemd-sysv. Therefore we can't confirm this bug. I'd suggest you contact Plesk Support Team for deep investigation directly on your server.

 

[B4c4rd1]

@IgorG

Many thanks for your response. I will check this with a test system. The ticket PPP-28915 is still being processed?

It all sounds as if there are many problems with systemd-sysv. This raises the question of how to make the correct state.

 

[IgorG]

The ticket PPP-28915 is still being processed?

Yes, it is marked as fixed in 17.8 but in progress for previous versions.