Issue latest wordpress update broke plesk's wp_cli and now an update to plesk broke plesk

[LIcon]

I updated wordpress last night for one of my websites and it is now showing "HTTP Error 500" in browsers.

I went into Plesk and on the page for that domain...
https://(MY IP ADDRESS):8443/smb/wordpress/detail/id/4
I saw this error text...

{"err_code":10001,"err_message":"This does not seem to be a WordPress install.\nPass --path=`path\/to\/wordpress` or run `wp core download`."} PHP Notice: Undefined variable: exit in /usr/share/plesk-wp-cli/php/class-wp-cli.php on line 623 PHP Notice: Undefined variable: exit in /usr/share/plesk-wp-cli/php/class-wp-cli.php on line 625 PHP Warning: include(/var/www/vhosts/[MY DOMAIN].com/httpdocs/wp-includes/version.php): failed to open stream: No such file or directory in /usr/share/plesk-wp-cli/php/WP_CLI/Runner.php on line 597 PHP Warning: include(): Failed opening '/var/www/vhosts/[MY DOMAIN].com/httpdocs/wp-includes/version.php' for inclusion (include_path='/usr/share/plesk-wp-cli/vendor/phpunit/php-token-stream:/usr/share/plesk-wp-cli/vendor/phpunit/phpunit-mock-objects:/usr/share/plesk-wp-cli/vendor/phpunit/php-code-coverage:/usr/share/plesk-wp-cli/vendor/phpunit/phpunit:/usr/share/plesk-wp-cli/vendor/symfony/yaml:.:') in /usr/share/plesk-wp-cli/php/WP_CLI/Runner.php on line 597 {"err_code":10002,"err_message":"WP-CLI needs WordPress 3.7 or later to work properly. The version currently installed is .\nTry running `wp core download --force`."} PHP Notice: Undefined variable: exit in /usr/share/plesk-wp-cli/php/class-wp-cli.php on line 623 PHP Notice: Undefined variable: exit in /usr/share/plesk-wp-cli/php/class-wp-cli.php on line 625 {"err_code":10001,"err_message":"This does not seem to be a WordPress install.\nPass --path=`path\/to\/wordpress` or run `wp core download`."} PHP Notice: Undefined variable: exit in /usr/share/plesk-wp-cli/php/class-wp-cli.php on line 623 PHP Notice: Undefined variable: exit in /usr/share/plesk-wp-cli/php/class-wp-cli.php on line 625 PHP Warning: include(/var/www/vhosts/[MY DOMAIN].com/httpdocs/wp-includes/version.php): failed to open stream: No such file or directory in /usr/share/plesk-wp-cli/php/WP_CLI/Runner.php on line 597 PHP Warning: include(): Failed opening '/var/www/vhosts/[MY DOMAIN].com/httpdocs/wp-includes/version.php' for inclusion (include_path='/usr/share/plesk-wp-cli/vendor/phpunit/php-token-stream:/usr/share/plesk-wp-cli/vendor/phpunit/phpunit-mock-objects:/usr/share/plesk-wp-cli/vendor/phpunit/php-code-coverage:/usr/share/plesk-wp-cli/vendor/phpunit/phpunit:/usr/share/plesk-wp-cli/vendor/symfony/yaml:.:') in /usr/share/plesk-wp-cli/php/WP_CLI/Runner.php on line 597 {"err_code":10002,"err_message":"WP-CLI needs WordPress 3.7 or later to work properly. The version currently installed is .\nTry running `wp core download --force`."} PHP Notice: Undefined variable: exit in /usr/share/plesk-wp-cli/php/class-wp-cli.php on line 623 PHP Notice: Undefined variable: exit in /usr/share/plesk-wp-cli/php/class-wp-cli.php on line 625 PHP Notice: Use of undefined constant minor - assumed 'minor' in /usr/share/plesk-wp-cli/php/WP_CLI/Runner.php(996) : eval()'d code on line 69 PHP Warning: require(/var/www/vhosts/[MY DOMAIN].com/httpdocs/wp-includes/version.php): failed to open stream: No such file or directory in /usr/share/plesk-wp-cli/php/wp-settings-cli.php on line 26 PHP Fatal error: require(): Failed opening required '/var/www/vhosts/[MY DOMAIN].com/httpdocs/wp-includes/version.php' (include_path='/usr/share/plesk-wp-cli/vendor/phpunit/php-token-stream:/usr/share/plesk-wp-cli/vendor/phpunit/phpunit-mock-objects:/usr/share/plesk-wp-cli/vendor/phpunit/php-code-coverage:/usr/share/plesk-wp-cli/vendor/phpunit/phpunit:/usr/share/plesk-wp-cli/vendor/symfony/yaml:.:') in /usr/share/plesk-wp-cli/php/wp-settings-cli.php on line 26


