Wordpress (wp cli) fail
June 24, 2017 8:08 AM Subscribe
I am trying to update my Wordpress installations via wp cli, which has always worked in the past. Today it is failing. Help me? Details within.
My host is Nearlyfreespeech. By default they disable a pile of things such that the end result is I cannot update wordpress via web, only a terminal.
I have a few domains through Google and one also through Nearlyfreespeech.
I've always, without issue, used wp cli to handle updates. This is what the host themselves recommend. Today however, EVERYTHING I do is getting some variant on this:
$ wp core update
Updating to version 4.8 (en_US)...
Downloading update from https://downloads.wordpress.org/release/wordpress-4.8-no-content.zip...
Warning: cURL error 28: Resolving timed out after 10765 milliseconds
Error: cURL error 28: Resolving timed out after 10672 milliseconds
My internet is working fine, since you're seeing this.
At first I thought maybe my internet is just wonky so I tried it again and THEN I got
$ wp core update
Updating to version 4.8 (en_US)...
Error: Another update is currently in progress.
The hell it is? If it's already time out?
THEN I thought well maybe my version is out of date, so I did
$ wp cli update
And THEN I get smacked with
Error: /usr/local/bin/wp is not writable by current user.
Which seems weird because ... that's how you're supposed to do it.
I've tried this on both my Google and NFS domains, so I don't think it's domain specific.
Help would be greatly appreciated. I must say in my paranoia I'm wondering if I got hacked and something funky is going on as a result. I do get regular bouts of bots trying to hack my password, and XML-RPC attacks, which my host informs me of. I'm not afraid to back up and reinstall, if that is the best solution. Thank you in advance.
My host is Nearlyfreespeech. By default they disable a pile of things such that the end result is I cannot update wordpress via web, only a terminal.
I have a few domains through Google and one also through Nearlyfreespeech.
I've always, without issue, used wp cli to handle updates. This is what the host themselves recommend. Today however, EVERYTHING I do is getting some variant on this:
$ wp core update
Updating to version 4.8 (en_US)...
Downloading update from https://downloads.wordpress.org/release/wordpress-4.8-no-content.zip...
Warning: cURL error 28: Resolving timed out after 10765 milliseconds
Error: cURL error 28: Resolving timed out after 10672 milliseconds
My internet is working fine, since you're seeing this.
At first I thought maybe my internet is just wonky so I tried it again and THEN I got
$ wp core update
Updating to version 4.8 (en_US)...
Error: Another update is currently in progress.
The hell it is? If it's already time out?
THEN I thought well maybe my version is out of date, so I did
$ wp cli update
And THEN I get smacked with
Error: /usr/local/bin/wp is not writable by current user.
Which seems weird because ... that's how you're supposed to do it.
I've tried this on both my Google and NFS domains, so I don't think it's domain specific.
Help would be greatly appreciated. I must say in my paranoia I'm wondering if I got hacked and something funky is going on as a result. I do get regular bouts of bots trying to hack my password, and XML-RPC attacks, which my host informs me of. I'm not afraid to back up and reinstall, if that is the best solution. Thank you in advance.
To remove the update lock, maybe try wp option delete core_updater.lock
posted by scruss at 8:38 AM on June 24, 2017
posted by scruss at 8:38 AM on June 24, 2017
Response by poster: Gakiko, you're totally right: it just now fixed itself with zero intervention from me.
Thank you!
posted by aperturescientist at 10:44 AM on June 24, 2017
Thank you!
posted by aperturescientist at 10:44 AM on June 24, 2017
This thread is closed to new comments.
My advice: wait a day or two, try again. Alternatively, post in the official NFS forums.
PS. You're probably not hacked, and if wp cli isn't working properly, reinstalling probably isn't the best idea right now (cause you'll wipe your site and won't be able to install it again untill it starts working!)
posted by gakiko at 8:31 AM on June 24, 2017