Completely Uninstall Wordpress Toolkit including users

3.14fingers · Jul 22, 2021

cPRex said:
@3.14fingers - thanks for the feedback on this. I'm going to go through these concerns in order to make sure nothing is missed.

While WordPress Toolkit does get automatically installed for users that had WordPress Manager, it doesn't take over any installations without you specifically telling it to. For example, if you have WordPress already installed, and then install WordPress Toolkit, it won't try and manage the installs unless you perform a scan for them.

I agree - and at this point I believe that is how it behaves. While WPT may see your installation, it won't adjust any configuration files unless you have it manage the WordPress install.

This point doesn't make sense to me since EasyApache is proprietary software and WordPress is distributed freely. WordPress doesn't run at a high enough level to make any adjustments to the EasyApache tools as those are handled by the root user. I do understand the point you're trying to make though, which is why we don't force users to use WPT. The reason we install the software at all is because we are trying to get users off the older WordPress Manager tool.

While there are additional paid features in the tool that require a license, those are the more advanced things like cloning and staging. Installation and management can all be done through the free version. There's also no reason you couldn't keep installing WordPress manually, as we have no plans to block one of the most popular pieces of software in the world to try and force users to pay for that to be installed on cPanel machines.

OK, thanks for the prompt reply. It is appreciated.

I do already know that Wordpress can't ACTUALLY mess with cPanel files. The fact that you say you can see the point I'm trying to make seems to cover that anyway.

I will reinforce though that I reckon cPanel should write a really thorough instruction manual on this new module. This should be over and above any advice described in brief at the Release Notes.

Considering how many people got caught off guard, along with the very long standing expected behaviour of Wordpress installations on cPanel, I'd suggest it should have a section heavily based around, and clearly describing in advance, a concept titled something like 'The Wordpress Toolkit Can Make Unexpected Changes To Your Installation & Configuration'

Sort of like giving a bloke a decent head's up before you hit him in a fight while he's not quite looking!

cPRex · Jul 22, 2021

We do have a docs page here with lots of good information:

WP Toolkit | cPanel & WHM Documentation

This document explains how to install, manage, and upgrade the WP Toolkit.

docs.cpanel.net

Is there something specific you'd like to see added there? If so, I'm happy to get that updated.

Spirogg · Mar 16, 2022

cPRex said:
We do have a docs page here with lots of good information:

WP Toolkit | cPanel & WHM Documentation

This document explains how to install, manage, and upgrade the WP Toolkit.

docs.cpanel.net

Is there something specific you'd like to see added there? If so, I'm happy to get that updated.

I’m sorry to chime in. Today I have a server using Ubuntu and version 102.07 one cPanel account. I saw this WP was installed so I created a dummy test drive and created a WP site. Then deleted the site and went to uninstall Wordpress. I have another forum Post for this - cause I didn’t not see this post here. And what do you know. There are no users using Wordpress cause as I said there is only one account and it’s blank. A dummy account I use to test. And all of a sudden guess what. WP Wordpress toolkit ( cPanel reinstalled wotoolkit on its own tonight. ) and sent me 3 emails that I configured this third party app on my server after I removed it yesterday. So it’s just reinstalling the toolkit after I removed it. I was shocked to see this.
3 emails all the same

The application “whm-wp-toolkit-api” has been registered with AppConfig for the service: whostmgr

Name:	whm-wp-toolkit-api
Service:	whostmgr
Server:	server2..com
ACLs required:	wp-toolkit
System User:	wp-toolkit
URL:	/cgi/wpt/index.php

This notice is the result of a request from “43338._USR_LOCAL_CPANEL_BIN_REGISTER_APPCONFIG__.d4e3aad0.tmp”.
The system generated this notice on Wednesday, March 16, 2022 at 7:03:54 AM UTC.
“AppConfig Registration Notifications” notifications are currently configured to have an importance of “Low”. You can change the importance or disable this type blah blah.

this is intrusive behavior on cPanel. How do we remove this intrusion.
no iser or account had Wordpress or any form Of Wordpress. My domain.com is empty a dummy page blank index.html with nothing in it. So how is it possible that you installed this after I removed it.
I don’t want this on my server you should
Offer it for those who do and not force it on us.
Ap remove is what I did to uninstall it. And tonight it reinstalls itself. WHAT THE ????

come on now. This is getting ridiculous.
You have a doc to remove wp and we do that and the next night you reinstall it ?

this is not right.
Please tell me
How to permanently remove this from
My server. Or should we just remove cPanel completely and go elsewhere ?

Spirogg · Mar 16, 2022

Spirogg said:
I’m sorry to chime in. Today I have a server using Ubuntu and version 102.07 one cPanel account. I saw this WP was installed so I created a dummy test drive and created a WP site. Then deleted the site and went to uninstall Wordpress. I have another forum Post for this - cause I didn’t not see this post here. And what do you know. There are no users using Wordpress cause as I said there is only one account and it’s blank. A dummy account I use to test. And all of a sudden guess what. WP Wordpress toolkit ( cPanel reinstalled wotoolkit on its own tonight. ) and sent me 3 emails that I configured this third party app on my server after I removed it yesterday. So it’s just reinstalling the toolkit after I removed it. I was shocked to see this.
3 emails all the same

The application “whm-wp-toolkit-api” has been registered with AppConfig for the service: whostmgr

Name: whm-wp-toolkit-api
Service: whostmgr
Server: server2..com
ACLs required: wp-toolkit
System User: wp-toolkit
URL: /cgi/wpt/index.php

