Another plugin update thread

Support
1

I’ve been browsing around and finding people with issues updating plugins, but so far none have been quite what I’m experiencing.

I spun up a new site yesterday using a blueprint we created. It was running WP 4.7.x so I immediately was prompted to update to 4.8. I attempted to do this several times via the dashboard but the install kept hanging. The refresh icon in the Chrome tab on the update page would just spin and spin. I finally just downloaded new WP Core files from wordpress.org and successfully updated that way.

Now I’m having a similar issue with the plugins I have installed with this blueprint. Clicking Update on them starts the update process by adding the .maintenance file to the root directory, and displaying the “Updating” text with the spinning orange arrows on the plugins page. But it just keeps spinning.

I have tried multiple reboots of Flywheel, updated my VirtualBox, and turned off Faster Docker Volumes. Nothing has worked. It sort of seems like maybe a lack of memory issue and it’s just taking FOREVER to unzip the files because I never see an update failed error. But that’s the best guess I have.

I am currently running Flywheel v 2.0.6

Hoping for some help!
Thanks

2

Well I sort of have an update. After about a half hour of waiting for Yoast SEO to update, I finally got an “Update Failed: Internal Server Error” error. So that’s something…

3

Hi Zac,

Can you please check your PHP error log for indications of what went wrong? You can find the logs in the logs folder in the site folder.

4

Hi Clay,

Here’s my fpm log, there is no php error log:

[24-Jul-2017 15:59:30] NOTICE: ready to handle connections
[24-Jul-2017 16:53:28] WARNING: [pool www] child 1233 exited with code 70 after 3019.567960 seconds from start
[24-Jul-2017 16:53:28] NOTICE: [pool www] child 1292 started
[24-Jul-2017 20:01:18] NOTICE: fpm is running, pid 75
[24-Jul-2017 20:01:18] NOTICE: ready to handle connections
[25-Jul-2017 14:04:23] NOTICE: fpm is running, pid 193
[25-Jul-2017 14:04:23] NOTICE: ready to handle connections
[25-Jul-2017 14:06:31] NOTICE: fpm is running, pid 488
[25-Jul-2017 14:06:32] NOTICE: ready to handle connections
[25-Jul-2017 14:13:49] NOTICE: Terminating ...
[25-Jul-2017 14:13:49] NOTICE: exiting, bye-bye!
[25-Jul-2017 14:13:54] NOTICE: fpm is running, pid 877
[25-Jul-2017 14:13:54] NOTICE: ready to handle connections
[25-Jul-2017 14:19:02] NOTICE: fpm is running, pid 568
[25-Jul-2017 14:19:02] NOTICE: ready to handle connections
[25-Jul-2017 15:39:13] NOTICE: fpm is running, pid 539
[25-Jul-2017 15:39:13] NOTICE: ready to handle connections```
5

Also I just checked another site (one I built about a month ago) and the plugins fail to update there as well.

6

Zac,

Are these sites running on the “Preferred” or “Custom” environment?

7

I’m fairly certain they are on “Custom”. Is there a way to check once the project has been created?

The other site I tested is now able to update plugins. I have updated 5 plugins successfully on that site now after turning Faster Docker Volumes back on.

I was able to update Ninja Forms a few minutes ago on the site I started this thread for. So I tried another (Redirection), but now that’s just spinning.

8

The easiest way to check is if there’s a “Dev Mode” toggle in the top-right of the site settings. If there is, then it’s using the Preferred environment.

If it’s Custom, do you see an error.log file in the PHP error log folder?

9

Good to know. This site is using Custom then, based on that.

I don’t see an error.log file in project/logs/php/5.5.38/ only php-fpm.log

10

Any other thoughts on this?

11

After updating VirtualBox and restarting the site I was able to update one plugin. Then tried another and it failed. So I restarted the site again and was able to update another plugin. I tried this twice more with success, so I thought maybe I just needed to restart the site between updates. After trying a fifth plugin I’m now back to a hanging update no matter how many times I restart.

Not really sure how to proceed.

edit: getting “Update Failed: Internal Server Error” now if I wait long enough

12

Turns out I can still update plugins, I have to disable Faster Docker Volumes, restart the site, enable Faster Docker Volumes, restart again, then run the update. This seems to work consistently, I was able to update 5 more plugins with this method.

Hopefully that shines some light for someone to do something.