• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

CPU load after upgrade to 9.3

P

PedroD

Guest
Hello everyone,

On the 23rd of January I upgraded my Debian base Plesk to 9.3, I noticed since the upgrade the CPU load rose up 25% on average. After monitoring the server services I noticed most of this was caused by qmail. This might be a bug... is someone else experiencing something like this?

See attached stats from watchdog:

stats-graph-month.png -> monthly activity, spiked on the 23rd when I upgraded
stats-graph-24h.png -> the CPU load is back to normal after stopping qmail service.
 

Attachments

  • stats-graph-month.png
    stats-graph-month.png
    7.8 KB · Views: 6
  • stats-graph-24h.png
    stats-graph-24h.png
    7.3 KB · Views: 6
Duh... problem persists, qmail insists on choking on its own queue, this was not happening before version 9.3 :( ...me and my versionitis...

Every time a message gets stuck in the queue it keeps increasing the CPU load processes, for now the only solution I found is to disable qmail altogether.

~# /var/qmail/bin/qmail-qstat
messages in queue: 9
messages in queue but not yet preprocessed: 0
~# /var/qmail/bin/qmail-qread
1 Feb 2010 10:45:55 GMT #20988226 6708360 <postmaster@####.com> bouncing

I even created the email postmaster@####.com with the hope I'd receive the messages and break the loop, but no success. Any thoughts?
 
Back
Top