Starting on October 19, 2021, we will enable single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
To be prepared for this change and to avoid the need to register during your next ticket submission after the change, we encourage you to create an account here before October 19 using the same email address as your current Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account. You will continue to use ZenDesk authentication until we switch over to single-sign-on on October 19th.

Articles in this section

See more

Plesk sw-engine process causes high CPU usage

Avatar
Robert Asilbekov
Updated
Follow
Plesk for Linux kb: technical ABT: Group B

Applicable to:

  • Plesk for Linux

Symptoms

Plesk sw-engine process causes high CPU usage:

# ps aux | grep sw-engine
root 1242 0.0 0.3 348136 28732 ? Ss Jan14 0:14 /usr/bin/sw-engine -c /usr/local/psa/admin/conf/php.ini /usr/local/psa/admin/bin/modules/watchdog/wdcollect -c /usr/local/psa/etc/modules/watchdog/wdcollect.inc.php
root 2315 0.0 0.1 353260 9908 ? Ss Jan14 0:00 sw-engine-fpm: master process (/etc/sw-engine/sw-engine-fpm.conf)
root 3136 0.0 0.3 363840 32028 ? S Jan14 1:00 /usr/bin/sw-engine -c /usr/local/psa/admin/conf/php.ini /usr/lib64/plesk-9.0/psa-health-monitor-notification.php

Plesk UI shows 502 error

Cause

Some sw-engine child processes are stuck and cannot be stopped normally.

Resolution

  1. Connect to the server via SSH.

  2. Stop sw-engine service:

    # service sw-engine stop
    Stopping sw-engine-fpm: [ OK ]

  3. Kill stuck processes:

    # kill -9 <process_ID>

    where <process_ID> are IDs of stuck sw-engineprocesses from ps aux command

  4. Start sw-engine service:

    # service sw-engine start
    Starting sw-engine-fpm: [ OK ]

Additional information

Process sw-engine produces high CPU usage

Comments

5 comments

Sort by Date Votes
  • Avatar
    Bryan Muthig

    What is the long term solution to this problem?  Is there an upgrade available to fix this problem?  Please elaborate on how to prevent this from occurring in the first place.

    0
    Comment actions Permalink
  • Avatar
    Bato Tsydenov

    @Bryan Muthig

    There are various causes why fpm service can get stuck.

    Such issues should be checked individually.

    If you are facing such issue I recommend you submit a Support ticket:

    How to submit a request to Plesk support?

    0
    Comment actions Permalink
  • Avatar
    Alexis

    I have this problem too with Plesk Obsidian Web Admin Edition Version 18.0.17.

    Suddenly at random time, sw-engine hang 100% CPU and crazy high I/O load (I have 10 disks, with several partition, but with atop I see disk usage for all about 70%, something never happen normally, 10% is the maximum). Rester sw-engine correct the problem.

    It's a Plesk script, so this is not normal something like this happen. That kill my website 2 times since yesterday and give me headache. Please, update your script for a protection against this. You can check the activity of sw-engine and restart the service when something not normal happen.

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello @Alexis,

    The described behavior isn't typical and required additional investigation. In case the issue is reproduced with the most recent version of Plesk Obsidian (RC4), this required additional investigation.

    Please, could you submit a request to Plesk support: https://support.plesk.com/hc/en-us/articles/213608509-How-to-submit-a-request-to-Plesk-support-

    0
    Comment actions Permalink
  • Avatar
    Kea

    I have a recurring problem with this.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles