• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • 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.

Leftover processes (and lots of 'em!)

S

Spazholio@

Guest
I need to determine just what the heck is going on with my system. It seems like I've seen things like this since we set everything up initially, but now that I have some time, I'd like to dig a little deeper. Can anyone tell me why I have processes running from *days* ago like these (please note - I'm writing this on April 29):

root 12226 11800 0 Apr13 ? 00:00:00 sh -c ( cat /var/cache/logwatch/logwatch.EdVYPX70/secure | /usr/bin/perl /usr/share/logwatch/scripts/services/secure) 2>&1

root 11757 447 0 Apr26 ? 00:00:00 tcp-env -Rt0 /var/qmail/bin/relaylock /var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true /var/qmail/bin/cmd5checkpw /var/qmail/bin/true

I have several (5-10) of each of these, and in some cases, they're over 2 weeks old. Can anyone tell me a) what's going on, and b) how to prevent it in the future?

Thanks!
 
Back
Top