Operational Issues with WordPress Toolkit WP site UPDATE functions on Multiple Servers

[daedparrotsoftware]

I'm having operational problems with WordPress Toolkit UPDATE functions.
Does not matter how many times I try to run an UPDATE scan in WordPress toolkit
there is usually 2 problems:

1) it never finds all the updates on all sites (if I login to sites they DO have updates needed)
[this problem ALWAYS occurs - finds some but NOT all updates needed]

2) it gives errors on updating THEMES on a large number of sites VERY Frequently.

This happens even though ALL THE SITES ARE CLONES of a template site (which DOES update)

It does NOT do this on the same sites, and not every time.
ONLY 6 WP sites on subdomains being managed (note - update scan on 6 sites takes 8 min)

===it shows ERRORS like:

The following errors have occurred while updating WordPress instance #1 ('WEBSITEDOMAIN'): - Unable to update theme 'thrive-theme`2.6.2`1`', details: {NO details]

OR

Unable to update theme THEMENAME from WordPress instance #15 ('WEBSITEDOMAIN'): Asset 'THEMENAME' with version '2.6.1' not found in WordPress instance #15 ('WEBSITEDOMAIN')

OR occasionally (3 times total over 200 Update/Update scan attempts):

Request to backend API failed with error: Request failed with status code 400


AFTER seeing these errors:

• MANUALLY logging into the WordPress sites and running Update there works perfectly.
  (Finds updates NOT found by WP Toolkit and updates everything)
• Updating using the WP management plugin MainWP also works perfectly

---

Server:
Plesk Obsidian Web PRO Edition version 18.0.36 on a DEDICATED server
WordPress Toolkit version: 5.5.1-5279
CentOS Linux 7.9.2009 (Core)
Dual Xeon 32 Core Processors with 128G Ram 4TB SSD drives

I also already tried detaching website and scan all instances again, but same problem!
As well as things like removing themes and plugins then re-installing
There are NO unused plugins or themes on ANY site
Rest API IS available

We also have the same problem/errors on OTHER servers - 3rd Party hosted such as Hostgateor. Hostm. etc. - with same version of Plesk and the WP Toolkit.

After 3 months of these issues, same errors but different sites, plugins. themes each time, I did report this as a possible BUG in the UPDATE SCAN & UPDATE functions

Thanks for your help

Sid B.

 

[weltonw]

Have you tried contacting Plesk support?

 

[daedparrotsoftware]

Yes. Since our Plesk, on all servers, comes as part of the hosting (they call it 'reseller' licenses) including our dedicated box, they won't do ANY support - not even a bug report - they sent us to the forum. I did file a bug report here. A couple of other people also reported same/similar issue over the last 2 months on the forum, but as yet they have not received a reply.

I am a bit more disappointed by their approach to "support" than I am by the performance issues of their software. We develop and sell software too, and have resellers, but we support people who have our software no matter where they got it or how they pay/paid for it.

Fortunately for Plesk, people on the forum do usually respond/help

Thanks!

Sid

 

[FishWater]

Since our Plesk, on all servers, comes as part of the hosting (they call it 'reseller' licenses)

Yeah this is a bummer. Plesk wants us to buy a support license if we get the license anywhere other than Plesk's site itself (usually the case when you get it along with hosting)

 

[greybeard]

Did this ever get resolved? I operate a shared hosting environment. On one server with 9 distinct WP installs, only one fails (with complete reliability) to allow us to update. It worked when we first established the server a year ago, then it failed. Not a permissions issue as far as I can tell.

The image below demonstrates the behavior I have been accustomed to. Today a new behavior has arisen. Previously there would be failure messages as shown below. Now I am getting a report of success, yet upon completion, all of the same updates (plugins, themes) remain visible, prompting for updates. Running "check for updates" after performing the aforementioned update did not change anything.

 

[greybeard]

I neglected to add this:
OS Microsoft Windows Server 2016
Product Plesk Obsidian
Version 18.0.41 Update #1, last updated on Feb 14, 2022 02:58 AM

While one would not normally do this, we have established FULL permissions to the entire BLOG folder in order to eliminate the concerns that this is a permissions issue.

 

[avatolin]

Try to go to WordPress admin dashboard and update plugins there.

 

[greybeard]

Try to go to WordPress admin dashboard and update plugins there.

