MBARI-WP and dylanjharris are you still experiencing the 502 situation when trying to upgrade Enfold as well? Four of my twenty installs won’t upgrade. Yigit has not responded for a week now since he confirmed the 502 after logging onto our largest site.

Yigit?????

Yigit – One last question please. Why won’t this upgrade work on PHP 5.6 then? I just tried it and got a 502 even with fresh Enfold copy and deleted the advanced-cache.php as well. I didn’t find object-cache.php but did refresh it with WP Engine utility. Why do some sites upgrade nicely on PHP 5.6 and yet the test site only on PHP7? Please advise and thanks.

Yigit –
After updating on the test site with PHP7 after successful update – I get a 502. (See Private)
WP Engine would like to work with the Enfold team because two more companies as shown on this ticket.

We ALL need help. This is happening on my larger sites where 4 of my 20 sites won’t upgrade since APRIL 25th.
Basilis was going to reach out to WP Engine… see prior messages.

Enfold team – Basilis
NOTE: With WP Engine’s info below, Brasilis perhaps you have more info on the TXT file they provided the link for?

Here’s what WP Engine found last night (now a Level 3 support)

WP Engine / Level 2 / Matthew C / Yesterday at 16:20

I’ve been reading over the ticket notes and testing on my end. I think it would be best if we escalate this issue to one of our higher level support techs.

I have gone through and summarized all of the notes here for them regarding where and when we can test on the site, and things we have already tried to give them a starting point.

Please let us know if you receive any more information. We will be in contact with you when we have more on our end!

WP Engine / Level 3 / Brian F / Yesterday at 21:25

Thanks for your patience as we took a deeper look into this.
I believe we’ve made some progress and I have some additional information to share with you. Firstly I believe the underlying cause of the problem is related to an interaction between the database, and the enfold theme.

One other thing I noticed is that when running several wp-cli commands from the staging area, a number of errors were returned which can be seen in this .txt file:
https://wpengine.zendesk.com/attachments/token/DP29ygWQyAD9UOovXsqVHLOL2/?name=output.txt
Although I don’t know for sure if these errors are related to the problem, I think that your development team would definitely want to be aware considering there is a fatal error related to the theme near the bottom of the list.

Another thing I found was that after I purged the transients out of the wels staging site database, I was able to successfully activate the enfold child theme without issues, so doing the same thing on the live database might help, please let us know if we have your permission to test that.

If it does turn out that purging the transients resolves this issue, it could suggest that the enfold theme or the associated child theme could have problems related to transients that should be looked into to avoid similar issues down the road. Please let us know what you think.

—– end

With that said, Brasilis perhaps you have more info on the TXT file they provided the link for?

WP Engine Julio D responded to your engineer’s suggestion MBARI-WP after checking my site’s log’s for the same kill script issue….

Julio D (WP Engine Support)
May 21, 2:43 PM CDT

Thanks for the update. I checked the logs for anything being killed by the long process kills script. I’m seeing a few
/wp-json/posts?type= requests being killed there. Nothing directly with Enfold from the look of it though. I don’t believe the kill script is causing a problem in this case. We could test this by disabling this function on your server. I would first want to test disabling Object cache first since turning off the kill script can cause other problems with the server load. We’d want to monitor the site when the script is off incase we need to enable it again quickly.

Let us know when it would be ok to disable Object Cache and we’ll start there.

I’m getting further with WP Engine / Michael …. I plan to try out his suggestion early AM tomorrow.

———
Michael G (WP Engine Level 2 Support)
May 21, 9:02 AM CDT

Thanks for the clarification. After further review, this looks like this may be tied to object caching. I found a couple of conflicts known to cause timeouts (502) while investigating the site.

The first is the Autoloaded data within the database. Generally, you want this below 800K bytes, and really the lower the better. Your site wels is currently using 868,445 which is 68,445. This is known to cause time outs as Object cache is retrieve, or new items are entered into it. This is the current Autoloaded data:
295323 ws_menu_editor_pro
112152 wp_installer_settings
64376 widget_enhancedtextwidget
63770 rewrite_rules
28200 _ubermenu_menu_item_styles
21742 bwp_minify_detector_log
19252 wp_user_roles
14406 cron
13618 monsterinsights_report_data_overview
12726 wp-mega-menu-settings
12328 avia_options_enfold_child
12236 wysija
11867 wpcf-custom-types
10204 wp-mega-menu-styles
8800 teccc_options
8105 avia_options_enfold
7057 theme_mods_enfold-child
6723 sidebars_widgets
6695 wpseo_titles
6209 otgs_active_components
The second conflict I was able to find was with the plugin the-events-calendar. This plugin uses the function wp_cache_add_non_persistent_groups, which is also known to conflict with object caching. What I’d like to try on wels is toggling off object caching, then have you processes the update once again to see if it completes. If it does, we can leave it disabled to give you some time to optimize the database. This article talks more about database operations: https://wpengine.com/support/database-optimization-best-practices/
If that sounds good to you, definitely let us know, and I can get that disabled for you!
———–
NOTE to MBari-WP – I reached out to conlin last week via email without response.

Still suffering through this upgrade. WP Engine disables the kill script for our main (and largest) site and when pressing the theme update button, the site resources churn and drag to a halt causing 502 error again. They suggest me trying this yet again in the middle of the night. I did notice that the Google Map API was one process hanging. I’m considering to remove the key prior to update. I’ll try anything at this point. Many many hours without light at the end of the tunnel. Your input would be appreciated.

Enfold team, I really need some direction on what to try next. Sounds like MBARI-WP could benefit as well.

I’m able to get the frontend to display of my test site when I delete the child theme, but not the backend admin dashboard which causes 502 errors.

• This reply was modified 6 years, 1 month ago by welswebmaster.

MBARI-WP Thanks. I’ll give that a try today on a copy of the site and report back here. Stay tuned.

Hi Victoria,
YES, I NEED HELP. I’ve spent about a week on this 40+ hours.
Here are answers to your questions.
1. WP Engine.
2. See private data sent to you in my earlier response.
Other WP Engine platform settings: https://wpengine.com/support/platform-settings/

Log errors: http://testwels.wpengine.com/wp-content/uploads/testwels_logs.txt (hosted on WPengine)

• This reply was modified 6 years, 1 month ago by welswebmaster.

An update…
All 5 steps you’ve recommended above were taken and still I get a 502. My guess is that something in my functions.php Child Theme is causing the issue. I’ve reverted to state prior to pressing the Theme Update button. Credentials and test site URL are in private content.

**** IMPORTANT **** I have only a limited time to use this PHP 7 Install. So your expedient response is appreciated. I’m on borrowed time ;-)

Thanks, Guenter. I’ll give it a try and report back.