This notice is the result of a request from “43338._USR_LOCAL_CPANEL_BIN_REGISTER_APPCONFIG__.d4e3aad0.tmp”.
The system generated this notice on Wednesday, March 16, 2022 at 7:03:54 AM UTC.
“AppConfig Registration Notifications” notifications are currently configured to have an importance of “Low”. You can change the importance or disable this type blah blah.

this is intrusive behavior on cPanel. How do we remove this intrusion.
no iser or account had Wordpress or any form Of Wordpress. My domain.com is empty a dummy page blank index.html with nothing in it. So how is it possible that you installed this after I removed it.
I don’t want this on my server you should
Offer it for those who do and not force it on us.
Ap remove is what I did to uninstall it. And tonight it reinstalls itself. WHAT THE ????

come on now. This is getting ridiculous.
You have a doc to remove wp and we do that and the next night you reinstall it ?

this is not right.
Please tell me
How to permanently remove this from
My server. Or should we just remove cPanel completely and go elsewhere ?

I am trying again now removing wp-toolkit-cpanel
to show you what I've done to remove it

Code:

[email protected]:~# apt-get remove wp-toolkit-cpanel
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libaps liblog4cplus libxmlrpc-core-c3 plesk-libboost-1.65 plesk-libboost-date-time1.65 plesk-libboost-filesystem1.65
  plesk-libboost-program-options1.65 plesk-libboost-regex1.65 plesk-libboost-serialization1.65 plesk-libboost-system1.65
  plesk-libboost-thread1.65 plesk-libpoco-1.9.0 plesk-librdbmspp plesk-libstdc++6.3.0 plesk-lmlib plesk-platform-runtime sw-engine
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
  wp-toolkit-cpanel
0 upgraded, 0 newly installed, 1 to remove and 2 not upgraded.
After this operation, 115 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 204028 files and directories currently installed.)
Removing wp-toolkit-cpanel (5.9.3-3400) ...
Removed /etc/systemd/system/multi-user.target.wants/wp-toolkit-background-tasks.service.
Removed /etc/systemd/system/multi-user.target.wants/wp-toolkit-scheduled-tasks.service.
info [uninstall_plugin] Uninstalling from jupiter
info [uninstall_plugin] Removing wp-toolkit from Feature Manager ...
info [uninstall_plugin] Done
info [uninstall_plugin] Scheduling task to update sprites
info [uninstall_plugin] Scheduling task to update API spec files
Plugin uninstalled ok
info [uninstall_plugin] Uninstalling from paper_lantern
info [uninstall_plugin] Scheduling task to update sprites
info [uninstall_plugin] Scheduling task to update API spec files
Plugin uninstalled ok
whm-wp-toolkit unregistered
cpanel-wp-toolkit unregistered
whm-wp-toolkit-api unregistered
Synchronizing state of sw-engine.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable sw-engine
Removed /etc/systemd/system/multi-user.target.wants/sw-engine.service.
[email protected]:~#

Then I ran

Code:

[email protected]:~# apt-get update
Hit:1 http://us.archive.ubuntu.com/ubuntu focal InRelease
Hit:2 http://repo.mysql.com/apt/ubuntu focal InRelease
Hit:3 http://us.archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:4 http://us.archive.ubuntu.com/ubuntu focal-backports InRelease
Hit:5 http://us.archive.ubuntu.com/ubuntu focal-security InRelease
Get:6 http://httpupdate.cpanel.net/ea4-u20-mirrorlist Mirrorlist
Hit:8 https://wp-toolkit.plesk.com/cPanel/build-5.9.3/wp-toolkit-deb ./ InRelease
Hit:9 https://wp-toolkit.plesk.com/cPanel/build-5.9.3/dist-deb-Ubuntu-20.04-x86_64 ./ InRelease
Get:10 http://httpupdate.cpanel.net/cpanel-plugins-u20-mirrorlist Mirrorlist
Hit:12 https://repo.cloudlinux.com/kernelcare-debian/10 stable InRelease
Hit:7 http://103.15.48.49/cpanelsync/repos/Ubuntu/20/EA4 ./ InRelease
Hit:11 http://103.15.48.49/cpanelsync/repos/Ubuntu/20/cpanel-plugins ./ InRelease
Fetched 3,744 B in 2s (1,743 B/s)
Reading package lists... Done

Then I ran

Code:

[email protected]:~# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libaps liblog4cplus libxmlrpc-core-c3 plesk-libboost-1.65 plesk-libboost-date-time1.65 plesk-libboost-filesystem1.65
  plesk-libboost-program-options1.65 plesk-libboost-regex1.65 plesk-libboost-serialization1.65 plesk-libboost-system1.65
  plesk-libboost-thread1.65 plesk-libpoco-1.9.0 plesk-librdbmspp plesk-libstdc++6.3.0 plesk-lmlib plesk-platform-runtime sw-engine
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.

Then I ran

Code:

[email protected]:~# apt autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  libaps liblog4cplus libxmlrpc-core-c3 plesk-libboost-1.65 plesk-libboost-date-time1.65 plesk-libboost-filesystem1.65
  plesk-libboost-program-options1.65 plesk-libboost-regex1.65 plesk-libboost-serialization1.65 plesk-libboost-system1.65
  plesk-libboost-thread1.65 plesk-libpoco-1.9.0 plesk-librdbmspp plesk-libstdc++6.3.0 plesk-lmlib plesk-platform-runtime sw-engine