Yeah, that fails. If I recall, last time I tried, I got a 503 error and the blog was left in maintenance mode.

At this point I'm left with manual update as the only option which is really inconvenient. Indeed, out of 2 dozen WP installs, I'm not able to manage plugins/themes/etc. at all via the normal WP admin. Clients are not very happy about that.

Thanks.

 

[sds_Novo]

Hi. Let me try to help you.

Which versions of WordPress Toolkit and problem WordPress do you use?

 

[greybeard]

WordPress Toolkit version: 5.9.3-6032
WordPress 5.9.2

Auto-update is turned off

I monitor the WP Toolkit daily, updating anything that comes up. This particular domain has not flagged an update in 2-3 weeks, thus I have not been able to snag an error to post here. However, when I tried to activate auto-updates I got this error. Does this give us any clues?

PHP Warning: PHP Startup: Unable to load dynamic library 'mysql' (tried: C:\Program Files (x86)\Plesk\Additional\PleskPHP74\ext\mysql (The specified module could not be found.), C:\Program Files (x86)\Plesk\Additional\PleskPHP74\ext\php_mysql.dll (The specified module could not be found.)) in Unknown on line 0 Warning: The '0-worker' plugin could not be found. Error: No plugins provided to enable auto-updates for.

I will post here next time a plugin comes up for updating and throws an error.

 

[sds_Novo]

I could not reproduce.
Windows 2016
Plesk 18.0.42 Update #1
WordPress Toolkit version: 5.9.3-6032
WordPress 5.9.2
PHP 7.4.28
All these plugins successfully updated.
Could you try another PHP (for example, 7.3)?

 

[greybeard]

Before I downgrade the PHP version I should note that this (shared) server has 9 WP installs. All but one (due to non-cooperative client) is at WP 5.9.2 and PHP 7.4.28. The holdout client is at WP 5.8.4. Every one of these installs allow updates via toolkit except for the one I am discussing in this thread.

At the present time, the problem site has not reported any pending updates. I'll post here next time a needed update is flagged.

 

[sds_Novo]

Thanks. I asked about PHP only because I tried your case with the same plugins on Windows both 2016, 2019, PHP 7.4.28 and did not see any problem: all plugins updated successfully. From the other hand, you got:
PHP Warning: PHP Startup: Unable to load dynamic library 'mysql' (tried: C:\Program Files (x86)\Plesk\Additional\PleskPHP74\ext\mysql (The specified module could not be found.), C:\Program Files (x86)\Plesk\Additional\PleskPHP74\ext\php_mysql.dll (The specified module could not be found.)) in Unknown on line 0 Warning: The '0-worker' plugin could not be found. Error: No plugins provided to enable auto-updates for.
I've checked these libraries in my PHP74 - there are no ones. And no any PHP warnings.
"I'll post here next time a needed update is flagged" - hope we'll resolve this issue.

 

[greybeard]

@sds_Novo

somehow auto-updates got turned on and it took a few days (after turning off auto-update) for the next update to arrive. Today, wordfence was due for an update, and the process crashed - thus taking down the site. Following is the error that occurred when I tried to run the updater via the WP Toolkit. After this I manually downloaded and installed the files.


