• 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.

Memory Problems

R

Rempala

Guest
Has anyone noticed any memory problems since the upgrade.
Our server is a Dual 2.8 Xeon with a gig of mem. We host 8 websites on it. but since the upgrade it looks like its running low on mem ( I could be reading it wrong). Under statistics this is what it says -

Total : 1008.04 MB
Used : 878.39 MB
Free : 129.66 MB
Shared : 0 B
Buffer : 139.50 MB
Cached : 390.91 MB
Usage : 87.14%
 
My memory has always run high and it doesn't seem to create a problem. I have 2 GB and it fills up to around 1.7 to 1.9GB.

The only times I start having problems is when it starts raising in the Swap area or the CPU processes begin getting maxed out.

But, memory has always run high on my server with no problems.

If you don't have 4PSA's Server Assistant, then I recommend getting it. It's pretty useful because it provides visuals of memory, cpu, etc usage in daily, weekly, monthly and even yearly graphs.
 
Thats my problem swap is being used and my CPUs are max out 99% of the time.

( I have email support but yet no reply)
 
Its qmail-smtpd doing it.
messages in queue but not yet preprocessed: 3234


[root@wna1 /]# top
22:06:02 up 29 min, 1 user, load average: 6.21, 6.97, 5.52
143 processes: 137 sleeping, 6 running, 0 zombie, 0 stopped
CPU states: cpu user nice system irq softirq iowait idle
total 196.4% 0.0% 3.4% 0.0% 0.0% 0.0% 0.0%
cpu00 98.5% 0.0% 1.4% 0.0% 0.0% 0.0% 0.0%
cpu01 98.0% 0.0% 1.9% 0.0% 0.0% 0.0% 0.0%
Mem: 1032236k av, 591108k used, 441128k free, 0k shrd, 82484k buff
111240k active, 336548k inactive
Swap: 2040244k av, 0k used, 2040244k free 242844k cached


28789 qmaild 25 0 1340 0 R 86.6 0.1 0:14 1 qmail-smtpd
26347 qmaild 25 0 1340 0 R 77.2 0.1 1:29 0 qmail-smtpd
28862 qmaild 22 0 1340 0 R 31.6 0.1 0:00 0 qmail-smtpd
27365 root 16 0 1300 0 R 1.4 0.1 0:00 1 top
28854 qmailr 16 0 1304 4 S 0.9 0.1 0:00 0 qmail-remote
3461 root 16 0 12760 0 S 0.4 1.2 0:03 1 httpd
28837 qmaild 15 0 676 4 S 0.4 0.0 0:00 1 qmail-smtpd
 
Did you ever solve this problem?

Because I have the same one too.

TED
 
I had that problem, because of qmail-scanner, I had to get it out or my server would became unusable in 10 min after started
 
Back
Top