• 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 Extreme delay with some operations

Vinko

New Pleskian
Hi,

I have Plesk Onyx installed on CentOS 7 VPS. Some operations complete with a delay which ranges from one or two minutes (e.g. opening WordPress toolkit, every single time, even if there's only one WP website), and some take more than 5 minutes (installing a "Domain Connect" extension took 6 minutes).

I opened htop, and saw command "systemd --switched-root --system --deserialize 22" takes 100% of CPU white the operation is trying to execute (so, while I'm waiting for WordPress toolkit to load, systemd takes 100% for the whole 2 minutes).

How can I figure out what went wrong with the server?
 
When systemd is running with the deserialize option:

systemd --switched-root --system --deserialize 22

The deserialize option is used to restore saved internal state that a previous invocation of systemd has written out to a file. Its option argument is an open file descriptor for that process. This command loads CPU, thus Apache doesn't have enough resources to run.
In this case, server reboot solves the issue.
 
To be honest, I have no idea what this all means :) , but yes, I can confirm that reboot solved it. But, why would I have to reboot the server to fix this? Why this problem occures at all, and how to prevent it? I wouldn't want to go into comparing uptime of my cpanel and my Plesk server to get the point accross.
 
Back
Top