• We value your experience with Plesk during 2025
    Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025.
    Please take this short survey:

    https://survey.webpros.com/
  • On Plesk for Linux mod_status is disabled on upgrades to improve Apache security.
    This is a one-time operation that occurs during an upgrade. You can manually enable mod_status later if needed.

Issue Hourly cron for Plesk Email Security (email-security/scripts/update-stats.php') generates increased CPU usage after Plesk update to 18.0.74 # 3

mcac

Basic Pleskian
Server operating system version
AlmaLinux 8.10
Plesk version and microupdate number
18.0.74 #3
Hello,
Two days ago, I updated Plesk on two Linux servers to Plesk 18.0.74 #3 during the day. The following night, the two servers started to generate high CPU usage by mariadb every hour. In the processes, I saw that emailsecurity is responsible for this. The cron job starts every hour and generates high utilisation for about 30 minutes or more every hour. The websites are still accessible as normal. Has anyone else had similar problems?
 

Attachments

  • Screenshot 2026-01-07 234310.jpg
    Screenshot 2026-01-07 234310.jpg
    36.5 KB · Views: 4
  • Screenshot 2026-01-07 234212.jpg
    Screenshot 2026-01-07 234212.jpg
    40.4 KB · Views: 4
Hi, @mcac . Our team is currently reviewing the case. I will follow-up with more details as soon as possible. For the time being, what you can do is manually kill the process:

Code:
ps auxf | grep update-stats.php
kill -9 PID
 
Thank you very much for your reply. I have now temporarily changed the cron job from hourly to daily. It will now run once a day at night until a solution is found.
 
We are seeing this issue as well, since Jan 5/6th:

OS: Ubuntu 22.04.5 LTS
Product: Plesk Obsidian 18.0.75

Constant High CPU from the update script, pushing MariaDB to 100% CPU.
 
Thank you all for your patience. The behavior was recognized as a bug with ID EXTPLESK-10100. It is expected for the fix to be introduced in Plesk Email Security 1.6.0, but I cannot provide an ETA on when it will be released. Aside from the previously suggested workaround, our developers suggest creating the following index:

Code:
plesk db -e "CREATE INDEX email ON emailsecurity.stats_accounts (email);"
 
Thats it. With this little patch the script takes only 40 seconds, not 40 minutes. Amazing.
 
Back
Top