Segfault PHP-FPM7

When browsing around, does it usually happen somewhere on the way through the checkout or other pages that does not have much to do with the store/cart?

I’ve been browsing without adding products or entering the cart and still it happens.

I’ve just installed my first docker environment and managed to install a similar docker container with nginx and php-fpm7 (unfortunately it was PHP 7.1 and not PHP 7.0). In the current state I was unable to reproduce this error, and the unittest that was run with EComPHP (which is the library that handles the SoapClient in this case) also managed to run without errors.

I’m using a simpler image from https://hub.docker.com/r/richarvey/nginx-php-fpm/ and I guess that version does not reflect your environment very good ??

The SOAP part of the plugin is, in the current public version, based on a older version of wsdl2phpgenerator and the wsdl-files can be found under the PLUGIN_PATH/rbwsdl. All functions are the passed through a library called EComPHP (stored under the PLUGIN_PATH/classes directory). This way to handle the web services became a bit obsolete and we’re working on a newer version that don’t need to go through a bunch of wsdl-stubs. It’s in develop-mode right now but can, if you want to test that version too, be downloaded from git at https://bitbucket.org/resursbankplugins/resurs-bank-payment-gateway-for-woocommerce/src/8f5a099e10480b5f4842bbe3f8d83530a9f97477/?at=develop%2F2.1.0

One other question is also quite interesting to look at: Did you manage to configure the plugin? If you did, which of the flows did you choose? Resurs Checkout is mostly based on rest-services, rather than SOAP, so if there is an environment issue here, that might work better while testing? However, it’s still quite weird that the segfault occurs, even if you’re not going through the store.

It’s a bit tricky because i myself did not configure this enviroment or the WooCommerce settings, since the Gateway plugin doesnt seem to have it’s own settings i don’t really know where to check.

Do you want me to try to reproduce a Docker Enviroment that is as close to ours and send it to you?

It’s a bit tricky to reproduce this environment otherwise.

Sure, it would be very interesting to see what’s causing this ??

Besides from this and the stackexchange-thread I’ve created a smaller local issue at https://resursbankplugins.atlassian.net/browse/WOO-180 too, to make followups.

You can find the test environment here:

https://github.com/frazr/Segfault-Test

Thanks!

I initiated the installation earlier today, and now I’ve run the first tests in the environment. Surprisingly, the plugin started – and worked as it should. However, I only run the standard plugins right now (the plugin, woocommerce 3.1.2, and nothing more than this). Do you have more plugins installed, in case there’s conflicts between other plugins and ours that might need a fix?

I’ve found some notices about undefined indexes that should probably be suppressed, so I’ll check as soon as I can if this has been fixed in the current develop version, or if we should dispatch a new version for this only. There was a few new notices, that I did not recognize from before (“session_start(): Cannot send session cache limiter – headers already sent”). During the installation of wordpress I also noticed some other errors (A 30 sec timeout that came out from nowhere, before the plugins was installed).

The docker environment – how is it with memory limits and such? Right now, I run on a machine that has 32 gig of ram. I have experienced out of memory issues on a few platforms before, that runs wordpress on 4 gig or less. The worst I’ve ever seen, was when I installed a VPS via CloudVPS and OpenStack, where nothing worked as soon as the memory limit was exceeded. There was some kind of memory leak that made the webserver consume more and more memory, for each reload of the page that was done and when the server went out of memory it crashed completely.

Yes on that site we have quite a few plugins installed: https://hastebin.com/wawapukola.sm

The docker container does not have any memory limits defined as it is today, it shouldn’t have something to do with limits since we’re running multiple wordpress sites on a container similar to the one i posted and only this single site is giving us trouble.

Okay, sounds weird but the webserver has no issue here i believe. There’s just this single php-fpm instance that keeps on dumping the core, checking now 5 core dumps in the last 6 minutes, imagine how many there’s in a day that i have to manually clean up ??

May have found the issue, perhaps not linked to your plugin directly just that your plugin triggers a bug in PHP.

https://bugs.php.net/bug.php?id=71662

Sounds interesting. We’ll keep this issue available in our JIRA tracker for a while, so if you manage to find out which parts it could be that triggers this we’d be happy to get your feedback on it. However, if this issue is more bound to what version of PHP that runs, it might be a quite small problem too, since it then might be fixable by upgrade. I’ll also keep the segfault environment, just in case, if we can figure out something else that triggers this.