• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • 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.

qmail-smtpd using 100% cpu

S

shalako

Guest
qmail-smtpd has been maxing out our server's cpu for hours, either as a single process or split into multiple processes adding up to 100% cpu usage. Other services are becoming non-responsive.

I've read that qmail-smtpd handles incoming mail. Does this mean we're just being blasted with a lot of mail? I've looked at /var/qmail/queue/local and the dirs aren't very big.

What can I do?
 
Originally posted by shalako
qmail-smtpd has been maxing out our server's cpu for hours, either as a single process or split into multiple processes adding up to 100% cpu usage. Other services are becoming non-responsive.

I've read that qmail-smtpd handles incoming mail. Does this mean we're just being blasted with a lot of mail? I've looked at /var/qmail/queue/local and the dirs aren't very big.

What can I do?
Hi...I'm having this problem too. I've seen several posts on it, but no solutions. So I'm trying to find out if anyone has found a solution.

Thanks,
G
 
I believe we were dealing with a denial-of-service attack on our hosting company. We migrated to a co-lo.
 
This isn't very useful information to go on, but it would suggest that either it is a DoS attack or a spammer is using one of your domains to use a "bounce" attack for spamming.

Steps that you can take are to a) investigate the source IP of the attacks and firewall them, and b) use strace and attach to the qmail-smtpd process to see what is happening <perhaps it is looping>

Good luck.
 
Back
Top