• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

logresolvemerge - 100% CPU - is this run by Plesk DailyMaintainence?

theWoosh

Basic Pleskian
Hi,
I am seeing a problem with CPU maxing out at 6.25 am which is when various system cron jobs are being run, by a process logresolvemerge. This appears to be code belonging to AWstats but I can't find any cron job that is triggering it. The only cron job at that time that I cannot analyse is /etc/cron.daily/50plesk-daily which calls /usr/local/psa/admin/plib/DailyMaintainance/script.php, which is encrypted and I cannot see what it is doing....
I would like to at least change parameters so that this job was being done 'nice'ly if it has to be done every morning at all or ideally change awstats config to make it less cpu intensive.
I have Plesk 12.01.18 running on Ubuntu 14.04 LTS. I would be grateful for any help in sorting this out.
Many thanks
 
Back
Top