Skip to main content

Completely Uninstall Wordpress Toolkit including users

mtbwacko
Today's cPanel update included the Wordpress Toolkit. After looking at it we decided we don't want it because it forces our users to pay for premium features to get all the benefits. So I disabled it in Features for our users. But now I see that every single account has the below 'WP_AUTO_UPDATE_CORE' line at the top of their wp-config.php files, placed there by Wordpress Toolkit. First, I resent the fact that a program would alter all of our user's files without any warning. So now I need to safely remove this line from hundreds of Wordpress installations. Is there a way to do this? I am aware of the following command, but I assume this will only remove the toolkit RPM, correct? >rpm -e wp-toolkit-cpanel So how do I safely remove the following line from hundreds of users' wp-config.php file? This just irks me to no end that I have to do this. define('WP_AUTO_UPDATE_CORE', 'minor');// This setting is required to make sure that WordPress updates can be properly managed in WordPress Toolkit. Remove this line if this WordPress website is not managed by WordPress Toolkit anymore.

Comments

95 comments

Date Votes
  • Alongar
    @cPRex I can confirm that WPT installed 'wordpress-backup' and doing a backup via WPT will install copies of the backup in that folder.
    0
  • cPRex Jurassic Moderator
    @rivermobster - I did my testing and couldn't reproduce that on my end. I had a WordPress site and I manually selected the "Discourage search engines from indexing this site" option in WordPress, then clicked the refresh button in WPT (which causes it to re-scan the site) and that was displayed properly. The same thing happens with the "Search engine indexing" option. Is it possible you just need to do the re-scan to let WPT pick up those changes? It doesn't grab that data in real-time, so that's likely where the confusion is.
    0
  • rivermobster
    @rivermobster - I did my testing and couldn't reproduce that on my end. I had a WordPress site and I manually selected the "Discourage search engines from indexing this site" option in WordPress, then clicked the refresh button in WPT (which causes it to re-scan the site) and that was displayed properly. The same thing happens with the "Search engine indexing" option. Is it possible you just need to do the re-scan to let WPT pick up those changes? It doesn't grab that data in real-time, so that's likely where the confusion is.

    Understood. I'll put that on my to-do list and give it a shot. Did you happen to try it with the aftermarket security plug ins and see if the re-scan will pick up those changes? I use All In One WP Security & Firewall if you feel so inclined to try. If not, I get that too. :)
    0
  • cPRex Jurassic Moderator
    I'm kind of afraid to go down that road. If I do it once here, I can just picture someone going "but you tested a custom plugin for rivermobster!" Well, yeah, because I don't want to get thrown in a river! I'm just going to give a more general "we don't test plugins" answer here :D
    0
  • rivermobster
    I'm kind of afraid to go down that road. If I do it once here, I can just picture someone going "but you tested a custom plugin for rivermobster!" Well, yeah, because I don't want to get thrown in a river! I'm just going to give a more general "we don't test plugins" answer here :D

    lol... Understood completely. I'll put that on my to-do list as well. :D
    0
  • theimagehouse
    I am so angry at this Wordpress Toolkit addition to my VPS. Who the hell gave you the right to even add it to my VPS, let alone scan my server and edit my clients config.php file. !!!! I had to answer to my clients why were folders and edits done to their website - THIS IS BLUDDY UNACCEPTABLE - I do not care how YOU feel this Toolkit is beneficial - IT NOT ! Please DO NOT damn install your rubbish on my server without my permission !! I had to manually detach every website (your stupid script is not automatic), and then uninstall. PLEASE PLEASE we don't have time to be cleaning your rubbish okay. @cPanel Dev Team - How the hell can you allow this! and on top of your price increases you want us to pay more for a stupid Toolkit for maintenance! PATHETIC !
    0
  • theimagehouse
    @custer thank you for your reply. Full update, minor update, plugin update etc are all available options of course from within 'Softaculous' which thousands of us already have installed. And please in future, do not alter or edit our clients files without our express permission! It doesn't look good when we have to explain to our clients that although we host their websites, some third party software called "cPanel" has edited them without asking us !!!

    I agree - We should have had an option to install WPT with the update and not being forced on our servers - I hate this !!
    0
  • custer
    There is nothing automatic about that tool. It requires you edit the command line to include the path to the wp-config.php file and then run it, one at a time, for each and every Wordpress installation on the server. Your installation script apparently found and edited every one of them without our intervention. Why are you making it so difficult to uninstall?

    The script can process all sites on a server if you specify the directory that contains all your vhosts instead of specifying the directory of each vhost individually. Let us know if you still have issues with the script.
    0
  • theimagehouse
    The script can process all sites on a server if you specify the directory that contains all your vhosts instead of specifying the directory of each vhost individually. Let us know if you still have issues with the script.

    Will there be an easier way to uninstall in the future? Or at least opt not to have it installed in the first place?
    0
  • Adam Reece | WebBox
    So much has been said already, but I too echo the sentiments of the rightly annoyed cPanel license holders in this thread. It was a totally unacceptable decision to unwittingly install WordPress Toolkit without consent of the server operators.
    @Forrest Ward - your server did not get any Wordpress installations as part of the update. If your server had Wordpress Manager, which has been a cPanel tool for some time, or if you clicked the option to install Wordpress Toolkit during the Feature Showcase, your machine would get Wordpress Toolkit installed. It just gives you the option to install and manage all Wordpress installations more easily. As mentioned earlier in this thread, you can remove the RPM if you don't want the tool on the machine at all.

    Wrong. I manage 9 WHM servers, and did not get asked about this during automatic updates. Most of which are in the "stable" branch until the next LTS is available, though this problem contradicts the meaning of stability. Having not known these plug-ins exist let alone what they are and do I've never opted in to WordPress Manager or WordPress Toolkit. WordPress Manager and WordPress Toolkit are not comparable. The latter suddenly imposes separate licensing restrictions without any prior notice or consent, and blocks clients from routine business. That is why this is a big problem. What exactly gives cPanel the right to modify client WordPress installations without their consent? Nothing. Don't modify our production web applications please. Removing this from our 9 WHM servers (including the hundreds of sites we host) along with dealing with queries about why some unknown software licensing constraint is suddenly in place, is costing us time thus money. Are cPanel going to compensate license holders for commercial time that has been lost correcting this problem? Also let's look at your own documentation: "When you upgrade a server to cPanel & WHM version 92, the nightly cPanel & WHM update process detects whether WordPress Manager is installed on the server. If WordPress Manager is installed, the update process will install WordPress Toolkit." I may appear to be unjustifiably annoyed with this (shambolic) decision but given the time lost and customer applications modified without consent it has to be 100% understood by the cPanel team that this is not an acceptable practice. Someone screwed up bad, and this has damaged our perspective of cPanel's direction along with their reputation. ---- I've run the RPM command to remove this plug-in from infected servers (and yes, this shady installation is an infection), however it only removes the plug-in itself. It does not undo the changes it made to client web applications without our consent. Is there a script from cPanel we can use to clean up their infection from client web applications, or must we go through each WordPress site manually?
    0
  • cPRex Jurassic Moderator
    @adamreece.webbox - you'll see I retracted that statement in a later post about the update. There are details here that will help remove the change:
    0
  • Adam Reece | WebBox
    This script looks like it only modifies infections made to "wp-config.php". On further inspection this infection has also created the following directories/files relative to the home folder:
    • /.wp-toolkit/
    • /.wp-toolkit-identifier
    • /public_html/wp-content/maintenance/
    • /public_html/wp-content/maintenance.php
    • /wordpress-backups/
    Not sure why we need to use a separate process at all. cPanel forced its way into our hosted WordPress sites easily enough, it should be able to see its way out just as easy as it came in. (This is again manual action due cPanel's intrusion costing its customers commercial time.)
    0
  • Adam Reece | WebBox
    Fellow server operators, here is a script for your scrutiny to process all customers you host and purge WP Toolkit from their home folder and individual site HTDOCS directories. Amendments welcome. `chmod 0750 /root/remove-wp-toolkit.sh`
  • Run the script. No modifications are made without your approval. If the output looks good run again with option "--consent" to action the cleaning proposed. @cPanel: You've cost us 2 hours of time today with your infection. If you'd like to compensate us "140+VAT for commercial time lost we can provide you with a link to do that. :)
    • 0
  • kernow
    @ adamreece.webbox Thanks for the script. Its a pity cPanel couldn't be bothered to write this for us. Let us know if they cough up "140+VAT for you, we would like to invoice them as well ;)
    0
  • WorkinOnIt
    Hello all A little late to this dreadfully shambolic party. Like others here, I am very annoyed to find this toolkit thing has been installed without my permission and also affecting my customers. This in fact is actually quite a blow in my confidence with cPanel and WHM. I mean, how can they sanction this kind of action? Will there be more malware coming from the core updates? What's worse, if you want to use the primary features, you have to PAY for it.... on top of all the cPanel price increases, this is another smack in the face. I will be deleting Wordpress Toolkit - Was happy with the old Wordpress manager.
    0
  • 3.14fingers
    Hello Every Wordpress Toolkit Disgruntled Person, Here is my point to cPanel... First of all, I reckon something that meddles with the existing Wordress installs on my servers in this fashion is akin to malware. Number two - If you are going to so rudely interrupt the long standing open-source party over at Wordpress perhaps you would like to first make the installation options very, very clear in advance. And also while you're at it you should probably write a very comprehensive instruction manual.... something like the depth of the beautiful Wordpress codex site. Number three - How would your company and clients feel if Matt Mullenweg and all the good people over at Wordpress wrote a new update that decided it was OK to screw with the EasyApache cPanel files without asking? Seriously, I can't help wondering whether Oakley have decided they are financially jealous of watching Wordpress get so much use on 'their' servers at the same time as being free and open source. Perhaps they think its time to try and corner the cPanel Wordpress users so they can make a free open source piece of software into something that will only run on WHM & Plesk if you pay Oakley some extra bucks. Maybe thats where this is heading. Imagine a future where you get up one day and find out you can no longer even run Wordpress at all on your cPanel, WHM & Plesk servers unless you pay an additional per user price for an extension that enables this wonderful open source software to even be installed at all. Despite the recent price hikes and license changes, I'm sure that's not what they are up to, they probably just want to make your life easier.
    0
  • cPRex Jurassic Moderator
    @3.14fingers - thanks for the feedback on this. I'm going to go through these concerns in order to make sure nothing is missed.
    First of all, I reckon something that meddles with the existing Wordress installs on my servers in this fashion is akin to malware.

    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.
    Number two - If you are going to so rudely interrupt the long standing open-source party over at Wordpress perhaps you would like to first make the installation options very, very clear in advance. And also while you're at it you should probably write a very comprehensive instruction manual.... something like the depth of the beautiful Wordpress codex site.

    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.
    Number three - How would your company and clients feel if Matt Mullenweg and all the good people over at Wordpress wrote a new update that decided it was OK to screw with the EasyApache cPanel files without asking?

    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.
    0
  • Adam Reece | WebBox
    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.

    Unfortunately experience shared in this thread shows that this is just not accurate. Looking at the experience we've had on our WHM servers, and that of other customers complaining in this thread, WP Toolkit did interfere with existing WordPress installations without our consent. I would put money on that plenty of impacted customers didn't even know WP Toolkit existed, let alone installed it intentionally and consented to modifying existing detached WordPress deployments. This did actual damage to the data of multiple of our clients. (Companies frequently get sued for this kind of negligence!) This cost us commercial time to repair, time taken away from other billable work, and I suspect the same for that of other complaints too.
    0
  • cPRex Jurassic Moderator
    @adamreece.webbox - I can't say I've seen that exact behavior. I do know there were issues when the product was first released, but that type of interference should no longer be happening. If you're still seeing that, could you open a ticket with our team so we can investigate?
    0
  • 3.14fingers
    @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!
    0
  • cPRex Jurassic Moderator
    We do have a docs page here with lots of good information:
    0
  • Spirogg
    We do have a docs page here with lots of good information: 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 ?
    0
  • Spirogg
    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 root@server2:~# 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. root@server2:~#
    Then I ran root@server2:~# 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 root@server2:~# 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 root@server2:~# 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) ... root@server2:~#
    Got This Error and not sure why ? 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.
    0
  • cPRex Jurassic Moderator
    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.
    0
  • Spirogg
    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
    0
  • Spirogg
    @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
    0
  • cPRex Jurassic Moderator
    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.
    0
  • Spirogg
    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.
    0
  • Spirogg
    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 2022-03-17 02:01:10 startup archives unpack 2022-03-17 02:01:11 install libxmlrpc-core-c3:amd64 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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
    0
  • cPRex Jurassic Moderator
    Do you have WordPress Manager installed at that machine?
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post