Wordpress toolkit problem on Centos/Cloudlinux6
There seems to be a problem with the stop script of the wp-toolkit.
it doesn't stop the background process scheduler, however, the start script will create more of them
84 1025266 1 0 2020 ? 00:01:16 /usr/bin/sw-engine /usr/local/cpanel/3rdparty/wp-toolkit/bin/run-script scheduled-tasks-executor.php
484 1284709 1 0 2020 ? 00:01:10 /usr/bin/sw-engine /usr/local/cpanel/3rdparty/wp-toolkit/bin/run-script scheduled-tasks-executor.php
484 1408658 1 0 Feb18 ? 00:25:34 /usr/bin/sw-engine /usr/local/cpanel/3rdparty/wp-toolkit/bin/run-script background-tasks-executor.php
484 1408678 1 0 Feb18 ? 00:00:39 /usr/bin/sw-engine /usr/local/cpanel/3rdparty/wp-toolkit/bin/run-script scheduled-tasks-executor.php
484 2160943 1 0 Feb15 ? 00:00:40 /usr/bin/sw-engine /usr/local/cpanel/3rdparty/wp-toolkit/bin/run-script scheduled-tasks-executor.php
484 3229523 1 0 Mar09 ? 00:18:44 /usr/bin/sw-engine /usr/local/cpanel/3rdparty/wp-toolkit/bin/run-script background-tasks-executor.php
484 3229529 1 0 Mar09 ? 00:00:29 /usr/bin/sw-engine /usr/local/cpanel/3rdparty/wp-toolkit/bin/run-script scheduled-tasks-executor.php
484 3490046 1 0 Apr29 ? 00:00:12 /usr/bin/sw-engine /usr/local/cpanel/3rdparty/wp-toolkit/bin/run-script background-tasks-executor.php
484 3490052 1 0 Apr29 ? 00:00:00 /usr/bin/sw-engine /usr/local/cpanel/3rdparty/wp-toolkit/bin/run-script scheduled-tasks-executor.php
484 3490606 1 0 Apr29 ? 00:00:12 /usr/bin/sw-engine /usr/local/cpanel/3rdparty/wp-toolkit/bin/run-script background-tasks-executor.php
484 3490612 1 0 Apr29 ? 00:00:00 /usr/bin/sw-engine /usr/local/cpanel/3rdparty/wp-toolkit/bin/run-script scheduled-tasks-executor.php
484 3514241 1 0 Apr26 ? 00:01:22 /usr/bin/sw-engine /usr/local/cpanel/3rdparty/wp-toolkit/bin/run-script background-tasks-executor.php
484 3514247 1 0 Apr26 ? 00:00:02 /usr/bin/sw-engine /usr/local/cpanel/3rdparty/wp-toolkit/bin/run-script scheduled-tasks-executor.php
484 3514672 1 0 Apr26 ? 00:01:23 /usr/bin/sw-engine /usr/local/cpanel/3rdparty/wp-toolkit/bin/run-script background-tasks-executor.php
484 3514678 1 0 Apr26 ? 00:00:02 /usr/bin/sw-engine /usr/local/cpanel/3rdparty/wp-toolkit/bin/run-script scheduled-tasks-executor.php
484 3712792 1 0 Feb17 ? 00:26:14 /usr/bin/sw-engine /usr/local/cpanel/3rdparty/wp-toolkit/bin/run-script background-tasks-executor.php
484 3712799 1 0 Feb17 ? 00:00:40 /usr/bin/sw-engine /usr/local/cpanel/3rdparty/wp-toolkit/bin/run-script scheduled-tasks-executor.php
484 4174131 1 0 Feb17 ? 00:25:55 /usr/bin/sw-engine /usr/local/cpanel/3rdparty/wp-toolkit/bin/run-script background-tasks-executor.php
484 4174138 1 0 Feb17 ? 00:00:40 /usr/bin/sw-engine /usr/local/cpanel/3rdparty/wp-toolkit/bin/run-script scheduled-tasks-executor.php
The start dates correspond to when a new wp-toolkit was received via yum. Part of the update is a start-stop:
10 User wp-toolkit may run the following commands on this host:
11 (ALL) NOPASSWD: ALL
12 Stopping sw-cp-serverd: [ OK ]
13 Starting sw-cp-serverd: [ OK ]
14 Install WHM Plugin
15 whm-wp-toolkit registered
The stop processing seems to be faulty and leaves running processes of possibly previous script versions on the server. This may be related to the server load problem cause by wp-toolkit that I posted before this thread,
Please sign in to leave a comment.
Comments
0 comments