I looked to see if Plesk needed to be updated, and initiated an update from v12 to v12.5, which resulted in errors (below). The error message instructed me to contact technical support.


Installation started in background
Checking whether the package dependencies are resolved.
Installing packages
sw-engine-fpm (pid 1213) is running...
Stopping psa... Stopping Plesk engine pool manager: sw-engine-fpm.
done
-- Warning: Skipping the data of table mysql.event. Specify the --events option explicitly.
===> Cumulative APS controller database (apsc) upgrade has been started.
===> Cumulative upgrade of APS controller database has been completed.
===> Cumulative Plesk database upgrade (revertable stage) has been started.
===> Preparing Plesk database upgrade (revertable stage).
Stopping psa... Stopping Plesk engine pool manager: sw-engine-fpm.
done
===> Cumulative upgrade of Plesk database (revertable stage) has been completed.
===> Plesk database scheme upgrade has been started.
Applying migrations from: /opt/psa/bootstrapper/pp12.5.30-bootstrapper/migrations/
===> Plesk database scheme upgrade has been completed.
Reading package lists...
Building dependency tree...
Reading state information...
The following packages were automatically installed and are no longer required:
sw-libboost-date-time1.54.0 sw-libboost-thread1.54.0
sw-libboost-serialization1.54.0
Use 'apt-get autoremove' to remove them.
Suggested packages:
procmail postfix-mysql postfix-pgsql postfix-ldap sasl2-bin dovecot-common
resolvconf postfix-cdb mail-reader ufw postfix-doc
The following packages will be REMOVED:
plesk-mail-qc-driver* psa-qmail* psa-qmail-rblsmtpd*
The following NEW packages will be installed:
libcommon-sense-perl libjson-xs-perl libjson0 liblua5.1-0 plesk-engine
plesk-mail-pc-driver plesk-migration-operability-check plesk-release postfix
postfix-pcre psa-courier-unicode python-dnspython
sw-libboost-iostreams1.55.0 sw-libboost-program-options1.55.0
sw-libboost-regex1.55.0 sw-libboost-serialization1.55.0
sw-libboost-thread1.55.0 sw-libmilter
The following packages will be upgraded:
libapache2-mod-aclr2-psa libapache2-mod-bw libapache2-mod-fcgid-psa
libapache2-mod-sysenv-psa libaps libpam-plesk plesk-base plesk-completion
plesk-core plesk-courier-imap-driver plesk-dns-bind-driver plesk-l10n
plesk-librdbmspp plesk-lmlib plesk-management-node plesk-platform-runtime
plesk-service-node-utilities plesk-skins plesk-web-hosting plesk-wp-cli
pp-sitebuilder psa psa-autoinstaller psa-courier-authlib psa-courier-imap
psa-firewall psa-libxml-proxy psa-locale-base-en-us psa-mail-driver-common
psa-migration-agents psa-migration-manager psa-php5-configurator
psa-phpmyadmin psa-phppgadmin psa-proftpd psa-pylibplesk psa-spamassassin
psa-updates psa-vhost psa-zendframework sw-cp-server sw-engine sw-libpoco
sw-rsync wpb-core wpb-designs-00 wpb-designs-01 wpb-designs-03
wpb-designs-04 wpb-designs-05 wpb-designs-07 wpb-designs-09 wpb-designs-12
wpb-designs-14 wpb-designs-20 wpb-headers
56 upgraded, 18 newly installed, 3 to remove and 41 not upgraded.
Need to get 312 MB of archives.
After this operation, 68.2 MB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
liblua5.1-0 libjson0 libcommon-sense-perl libjson-xs-perl postfix
postfix-pcre python-dnspython
E: There are problems and -y was used without --force-yes
Error: An error occurred on attempt to install packages.
Attention! Your software might be inoperable.
Please contact product technical support.

When I try to go to the Plesk control panel I am seeing "502 Bad Gateway" "nginx"

The server is running Debian 6.0.10

 

[Bitpalast]

Some thoughts on this:

WARNING: The following packages cannot be authenticated!
liblua5.1-0 libjson0 libcommon-sense-perl libjson-xs-perl postfix
postfix-pcre python-dnspython
E: There are problems and -y was used without --force-yes
Error: An error occurred on attempt to install packages.

can be caused by outdated keys that the signature of the packages is tested against. Verification fails, and as the installation routine does not force an install upon such failures, the installation fails. You can try to update the key on Debian using these commands:

sudo apt-key update
sudo apt-get update

Then run the Plesk upgrade installation again. Now that the keys are updated, Plesk autoinstaller should also run.

The "502 Bad Gateway" is only a symptom of Apache not running. It is not running, because the panel and the associated services have been stopped before the upgrade. As an emergency procedure to bring customer websites back online you could maybe try to start Apache manually. It is unlikely that this will not start even though the panel is in a bad state.