0 upgraded, 0 newly installed, 17 to remove and 2 not upgraded.
After this operation, 52.4 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 191507 files and directories currently installed.)
Removing sw-engine (2.30.1-ubuntu.20.04.200904.1939) ...
Removing libaps (1.0.10-ubuntu.20.04.200904.1939) ...
Removing plesk-lmlib (0.2.4-ubuntu.20.04.200904.1939) ...
dpkg: warning: while removing plesk-lmlib, unable to remove directory '/run/lock': Device or resource busy - directory may be a mount point?
Removing liblog4cplus (1.2.0.1-ubuntu.20.04.200904.1939) ...
Removing libxmlrpc-core-c3 (1.33.14-8build2) ...
Removing plesk-libboost-thread1.65 (1.65.1-ubuntu.20.04.200630.1129) ...
Removing plesk-libboost-filesystem1.65 (1.65.1-ubuntu.20.04.200630.1129) ...
Removing plesk-libboost-system1.65 (1.65.1-ubuntu.20.04.200630.1129) ...
Removing plesk-libboost-date-time1.65 (1.65.1-ubuntu.20.04.200630.1129) ...
Removing plesk-libboost-program-options1.65 (1.65.1-ubuntu.20.04.200630.1129) ...
Removing plesk-libboost-regex1.65 (1.65.1-ubuntu.20.04.200630.1129) ...
Removing plesk-libboost-serialization1.65 (1.65.1-ubuntu.20.04.200630.1129) ...
Removing plesk-libpoco-1.9.0 (1.9.0-ubuntu.20.04.200904.1939) ...
Removing plesk-librdbmspp (2.0.2-ubuntu.20.04.200904.1939) ...
Removing plesk-platform-runtime (1.0.2-ubuntu.20.04.200904.1939) ...
Removing plesk-libstdc++6.3.0 (6.3.0-ubuntu.20.04.200630.1040) ...
Removing plesk-libboost-1.65 (1.65.1-ubuntu.20.04.200630.1129) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for libc-bin (2.31-0ubuntu9.7) ...
[email protected]:~#

Got This Error and not sure why ?

Code:

 dpkg: warning: while removing plesk-lmlib, unable to remove directory '/run/lock': Device or resource busy - directory may be a mount point?

there is a domain I have setup > 1 account only.. and this has no website, no WP sites nothing
. its blank only in public_html a index.html files with nothing in it.

this account is Setup as a reseller account.

Now we will wait for tomorrow again to see if we get a reinstall of WP as we did tonight ? Which as it showed in above terminal CLI commands it was removed from WHM and cPanel.

cPRex · Mar 16, 2022

If this was a recent installation using 102, which it sounds like it was since you're on Ubuntu, Toolkit gets installed by default during the cPanel installation.

If you see it reinstalled after that work you performed, let me know, but I would not expect that to happen.

Spirogg · Mar 16, 2022

cPRex said:
If this was a recent installation using 102, which it sounds like it was since you're on Ubuntu, Toolkit gets installed by default during the cPanel installation.

If you see it reinstalled after that work you performed, let me know, but I would not expect that to happen.

@cPRex will let you know thanks

Spirogg · Mar 17, 2022

Spirogg said:
@cPRex will let you know thanks

@cPRex Ok well last night it updated by itself again.
so the uninstall Did not work.
Why does this keep reinstalling by itself ?
Thanks

cPRex · Mar 17, 2022

Hmmmmmmm - can you check the install log on the server and let me know what it says there? Usually that's in /var/log/yum.log assuming this is a CentOS system.

Spirogg · Mar 17, 2022

cPRex said:
Hmmmmmmm - can you check the install log on the server and let me know what it says there? Usually that's in /var/log/yum.log assuming this is a CentOS system.

@cPRex here is the email I got below of the reinstall

- Also I Got 3 emails of the same as well. so not sure why it's sending 3 emails about this ?

Operating System:
Ubuntu v20.04.3
Product:
cPanel & WHM v102.0.8 (STANDARD DEVELOPER)

The application “whm-wp-toolkit-api” has registered with AppConfig for the service: whostmgr


Name:	whm-wp-toolkit-api
Service:	whostmgr
Server:	server2
ACLs required:	wp-toolkit
System User:	wp-toolkit
URL:	/cgi/wpt/index.php

You can view all current registered applications here:
2087/scripts6/get_appconfig_application_list

This notice is the result of a request from “13902._USR_LOCAL_CPANEL_BIN_REGISTER_APPCONFIG__.a9d3faa8.tmp”.
The system generated this notice on Thursday, March 17, 2022 at 7:02:10 AM UTC.
“AppConfig Registration Notifications” notifications are currently configured to have an importance of “Low”. You can change the importance or disable this type of notification in WHM’s Contact Manager at: 2087/scripts2/editcontact?event=appconfig
Do not reply to this automated message.

will try and find the logs. for you now.

Spirogg · Mar 17, 2022

cPRex said:
Hmmmmmmm - can you check the install log on the server and let me know what it says there? Usually that's in /var/log/yum.log assuming this is a CentOS system.

