Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
The APS Catalog has been deprecated and removed from all Plesk Obsidian versions. Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.
I'm running a Plesk Onyx 17.8.11 Update #67 and I have this problem for a while. A scheduled weekly quotacheck process freezes and it gets stuck at 100% cpu usage. Couldn’t find anything in the kb, what could be the problem? Thanks in advance
I can see so many Google results on a hanging quotacheck that I feel unable to solve this. It could be anything. Some issues with the file system for example. Named pipes for example. Maybe a mount that is going to a very slow external location. Whatsoever. Maybe you should consider to ask Plesk support whether they can dig into this deeper to figure out why it happens. However, I don't think it is a Plesk issue. Rather a general issue with the disk or OS.
@fruf, did you try executing the quota check manually, with the similar but perhaps more verbose arguments? Observing that (and the logs) could perhaps tell you more.
I can see so many Google results on a hanging quotacheck that I feel unable to solve this. It could be anything. Some issues with the file system for example. Named pipes for example. Maybe a mount that is going to a very slow external location. Whatsoever. Maybe you should consider to ask Plesk support whether they can dig into this deeper to figure out why it happens. However, I don't think it is a Plesk issue. Rather a general issue with the disk or OS.
The system is a VPS, running on a server with ssd drives so a disk problem seems unlikely. To be honest I’m not really sure what quotacheck does here, I thought it’s related to plesk subscription quotas
@fruf, did you try executing the quota check manually, with the similar but perhaps more verbose arguments? Observing that (and the logs) could perhaps tell you more.