Issue once updated to WordPress 4.9.5

Anonymous

#171295

We’ve upgraded the site 4.9.5: Whenever I publish a post or do any database-altering task, I get a 502 Bad Gateway message instead of a success message. When I refresh it seems like it has been successfully altered. This was not happening with 4.9.4, however, we did have some issues getting the database tables installed initially.

http://alec-dev-aldrich-advisors.pantheonsite.io/

Happy to reply privately with login credentials.

Anonymous

#171305

here is some feedback from the pantheon engineer. We tested every plugin and the issue only arises when Search & Filter Pro is enabled:

As I check on your php-fpm log, PHP is sigfaulting. Here’s the portion of your log.

[06-Apr-2018 22:23:36] WARNING: [pool www] child 15446 exited on signal 11 (SIGSEGV) after 591.942726 seconds from start
[06-Apr-2018 22:23:36] NOTICE: [pool www] child 24318 started
[06-Apr-2018 22:23:44] WARNING: [pool www] child 23595 exited on signal 11 (SIGSEGV) after 75.070535 seconds from start
[06-Apr-2018 22:23:44] NOTICE: [pool www] child 24373 started
[06-Apr-2018 22:23:44] WARNING: [pool www] child 15447 exited on signal 11 (SIGSEGV) after 599.975879 seconds from start
[06-Apr-2018 22:23:44] NOTICE: [pool www] child 24379 started
PHP is segfaulting, meaning its failing internally in an unpredictable way without returning a fatal error because execution doesn’t get far enough to produce a stack trace.

These are really hard to diagnose because PHP can’t return a stack trace to tell you what is happening, you typically have to dig in really deep with XDebug to get anything useful to debug: http://stackoverflow.com/questions/13079513/how-do-i-diagnose-this-php-segmentation-fault

I’d also suggest getting a local copy of the site running Kalabox or lando if you haven’t already (https://www.kalabox.io or http://devwithlando.io/). It will help with debugging issues if you need to dig deep with Xdebug, etc.

Hopefully that helps and please let us know if you have further questions!

Anonymous

#171402

Update on this:

I have discovered that the 502 issue comes into play when the widely supported popup maker analytics plugin is activated: https://wppopupmaker.com/extensions/

I have a suspicion that these two plugins are jockeying for use of background caching simultaneously, or that Search & Filter Pro is trying to cache / archive the popup content type which doesn’t have an archive, while popup maker is trying to analyze the analytics on it. Is there anyway to make the popups taxonomy invisible to S&F Pro?

Ross Moderator

#171529

Hi Alec

I have another couple of users’ with similar issues to this.

Thanks for the info so far, and hopefully will be tackling this shortly.

I’ll come back to you with any questions / info.

Thanks

Ross Moderator

#171607

This reply has been marked as private.

[Author]

Posts