@cPRex here is the log ( i think this is the right one ( /var/log/dpkg.log )

I started the log at this time 2am when the update started

Code:

2022-03-17 02:01:10 startup archives unpack
2022-03-17 02:01:11 install libxmlrpc-core-c3:amd64 <none> 1.33.14-8build2
2022-03-17 02:01:11 status triggers-pending libc-bin:amd64 2.31-0ubuntu9.7
2022-03-17 02:01:11 status half-installed libxmlrpc-core-c3:amd64 1.33.14-8build2
2022-03-17 02:01:11 status unpacked libxmlrpc-core-c3:amd64 1.33.14-8build2
2022-03-17 02:01:11 install plesk-libstdc++6.3.0:amd64 6.3.0-ubuntu.20.04.200630.1040 6.3.0-ubuntu.20.04.200630.1040
2022-03-17 02:01:11 status half-installed plesk-libstdc++6.3.0:amd64 6.3.0-ubuntu.20.04.200630.1040
2022-03-17 02:01:12 status triggers-pending man-db:amd64 2.9.1-1
2022-03-17 02:01:12 status unpacked plesk-libstdc++6.3.0:amd64 6.3.0-ubuntu.20.04.200630.1040
2022-03-17 02:01:12 install plesk-platform-runtime:amd64 1.0.2-ubuntu.20.04.200904.1939 1.0.2-ubuntu.20.04.200904.1939
2022-03-17 02:01:12 status half-installed plesk-platform-runtime:amd64 1.0.2-ubuntu.20.04.200904.1939
2022-03-17 02:01:13 status unpacked plesk-platform-runtime:amd64 1.0.2-ubuntu.20.04.200904.1939
2022-03-17 02:01:13 install plesk-librdbmspp:amd64 2.0.2-ubuntu.20.04.200904.1939 2.0.2-ubuntu.20.04.200904.1939
2022-03-17 02:01:13 status half-installed plesk-librdbmspp:amd64 2.0.2-ubuntu.20.04.200904.1939
2022-03-17 02:01:14 status unpacked plesk-librdbmspp:amd64 2.0.2-ubuntu.20.04.200904.1939
2022-03-17 02:01:14 install plesk-libpoco-1.9.0:amd64 1.9.0-ubuntu.20.04.200904.1939 1.9.0-ubuntu.20.04.200904.1939
2022-03-17 02:01:14 status half-installed plesk-libpoco-1.9.0:amd64 1.9.0-ubuntu.20.04.200904.1939
2022-03-17 02:01:15 status unpacked plesk-libpoco-1.9.0:amd64 1.9.0-ubuntu.20.04.200904.1939
2022-03-17 02:01:15 install plesk-libboost-1.65:amd64 <none> 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:15 status half-installed plesk-libboost-1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:15 status unpacked plesk-libboost-1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:16 install plesk-libboost-date-time1.65:amd64 1.65.1-ubuntu.20.04.200630.1129 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:16 status half-installed plesk-libboost-date-time1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:16 status unpacked plesk-libboost-date-time1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:17 install plesk-libboost-system1.65:amd64 1.65.1-ubuntu.20.04.200630.1129 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:17 status half-installed plesk-libboost-system1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:18 status unpacked plesk-libboost-system1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:18 install plesk-libboost-filesystem1.65:amd64 1.65.1-ubuntu.20.04.200630.1129 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:18 status half-installed plesk-libboost-filesystem1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:18 status unpacked plesk-libboost-filesystem1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:19 install plesk-libboost-regex1.65:amd64 1.65.1-ubuntu.20.04.200630.1129 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:19 status half-installed plesk-libboost-regex1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:19 status unpacked plesk-libboost-regex1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:19 install plesk-libboost-serialization1.65:amd64 1.65.1-ubuntu.20.04.200630.1129 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:19 status half-installed plesk-libboost-serialization1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:20 status unpacked plesk-libboost-serialization1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:21 install plesk-libboost-thread1.65:amd64 1.65.1-ubuntu.20.04.200630.1129 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:21 status half-installed plesk-libboost-thread1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:21 status unpacked plesk-libboost-thread1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:22 install libaps:amd64 1.0.10-ubuntu.20.04.200904.1939 1.0.10-ubuntu.20.04.200904.1939
2022-03-17 02:01:22 status half-installed libaps:amd64 1.0.10-ubuntu.20.04.200904.1939
2022-03-17 02:01:22 status unpacked libaps:amd64 1.0.10-ubuntu.20.04.200904.1939
2022-03-17 02:01:23 install liblog4cplus:amd64 1.2.0.1-ubuntu.20.04.200904.1939 1.2.0.1-ubuntu.20.04.200904.1939
2022-03-17 02:01:23 status half-installed liblog4cplus:amd64 1.2.0.1-ubuntu.20.04.200904.1939
2022-03-17 02:01:24 status unpacked liblog4cplus:amd64 1.2.0.1-ubuntu.20.04.200904.1939
2022-03-17 02:01:24 install plesk-libboost-program-options1.65:amd64 1.65.1-ubuntu.20.04.200630.1129 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:24 status half-installed plesk-libboost-program-options1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:24 status unpacked plesk-libboost-program-options1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:25 install plesk-lmlib:amd64 0.2.4-ubuntu.20.04.200904.1939 0.2.4-ubuntu.20.04.200904.1939
2022-03-17 02:01:25 status half-installed plesk-lmlib:amd64 0.2.4-ubuntu.20.04.200904.1939
2022-03-17 02:01:25 status unpacked plesk-lmlib:amd64 0.2.4-ubuntu.20.04.200904.1939
2022-03-17 02:01:26 install sw-engine:amd64 2.30.1-ubuntu.20.04.200904.1939 2.30.1-ubuntu.20.04.200904.1939
2022-03-17 02:01:26 status half-installed sw-engine:amd64 2.30.1-ubuntu.20.04.200904.1939
2022-03-17 02:01:27 status triggers-pending systemd:amd64 245.4-4ubuntu3.15
2022-03-17 02:01:28 status unpacked sw-engine:amd64 2.30.1-ubuntu.20.04.200904.1939
2022-03-17 02:01:28 install wp-toolkit-cpanel:amd64 5.9.3-3400 5.9.3-3400
2022-03-17 02:01:28 status half-installed wp-toolkit-cpanel:amd64 5.9.3-3400
2022-03-17 02:01:49 status unpacked wp-toolkit-cpanel:amd64 5.9.3-3400
2022-03-17 02:01:50 startup packages configure
2022-03-17 02:01:50 configure plesk-libboost-1.65:amd64 1.65.1-ubuntu.20.04.200630.1129 <none>
2022-03-17 02:01:50 status unpacked plesk-libboost-1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:50 status half-configured plesk-libboost-1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:50 status installed plesk-libboost-1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:50 configure plesk-libstdc++6.3.0:amd64 6.3.0-ubuntu.20.04.200630.1040 <none>
2022-03-17 02:01:50 status unpacked plesk-libstdc++6.3.0:amd64 6.3.0-ubuntu.20.04.200630.1040
2022-03-17 02:01:50 status half-configured plesk-libstdc++6.3.0:amd64 6.3.0-ubuntu.20.04.200630.1040
2022-03-17 02:01:50 status installed plesk-libstdc++6.3.0:amd64 6.3.0-ubuntu.20.04.200630.1040
2022-03-17 02:01:50 configure libxmlrpc-core-c3:amd64 1.33.14-8build2 <none>
2022-03-17 02:01:50 status unpacked libxmlrpc-core-c3:amd64 1.33.14-8build2
2022-03-17 02:01:51 status half-configured libxmlrpc-core-c3:amd64 1.33.14-8build2
2022-03-17 02:01:51 status installed libxmlrpc-core-c3:amd64 1.33.14-8build2
2022-03-17 02:01:51 configure plesk-platform-runtime:amd64 1.0.2-ubuntu.20.04.200904.1939 <none>
2022-03-17 02:01:51 status unpacked plesk-platform-runtime:amd64 1.0.2-ubuntu.20.04.200904.1939
2022-03-17 02:01:51 status half-configured plesk-platform-runtime:amd64 1.0.2-ubuntu.20.04.200904.1939
2022-03-17 02:01:51 status installed plesk-platform-runtime:amd64 1.0.2-ubuntu.20.04.200904.1939
2022-03-17 02:01:51 configure liblog4cplus:amd64 1.2.0.1-ubuntu.20.04.200904.1939 <none>
2022-03-17 02:01:51 status unpacked liblog4cplus:amd64 1.2.0.1-ubuntu.20.04.200904.1939
2022-03-17 02:01:51 status half-configured liblog4cplus:amd64 1.2.0.1-ubuntu.20.04.200904.1939
2022-03-17 02:01:51 status installed liblog4cplus:amd64 1.2.0.1-ubuntu.20.04.200904.1939
2022-03-17 02:01:52 configure plesk-libboost-serialization1.65:amd64 1.65.1-ubuntu.20.04.200630.1129 <none>
2022-03-17 02:01:52 status unpacked plesk-libboost-serialization1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:52 status half-configured plesk-libboost-serialization1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:52 status installed plesk-libboost-serialization1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:52 configure plesk-libboost-system1.65:amd64 1.65.1-ubuntu.20.04.200630.1129 <none>
2022-03-17 02:01:52 status unpacked plesk-libboost-system1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:53 status half-configured plesk-libboost-system1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:53 status installed plesk-libboost-system1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:53 configure plesk-libboost-regex1.65:amd64 1.65.1-ubuntu.20.04.200630.1129 <none>
2022-03-17 02:01:53 status unpacked plesk-libboost-regex1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:53 status half-configured plesk-libboost-regex1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:53 status installed plesk-libboost-regex1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:53 configure plesk-libboost-filesystem1.65:amd64 1.65.1-ubuntu.20.04.200630.1129 <none>
2022-03-17 02:01:53 status unpacked plesk-libboost-filesystem1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:53 status half-configured plesk-libboost-filesystem1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:53 status installed plesk-libboost-filesystem1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:53 configure plesk-libboost-program-options1.65:amd64 1.65.1-ubuntu.20.04.200630.1129 <none>
2022-03-17 02:01:53 status unpacked plesk-libboost-program-options1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:53 status half-configured plesk-libboost-program-options1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:54 status installed plesk-libboost-program-options1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:55 configure plesk-libboost-date-time1.65:amd64 1.65.1-ubuntu.20.04.200630.1129 <none>
2022-03-17 02:01:55 status unpacked plesk-libboost-date-time1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:55 status half-configured plesk-libboost-date-time1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:55 status installed plesk-libboost-date-time1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:55 configure plesk-libpoco-1.9.0:amd64 1.9.0-ubuntu.20.04.200904.1939 <none>
2022-03-17 02:01:55 status unpacked plesk-libpoco-1.9.0:amd64 1.9.0-ubuntu.20.04.200904.1939
2022-03-17 02:01:55 status half-configured plesk-libpoco-1.9.0:amd64 1.9.0-ubuntu.20.04.200904.1939
2022-03-17 02:01:55 status installed plesk-libpoco-1.9.0:amd64 1.9.0-ubuntu.20.04.200904.1939
2022-03-17 02:01:55 configure plesk-librdbmspp:amd64 2.0.2-ubuntu.20.04.200904.1939 <none>
2022-03-17 02:01:55 status unpacked plesk-librdbmspp:amd64 2.0.2-ubuntu.20.04.200904.1939
2022-03-17 02:01:55 status half-configured plesk-librdbmspp:amd64 2.0.2-ubuntu.20.04.200904.1939
2022-03-17 02:01:56 status installed plesk-librdbmspp:amd64 2.0.2-ubuntu.20.04.200904.1939
2022-03-17 02:01:56 configure plesk-libboost-thread1.65:amd64 1.65.1-ubuntu.20.04.200630.1129 <none>
2022-03-17 02:01:56 status unpacked plesk-libboost-thread1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:56 status half-configured plesk-libboost-thread1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:56 status installed plesk-libboost-thread1.65:amd64 1.65.1-ubuntu.20.04.200630.1129
2022-03-17 02:01:56 configure libaps:amd64 1.0.10-ubuntu.20.04.200904.1939 <none>
2022-03-17 02:01:56 status unpacked libaps:amd64 1.0.10-ubuntu.20.04.200904.1939
2022-03-17 02:01:56 status half-configured libaps:amd64 1.0.10-ubuntu.20.04.200904.1939
2022-03-17 02:01:56 status installed libaps:amd64 1.0.10-ubuntu.20.04.200904.1939
2022-03-17 02:01:57 configure plesk-lmlib:amd64 0.2.4-ubuntu.20.04.200904.1939 <none>
2022-03-17 02:01:57 status unpacked plesk-lmlib:amd64 0.2.4-ubuntu.20.04.200904.1939
2022-03-17 02:01:57 status half-configured plesk-lmlib:amd64 0.2.4-ubuntu.20.04.200904.1939
2022-03-17 02:01:58 status installed plesk-lmlib:amd64 0.2.4-ubuntu.20.04.200904.1939
2022-03-17 02:01:58 configure sw-engine:amd64 2.30.1-ubuntu.20.04.200904.1939 <none>
2022-03-17 02:01:58 status unpacked sw-engine:amd64 2.30.1-ubuntu.20.04.200904.1939
2022-03-17 02:01:58 status half-configured sw-engine:amd64 2.30.1-ubuntu.20.04.200904.1939
2022-03-17 02:02:02 status installed sw-engine:amd64 2.30.1-ubuntu.20.04.200904.1939
2022-03-17 02:02:02 configure wp-toolkit-cpanel:amd64 5.9.3-3400 <none>
2022-03-17 02:02:02 status unpacked wp-toolkit-cpanel:amd64 5.9.3-3400
2022-03-17 02:02:03 status half-configured wp-toolkit-cpanel:amd64 5.9.3-3400
2022-03-17 02:02:17 status installed wp-toolkit-cpanel:amd64 5.9.3-3400
2022-03-17 02:02:17 trigproc systemd:amd64 245.4-4ubuntu3.15 <none>
2022-03-17 02:02:17 status half-configured systemd:amd64 245.4-4ubuntu3.15
2022-03-17 02:02:18 status installed systemd:amd64 245.4-4ubuntu3.15
2022-03-17 02:02:18 trigproc man-db:amd64 2.9.1-1 <none>
2022-03-17 02:02:18 status half-configured man-db:amd64 2.9.1-1
2022-03-17 02:02:19 status installed man-db:amd64 2.9.1-1
2022-03-17 02:02:19 trigproc libc-bin:amd64 2.31-0ubuntu9.7 <none>
2022-03-17 02:02:19 status half-configured libc-bin:amd64 2.31-0ubuntu9.7
2022-03-17 02:02:19 status installed libc-bin:amd64 2.31-0ubuntu9.7
2022-03-17 04:56:29 startup archives unpack
2022-03-17 04:56:30 upgrade command-not-found:all 20.04.5 20.04.6
2022-03-17 04:56:30 status half-configured command-not-found:all 20.04.5
2022-03-17 04:56:30 status unpacked command-not-found:all 20.04.5
2022-03-17 04:56:30 status half-installed command-not-found:all 20.04.5
2022-03-17 04:56:31 status unpacked command-not-found:all 20.04.6
2022-03-17 04:56:31 upgrade python3-commandnotfound:all 20.04.5 20.04.6
2022-03-17 04:56:31 status half-configured python3-commandnotfound:all 20.04.5
2022-03-17 04:56:32 status unpacked python3-commandnotfound:all 20.04.5
2022-03-17 04:56:32 status half-installed python3-commandnotfound:all 20.04.5
2022-03-17 04:56:33 status unpacked python3-commandnotfound:all 20.04.6
2022-03-17 04:56:35 startup packages configure
2022-03-17 04:56:35 configure python3-commandnotfound:all 20.04.6 <none>
2022-03-17 04:56:35 status unpacked python3-commandnotfound:all 20.04.6
2022-03-17 04:56:35 status half-configured python3-commandnotfound:all 20.04.6
2022-03-17 04:56:36 status installed python3-commandnotfound:all 20.04.6
2022-03-17 04:56:36 configure command-not-found:all 20.04.6 <none>
2022-03-17 04:56:36 status unpacked command-not-found:all 20.04.6
2022-03-17 04:56:37 status half-configured command-not-found:all 20.04.6
2022-03-17 04:56:37 status installed command-not-found:all 20.04.6

Thanks for your help as always

Spiro

cPRex · Mar 17, 2022

Do you have WordPress Manager installed at that machine?

Spirogg · Mar 17, 2022

cPRex said:
Do you have WordPress Manager installed at that machine?

I don't see it anywhere, ? this was an fresh install in feb with 102 and Ubuntu

Spirogg · Mar 17, 2022

cPRex said:
Do you have WordPress Manager installed at that machine?

sent you a PM

Spirogg · Mar 17, 2022

cPRex said:
Do you have WordPress Manager installed at that machine?

@cPRex here is the ticket #94426778
thanks

cPRex · Mar 17, 2022

Thanks - I'm following along now.

Spirogg · Mar 18, 2022

cPRex said:
Thanks - I'm following along now.

@cPRex OK we got the answer below and case ID DOC-17759

The WordPress Toolkit was being reinstalled on your server due to a cron job that was still present on your server. This cron job runs at 1AM every day, and performs a reinstall of the WordPress Toolkit if required. You can see here in the logs that this cron ran on your server on both the 16th and 17th of March:
--

Code:

Mar 16 01:00:01 server2 CRON[40375]: (root) CMD (sleep $((1 + RANDOM % 5))h $((1 + RANDOM % 60))m; /usr/local/bin/wp-toolkit update-configuration > /dev/null 2> /dev/null || /usr/local/cpanel/3rdparty/wp-toolkit/bin/wp-toolkit-installer.sh --generate-configs > /dev/null 2> /dev/null; DEBIAN_FRONTEND=noninteractive LANG=C /usr/bin/apt-get --assume-yes --no-reinstall -o Dpkg::Options::="--force-confnew" install "wp-toolkit-cpanel" > /dev/null 2> /dev/null)

--

Code:

Mar 17 01:00:01 server2 CRON[11372]: (root) CMD (sleep $((1 + RANDOM % 5))h $((1 + RANDOM % 60))m; /usr/local/bin/wp-toolkit update-configuration > /dev/null 2> /dev/null || /usr/local/cpanel/3rdparty/wp-toolkit/bin/wp-toolkit-installer.sh --generate-configs > /dev/null 2> /dev/null; DEBIAN_FRONTEND=noninteractive LANG=C /usr/bin/apt-get --assume-yes --no-reinstall -o Dpkg::Options::="--force-confnew" install "wp-toolkit-cpanel" > /dev/null 2> /dev/null)

--
The "sleep" command at the beginning of this gives an offset to this command, but this eventually ran forcing WordPress Toolkit to be installed:
--

Code:

[19:08:17 server2 [email protected] ~]cPs# grep -i -B1 wp-toolkit /var/log/apt/history.log
Start-Date: 2022-03-05 02:01:18
Commandline: /usr/bin/apt-get --assume-yes --no-reinstall -o Dpkg::Options::=--force-confnew install wp-toolkit-cpanel
Upgrade: wp-toolkit-cpanel:amd64 (5.9.2-3345, 5.9.3-3400)
--
Start-Date: 2022-03-15 05:58:08
Commandline: apt remove wp-toolkit-cpanel
Remove: wp-toolkit-cpanel:amd64 (5.9.3-3400)
--
Start-Date: 2022-03-16 02:01:10
Commandline: /usr/bin/apt-get --assume-yes --no-reinstall -o Dpkg::Options::=--force-confnew install wp-toolkit-cpanel
Install: plesk-libboost-date-time1.65:amd64 (1.65.1-ubuntu.20.04.200630.1129, automatic), plesk-libboost-1.65:amd64 (1.65.1-ubuntu.20.04.200630.1129, automatic), plesk-libboost-thread1.65:amd64 (1.65.1-ubuntu.20.04.200630.1129, automatic), plesk-libboost-serialization1.65:amd64 (1.65.1-ubuntu.20.04.200630.1129, automatic), libaps:amd64 (1.0.10-ubuntu.20.04.200904.1939, automatic), plesk-libboost-system1.65:amd64 (1.65.1-ubuntu.20.04.200630.1129, automatic), wp-toolkit-cpanel:amd64 (5.9.3-3400), sw-engine:amd64 (2.30.1-ubuntu.20.04.200904.1939, automatic), plesk-libstdc++6.3.0:amd64 (6.3.0-ubuntu.20.04.200630.1040, automatic), plesk-libboost-program-options1.65:amd64 (1.65.1-ubuntu.20.04.200630.1129, automatic), plesk-libboost-filesystem1.65:amd64 (1.65.1-ubuntu.20.04.200630.1129, automatic), plesk-lmlib:amd64 (0.2.4-ubuntu.20.04.200904.1939, automatic), plesk-libpoco-1.9.0:amd64 (1.9.0-ubuntu.20.04.200904.1939, automatic), plesk-libboost-regex1.65:amd64 (1.65.1-ubuntu.20.04.200630.1129, automatic), libxmlrpc-core-c3:amd64 (1.33.14-8build2, automatic), liblog4cplus:amd64 (1.2.0.1-ubuntu.20.04.200904.1939, automatic), plesk-platform-runtime:amd64 (1.0.2-ubuntu.20.04.200904.1939, automatic), plesk-librdbmspp:amd64 (2.0.2-ubuntu.20.04.200904.1939, automatic)
--
Start-Date: 2022-03-16 03:48:18
Commandline: apt-get remove wp-toolkit-cpanel
Remove: wp-toolkit-cpanel:amd64 (5.9.3-3400)
--
Start-Date: 2022-03-17 02:01:10
Commandline: /usr/bin/apt-get --assume-yes --no-reinstall -o Dpkg::Options::=--force-confnew install wp-toolkit-cpanel
Install: plesk-libboost-date-time1.65:amd64 (1.65.1-ubuntu.20.04.200630.1129, automatic), plesk-libboost-1.65:amd64 (1.65.1-ubuntu.20.04.200630.1129, automatic), plesk-libboost-thread1.65:amd64 (1.65.1-ubuntu.20.04.200630.1129, automatic), plesk-libboost-serialization1.65:amd64 (1.65.1-ubuntu.20.04.200630.1129, automatic), libaps:amd64 (1.0.10-ubuntu.20.04.200904.1939, automatic), plesk-libboost-system1.65:amd64 (1.65.1-ubuntu.20.04.200630.1129, automatic), wp-toolkit-cpanel:amd64 (5.9.3-3400), sw-engine:amd64 (2.30.1-ubuntu.20.04.200904.1939, automatic), plesk-libstdc++6.3.0:amd64 (6.3.0-ubuntu.20.04.200630.1040, automatic), plesk-libboost-program-options1.65:amd64 (1.65.1-ubuntu.20.04.200630.1129, automatic), plesk-libboost-filesystem1.65:amd64 (1.65.1-ubuntu.20.04.200630.1129, automatic), plesk-lmlib:amd64 (0.2.4-ubuntu.20.04.200904.1939, automatic), plesk-libpoco-1.9.0:amd64 (1.9.0-ubuntu.20.04.200904.1939, automatic), plesk-libboost-regex1.65:amd64 (1.65.1-ubuntu.20.04.200630.1129, automatic), libxmlrpc-core-c3:amd64 (1.33.14-8build2, automatic), liblog4cplus:amd64 (1.2.0.1-ubuntu.20.04.200904.1939, automatic), plesk-platform-runtime:amd64 (1.0.2-ubuntu.20.04.200904.1939, automatic), plesk-librdbmspp:amd64 (2.0.2-ubuntu.20.04.200904.1939, automatic)

--
As you can see, the "reinstall" commands that are occurring in the above log match the cron jobs.
--
This cron job is provided by the wp-toolkit-cpanel package:
--

Code:

[19:04:20 server2 [email protected] ~]cPs# dpkg -S /etc/cron.d/wp-toolkit-update
wp-toolkit-cpanel: /etc/cron.d/wp-toolkit-update

--
This cron job is being left in place on your server due to the "apt-get remove" command being used. Per the Ubuntu documentation here: https://manpages.ubuntu.com/manpages/xenial/man8/apt-get.8.html
--
remove

remove is identical to install except that packages are removed instead of installed.
Note that removing a package leaves its configuration files on the system. If a plus
sign is appended to the package name (with no intervening space), the identified
package will be installed instead of removed.

Specifically, this part:
Note that removing a package leaves its configuration files on the system.

When you use 'apt-get remove' configuration files for an installed package are left on the system; a cron job is considered to be a configuration file and so this cron job continues to exist and run.

To resolve this, I ran the following to fully remove the WordPress Toolkit and all its configuration files:

Code:

[19:13:51 server2 [email protected] ~]cPs# apt-get purge wp-toolkit-cpanel
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
wp-toolkit-cpanel*
0 upgraded, 0 newly installed, 1 to remove and 8 not upgraded.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 194180 files and directories currently installed.)
Purging configuration files for wp-toolkit-cpanel (5.9.3-3400) ...