Selected items were updated with errors: - Unable to update plugin 'wordfence`7.5.8`1`', details: PHP Warning: PHP Startup: Unable to load dynamic library 'mysql' (tried: C:\Program Files (x86)\Plesk\Additional\PleskPHP74\ext\mysql (The specified module could not be found.), C:\Program Files (x86)\Plesk\Additional\PleskPHP74\ext\php_mysql.dll (The specified module could not be found.)) in Unknown on line 0 PHP Warning: fopen(C:\inetpub\vhosts\domainname.com\httpdocs\blog\wp-content\plugins\wordfence\waf/../languages/wordfence.mo): failed to open stream: No such file or directory in C:\inetpub\vhosts\domainname.com\httpdocs\blog\wp-content\plugins\wordfence\waf\pomo\streams.php on line 185 Warning: fopen(C:\inetpub\vhosts\domainname.com\httpdocs\blog\wp-content\plugins\wordfence\waf/../languages/wordfence.mo): failed to open stream: No such file or directory in C:\inetpub\vhosts\domainname.com\httpdocs\blog\wp-content\plugins\wordfence\waf\pomo\streams.php on line 185 PHP Warning: include(/wfIPWhitelist.php): failed to open stream: No such file or directory in C:\inetpub\vhosts\domainname.com\httpdocs\blog\wp-content\plugins\wordfence\waf\bootstrap.php on line 208 Warning: include(/wfIPWhitelist.php): failed to open stream: No such file or directory in C:\inetpub\vhosts\domainname.com\httpdocs\blog\wp-content\plugins\wordfence\waf\bootstrap.php on line 208 PHP Warning: include(): Failed opening '/wfIPWhitelist.php' for inclusion (include_path='.;.\includes;.\pear') in C:\inetpub\vhosts\domainname.com\httpdocs\blog\wp-content\plugins\wordfence\waf\bootstrap.php on line 208 Warning: include(): Failed opening '/wfIPWhitelist.php' for inclusion (include_path='.;.\includes;.\pear') in C:\inetpub\vhosts\domainname.com\httpdocs\blog\wp-content\plugins\wordfence\waf\bootstrap.php on line 208 PHP Warning: Invalid argument supplied for foreach() in C:\inetpub\vhosts\domainname.com\httpdocs\blog\wp-content\plugins\wordfence\waf\bootstrap.php on line 211 Warning: Invalid argument supplied for foreach() in C:\inetpub\vhosts\domainname.com\httpdocs\blog\wp-content\plugins\wordfence\waf\bootstrap.php on line 211 PHP Warning: include(/wfIPWhitelist.php): failed to open stream: No such file or directory in C:\inetpub\vhosts\domainname.com\httpdocs\blog\wp-content\plugins\wordfence\waf\bootstrap.php on line 208 Warning: include(/wfIPWhitelist.php): failed to open stream: No such file or directory in C:\inetpub\vhosts\domainname.com\httpdocs\blog\wp-content\plugins\wordfence\waf\bootstrap.php on line 208 PHP Warning: include(): Failed opening '/wfIPWhitelist.php' for inclusion (include_path='.;.\includes;.\pear') in C:\inetpub\vhosts\domainname.com\httpdocs\blog\wp-content\plugins\wordfence\waf\bootstrap.php on line 208 Warning: include(): Failed opening '/wfIPWhitelist.php' for inclusion (include_path='.;.\includes;.\pear') in C:\inetpub\vhosts\domainname.com\httpdocs\blog\wp-content\plugins\wordfence\waf\bootstrap.php on line 208 PHP Warning: Invalid argument supplied for foreach() in C:\inetpub\vhosts\domainname.com\httpdocs\blog\wp-content\plugins\wordfence\waf\bootstrap.php on line 211 Warning: Invalid argument supplied for foreach() in C:\inetpub\vhosts\domainname.com\httpdocs\blog\wp-content\plugins\wordfence\waf\bootstrap.php on line 211 PHP Warning: require_once(C:\inetpub\vhosts\domainname.com\httpdocs\blog\wp-content\plugins\wordfence/lib/wordfenceConstants.php): failed to open stream: No such file or directory in C:\inetpub\vhosts\domainname.com\httpdocs\blog\wp-content\plugins\wordfence\wordfence.php on line 114 Warning: require_once(C:\inetpub\vhosts\domainname.com\httpdocs\blog\wp-content\plugins\wordfence/lib/wordfenceConstants.php): failed to open stream: No such file or directory in C:\inetpub\vhosts\domainname.com\httpdocs\blog\wp-content\plugins\wordfence\wordfence.php on line 114 PHP Fatal error: require_once(): Failed opening required 'C:\inetpub\vhosts\domainname.com\httpdocs\blog\wp-content\plugins\wordfence/lib/wordfenceConstants.php' (include_path='.;.\includes;.\pear') in C:\inetpub\vhosts\domainname.com\httpdocs\blog\wp-content\plugins\wordfence\wordfence.php on line 114 Fatal error: require_once(): Failed opening required 'C:\inetpub\vhosts\domainname.com\httpdocs\blog\wp-content\plugins\wordfence/lib/wordfenceConstants.php' (include_path='.;.\includes;.\pear') in C:\inetpub\vhosts\domainname.com\httpdocs\blog\wp-content\plugins\wordfence\wordfence.php on line 114 Error: There has been a critical error on this website. Learn more about troubleshooting WordPress. There has been a critical error on this website.