Error during "Running post-install steps" -- `wo` command no longer runnable
See original GitHub issueAfter this failure, the wo command no longer works as intended, throwing this same error whenever wo is run.
[~] wo update
Downloading update script [Done]
updating WordOps, please wait...
Welcome to WordOps install/update script v3.14.0
Installing wo dependencies [OK]
Installing WordOps [OK]
Running post-install steps [OK]
Traceback (most recent call last):
File "/usr/local/bin/wo", line 5, in <module>
from wo.cli.main import main
File "/opt/wo/lib/python3.5/site-packages/wo/__init__.py", line 1, in <module>
__import__('pkg_resources').declare_namespace(__name__)
AttributeError: module 'pkg_resources' has no attribute 'declare_namespace'
WordOps (wo) upgrade to v3.14.0 was succesfull!
Changelog is available on https://github.com/WordOps/WordOps/releases/tag/v3.14.0
System Information
-
lsb_release -a
[~] lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 9.13 (stretch)
Release: 9.13
Codename: stretch
-
wo info
Cannot be run
-
nginx -V
nginx version: nginx/1.18.0 (WordOps Nginx-wo)
built with OpenSSL 1.1.1g 21 Apr 2020 (running with OpenSSL 1.1.1j 16 Feb 2021)
TLS SNI support enabled
configure arguments: --with-cc-opt='-g -O2 -fdebug-prefix-map=/usr/src/packages/BUILD=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -flto -ffat-lto-objects -Wdate-time -D_FORTIFY_SOURCE=2' --with-ld-opt='-Wl,-z,relro -fPIC -flto -ffat-lto-objects' --prefix=/usr/share/nginx --conf-path=/etc/nginx/nginx.conf --http-log-path=/var/log/nginx/access.log --error-log-path=/var/log/nginx/error.log --lock-path=/var/lock/nginx.lock --pid-path=/run/nginx.pid --http-client-body-temp-path=/var/lib/nginx/body --http-fastcgi-temp-path=/var/lib/nginx/fastcgi --http-proxy-temp-path=/var/lib/nginx/proxy --http-scgi-temp-path=/var/lib/nginx/scgi --http-uwsgi-temp-path=/var/lib/nginx/uwsgi --build='WordOps Nginx-wo' --with-debug --with-pcre-jit --with-file-aio --with-threads --with-http_ssl_module --with-http_v2_module --with-http_stub_status_module --with-http_realip_module --with-http_auth_request_module --with-openssl-opt='zlib enable-ec_nistp_64_gcc_128 enable-tls1_3 no-ssl3-method -fPIC' --with-http_addition_module --with-http_geoip_module --with-http_gzip_static_module --with-http_mp4_module --with-http_sub_module --with-http_xslt_module --without-http_memcached_module --add-module=/usr/src/packages/BUILD/debian/modules/headers-more-nginx-module --add-module=/usr/src/packages/BUILD/debian/modules/nginx-auth-pam --add-module=/usr/src/packages/BUILD/debian/modules/nginx-cache-purge --add-module=/usr/src/packages/BUILD/debian/modules/nginx-echo --add-module=/usr/src/packages/BUILD/debian/modules/nginx-upstream-fair --add-module=/usr/src/packages/BUILD/debian/modules/ngx_http_substitutions_filter_module --add-module=/usr/src/packages/BUILD/debian/modules/memc-nginx-module --add-module=/usr/src/packages/BUILD/debian/modules/srcache-nginx-module --add-module=/usr/src/packages/BUILD/debian/modules/HttpRedisModule --add-module=/usr/src/packages/BUILD/debian/modules/redis2-nginx-module --add-module=/usr/src/packages/BUILD/debian/modules/ngx_devel_kit --add-module=/usr/src/packages/BUILD/debian/modules/set-misc-nginx-module --add-module=/usr/src/packages/BUILD/debian/modules/nginx-module-vts --add-module=/usr/src/packages/BUILD/debian/modules/ngx_brotli
-
wo -v
Cannot be run
-
wp cli info --allow-root
[~] wp cli info --allow-root
OS: Linux 4.9.0-17-amd64 #1 SMP Debian 4.9.290-1 (2021-12-12) x86_64
Shell: /bin/bash
PHP binary: /usr/bin/php7.4
PHP version: 7.4.27
php.ini used: /etc/php/7.4/cli/php.ini
MySQL binary: /usr/bin/mysql
MySQL version: mysql Ver 15.1 Distrib 10.5.13-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2
SQL modes: STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION
WP-CLI root dir: phar://wp-cli.phar/vendor/wp-cli/wp-cli
WP-CLI vendor dir: phar://wp-cli.phar/vendor
WP_CLI phar path: /root
WP-CLI packages dir:
WP-CLI global config:
WP-CLI project config:
WP-CLI version: 2.6.0
-
curl -sL git.io/fjAp3 | sudo -E bash -
Here the link to provide in your github issue : <html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>
Issue Analytics
- State:
- Created 2 years ago
- Comments:12
Top Results From Across the Web
npm post-install typings not working correctly - Stack Overflow
when I run npm install in my directory I get an error: 'typings' is not recognized as an internal or external command, operable...
Read more >Error Codes | Yarn - Package Manager
A list of Yarn's error codes with detailed explanations.
Read more >Getting Started - ESBuild
Notice that this uses the esbuild command directly without a relative path. ... The build function runs the esbuild executable in a child...
Read more >Troubleshoot installation issues for Microsoft Defender for ...
An error in installation may or may not result in a meaningful ... If mdatp.service isn't found upon running the previous command, run:....
Read more >Scripts - Composer
Composer fires the following named events during its execution process: ... If the command was run with the --no-dev flag, this variable will...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Not sure if the commands below help.
sudo pip install -U pip setuptools sudo python3 -m pip install -I wordops
I was able to fix it!
This is how:
run these commands:
sudo python3 get-pip.pysudo pip install -U pip setuptoolssudo python3 -m pip install -I wordops(we will see an error message within now triggered output, but it will work nevertheless)wo -vInvalid syntax gone! Things are back to normal.