The command "apt-get purge" is defined as follows:

purge
purge is identical to remove except that packages are removed and purged (any
configuration files are deleted too).

Using "purge" will remove the package AND its configuration files. Following this, the cron job was no longer present:

Code:

[19:14:55 server2 [email protected] ~]cPs# cat /etc/cron.d/wp-toolkit-update
cat: /etc/cron.d/wp-toolkit-update: No such file or directory

This will keep the WordPress Toolkit uninstalled on your server, as this cron job was the reason that the WordPress Toolkit was being reinstalled.

Additionally, I have submitted a case to our documentation team with case ID DOC-17759 to update our documentation for WordPress Toolkit here: https://docs.cpanel.net/knowledge-base/cpanel-developed-plugins/wordpress-toolkit/

- I also found that when you go to your cpanel home/user directory

there is this leftover file

Code:

.wp-toolkit-identifier

so I deleted it as well, since I do not want WordPress Toolkit installed on my server.
Now it's almost 2am here and this is the time when my server reinstalled wp toolkit.

so I am waiting to see success

EDIT 5:46am No WordPress Toolkit all gone ...

Thanks to David H. whom helped resolve this and give great in-depth information
Much appreciated David H.

Search

Search

Completely Uninstall Wordpress Toolkit including users

3.14fingers

Member

cPRex

Jurassic Moderator

WP Toolkit | cPanel & WHM Documentation

Spirogg

Well-Known Member

WP Toolkit | cPanel & WHM Documentation

Spirogg

Well-Known Member

cPRex

Jurassic Moderator

Spirogg

Well-Known Member

Spirogg

Well-Known Member

cPRex

Jurassic Moderator

Spirogg

Well-Known Member

Spirogg

Well-Known Member

cPRex

Jurassic Moderator

Spirogg

Well-Known Member

Spirogg

Well-Known Member

Spirogg

Well-Known Member

cPRex

Jurassic Moderator

Spirogg

Well-Known Member