• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Issue Problems with sw-engine

straddi

Basic Pleskian
I've noticed that the cache in my RAM keeps getting larger and larger at the same time, and the system crashes. The server is no longer accessible from outside. A restart fixes the problem, but it keeps happening again at the same time.

I noticed that the sw-engine causes an enormous server load during this time.
Therefore, I deactivated it and Plesk with service sw-engine stop && service sw-cp-server stop. A query with service sw-engine status shows that it is deactivated. However, it is still apparently active, as shown in the attached image.

This is exactly the time at which the cache starts growing when sw-engine is enabled.
 

Attachments

  • sw-engine.png
    sw-engine.png
    135.8 KB · Views: 6
Could be a number of things. You can try reinstalling the package, in case it's corrupted. Let's check the logs, shall we?

  1. Share /var/log/sw-cp-server/error_log and /var/log/sw-cp-server/sw-engine.log
  2. Install atop and change the interval to 20 secs. Then share a screenshot of the atop logs during the issue.
 
I installed and started Atop

1744875945201.png

and configured as follows

# /etc/default/atop
# see man atoprc for more possibilities to configure atop execution

LOGOPTS=""
LOGINTERVAL=20
LOGGENERATIONS=28
LOGPATH=/var/log/atop

However, only one log file is stored in the path, namely the one from the start of the atop application (atop_20250417)
 
Yes, that's fine. When the issue happens again, open that file with atop as shown in the guide I linked, and go to the timestamp when the problem happened.
 
Back
Top