Symptoms
-
Checking WordPress updates going to WordPress > Updates > Clicking on Check for Updates fails with the following message:
PLESK_ERROR: Task is not responding: id=XX, pid=XXX, type=ext-wp-toolkit-mass-check-updates
-
With Plesk debug mode enabled, the following error is shown in
/var/log/plesk/panel.logfile:CONFIG_TEXT: DEBUG [util_exec] [9411d2388e8e19d5a692cebc1ad026bb-0] Starting: filemng sysuser exec /var/www/vhosts/example.com/httpdocs timeout 60 /opt/plesk/php/7.1/bin/php -d safe_mode=off -d display_errors=off -d opcache.enable_cli=off -d open_basedir= -d error_reporting=341 -d max_execution_time=60 -c /var/www/vhosts/system/example.com/etc/php.ini /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/php/boot-fs.php --path=/var/www/vhosts/example.com/httpdocs --no-color wpt-cron event reschedule wp_maybe_auto_update +2 day, stdin:
DEBUG [panel] Execute hook Modules_WpToolkit_Backup_Domain::backup
ERR [1] ERROR: escapeshellarg(): Input string contains NULL bytes (functions.php:1209)
ERR [panel] Task is not responding: id=1600, pid=29568, type=ext-wp-toolkit-mass-check-updates
Cause
This is a Plesk bug with ID #EXTWPTOOLK-3376 which will be fixed in future Plesk updates.
Resolution
Until the fix will become available, the following workaround is available:
-
Change the password for the WordPress administrator that it contained numbers and characters with utf8 encoding only: WordPress ToolKit > Select instance > [Setup]
Note: The WordPress instance can be identified by the domain shown in the panel.log file, this is described in the symptoms section.
Comments
11 comments
Was trying to clone an old development site (created back in 2016) over to it's production domain. I was running into a similar issue. The Copying Files step would not complete. After resetting the administrator's credentials the migration completed!
--
CharlieMPK - Systems Administrator
MPK Network Services
Hello CharlieMPK
Glad to hear this helped.
Also for anyone finding this to be a challenge and wanting a quick way to resolve. We detached all of our wordpress instances and scanned for them again (took a few tries) then highlighted them all since it also scanned for updates and did an update opposed to scan for updates which it's now working on. :) ENJOY
Sorry, one last note: The updates were successful however the wordpress instance is not showing the correct version of wordpress installed in the wordpress toolkit. It might show for some but a good handful of the sites are showing 5.1 even though they are updated to the latest version available. We can check that by logging into any individual site to see the current version is actually 5.3.2 but reported in toolkit as 5.1
Hi Tech01, thanks for sharing that workaround. Could you open a support ticket with us in order to troubleshoot that issue with Wordpress version?
Submitted ticket, however we were eventually referred back to this original article for support. .....
Hello Tech01
In such cases feel free to reopen support tickets.
The ticket was reopened from our side.
The problem is that it is a known issue. The known issue thread told me to open a ticket. I opened ticket, some changes were made but we still have the same issue as the article here where we cannot mass update all the wordpress instances. This is a HUGE security risk that needs to be patched. We have a number of Wordpress instances that are likely out of date and need to be updated. Updating them individually would take way too long so we kindly request this issue be given the highest priority for resolution in the next plesk update.
Tech01
Thank you for the clarification and feedback.
Plesk Development team is collecting the information about reoccurring issues.
However, the precise ETA is to be available later.
when can we expect this bug to be fixed?
Hello Tech01
There's still no WA available.
For now, please, use the proposed workaround.
Please sign in to leave a comment.