• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue sw-engine status red

Gernot Schabkar

New Pleskian
hello.
i got 2-3 times a day the cpu alert red for about 20 minutes. this is a fresh server with about 12 abonnements , 15 Domains, 8 cpus and 16gb ram. that shouldnt be?

30023 psaadm 20 0 273232 45664 35708 R 100.0 0.3 0:00.21 sw-engine
30022 psaadm 20 0 273540 46228 35828 R 98.4 0.3 0:00.20 sw-engine
30024 psaadm 20 0 273532 45932 35632 R 98.4 0.3 0:00.20 sw-engine
30025 psaadm 20 0 273248 45504 35524 R 98.4 0.3 0:00.20 sw-engine
30026 psaadm 20 0 272908 45124 35340 R 98.4 0.3 0:00.20 sw-engine

what is going wrong, where to search for solutions?
 
I counted, i got 8 mails a day concerning CPU load with all colors a day.
all with the psaadm user.
the server is doing close to nothing every day , only 5 webhosts. i planned putting 500 on this server, thats not looking good...

Message:
Der Status des Serversystem-Parameters "Services > CPU-Auslastung durch Apache" wurde von "yellow" in "red" geändert.

top - 09:37:23 up 48 days, 18:43, 0 users, load average: 0.15, 0.55, 0.51
Tasks: 222 total, 6 running, 216 sleeping, 0 stopped, 0 zombie
%Cpu(s): 4.1 us, 0.1 sy, 0.0 ni, 95.7 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem: 14402584 total, 13929152 used, 473432 free, 432620 buffers
KiB Swap: 62499836 total, 74116 used, 62425720 free. 11940844 cached Mem

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
30023 psaadm 20 0 273232 45664 35708 R 100.0 0.3 0:00.21 sw-engine
30022 psaadm 20 0 273540 46228 35828 R 98.4 0.3 0:00.20 sw-engine
30024 psaadm 20 0 273532 45932 35632 R 98.4 0.3 0:00.20 sw-engine
30025 psaadm 20 0 273248 45504 35524 R 98.4 0.3 0:00.20 sw-engine
30026 psaadm 20 0 272908 45124 35340 R 98.4 0.3 0:00.20 sw-engine
 
No, not suggesting a downgrade. It was just one possibility for what is causing the high sw-engine load.
 
Do you or customers have any crontab jobs active ("geplante Aufgaben")? Which ones?

I would like to annotate that 16 GB RAM is far too small for the planned 500 domains. I suggest to upgrade to at least 64 MB unless you want to constantly use a swap file. However, this only as a note, it is not causing the sw-engine load.
 
agreed, i can scale it up to 128 gb.
no, nothing in the crontabs yet.
maybe i should mention, that i had tomcat causing some huge cpu loads in the past, but i didnt need it, so i stopped the service.
 
Your best chance to find out what is causing this is to run
# ps -aux | grep sw-engine
while the problem exists. As the issue occurs for a longer period of time, it should be possible to catch the window and look at the process list. It will display more details what commands sw-engine is running at that time. These will probably allow a better insight into what is happening.
 
maybe another hint, or another problem..
im getting every some days the error in my backoffice :
Fehler: Der ModSecurity-Regelsatz konnte nicht aktualisiert werden: DB query failed: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'psa.Configurations' doesn't exist, query was: DESCRIBE `Configurations`
 
I am sorry that I cannot assess the future behavior of the system in this case. There is an obvious defect in your psa database. It can have a severe negative impact on the installation, but it does not necessarily have to.

You can try to
# plesk repair db -y
to fix it. That is pretty safe, because psa database is auto-backed-up during the repair, so it could be re-imported in case things go totally wrong.

Else if you feel unsafe with instructions given in FAQ article opening a support ticket is a good option, too.
 
plesk repair db -y

Checking the Plesk database using the native database server tools .. [OK]

Checking the structure of the Plesk database ........................ [OK]

Checking the consistency of the Plesk database ...................... [OK]

Error messages: 0; Warnings: 0; Errors resolved: 0

didnt do anything..
btw. have many thanks for your help.
 
Back
Top