Feed Stuck

Hi,

Thanks for using our plugin and reaching out to us. I have checked your debug.log and it seems that you have enabled the option to only update your feed when a product changes or has been added. Meaning that no updates of your feed will take place when no such changes are measured.

Your Facebook feed successfully updated today. Did you try stopping the processing and manually refreshing your Google feed already?

I only now see the email you send. It seems you are on Siteground who, unfortunately, are notorious for CPU restrictions.

Just to make sure are you on PHP 7.2 or higher?

Sorry – I replied to email.
PHP is 7.3.
I did notice that originally Product feed TXT, Product feed TSV and Product feed logs all showed False.
Now Product feed logs shows true. Not sure if this is relevant.

I changed the feed to only update when necessary to see if that was not part of the problem. However, using the manual update, I can take anything up to 3 days worth of continuously refreshing, disabling, re-enabling to try get the feed through. This afternoon by some luck the feeds do seem to have gone through.

I am afraid this is caused by Siteground.

Sitegrounds shared hosting plans only permit 30sec execution time before returning a php timeout error. Unfortunately, Sitegrounds will not increase execution time and any of their plans, not even their “Go Geek” plan.

The last thing you can do is lower the batch size of our plugin so it will process your product feed in smaller batches and hopefully not reach sitegrounds timeout settings. Can you lower the plugin batch size to 200? This blog post explains how you can lower the batch size: https://adtribes.io/batch-size-configuration-product-feed/

Ok Thanks.

Reply from Siteground
Thank you for the update. The PHP max_execution_time on our servers is 120 seconds and should be more than enough for the execution of any single PHP script. However, we have timeout limitation of 30 seconds in the webservice which is a regular value with most hosting provider’s. In any situation, I was able to trace the errors that you were receiving:

[Mon Dec 07 22:34:24.356508 2020] [core:error] [pid 7804] [client 80.95.15.154:46318] Script timed out before returning headers: admin-ajax.php, referer: https://kiladeals.com/wp-admin/admin.php?page=woo-product-feed-pro%2Fwoocommerce-sea.php&action=edit_project&step=4&project_hash=UKnFF4HaZzTW0m5FTZXu3XF5CqokHIB3&channel_hash=a80023c048bcf50aa70821992617d970

[Mon Dec 07 22:34:27.126719 2020] [:warn] [pid 10193] [client 80.95.15.154:46604] Timeout waiting for output from CGI script /home/sellhou5/public_html/kiladeals/wp-admin/admin-ajax.php, referer: https://kiladeals.com/wp-admin/admin.php?page=woo-product-feed-pro%2Fwoocommerce-sea.php&action=edit_project&step=4&project_hash=UKnFF4HaZzTW0m5FTZXu3XF5CqokHIB3&channel_hash=a80023c048bcf50aa70821992617d970

[Mon Dec 07 22:34:27.126795 2020] [core:error] [pid 10193] [client 80.95.15.154:46604] Script timed out before returning headers: admin-ajax.php, referer: https://kiladeals.com/wp-admin/admin.php?page=woo-product-feed-pro%2Fwoocommerce-sea.php&action=edit_project&step=4&project_hash=UKnFF4HaZzTW0m5FTZXu3XF5CqokHIB3&channel_hash=a80023c048bcf50aa70821992617d970

and they are indeed caused by the Timeout limitation of the webservice. I went ahead and increased this value to 300 seconds for all scripts that were experiencing such timeouts. In case the script timeouts again, this would mean that the PHP max_execution_time value of 120 seconds is being reached. I am afraid that the PHP max_execution_time could not be increased further on our shared hosting servers and in case the process continues to timeout, I would recommend you to consider reducing the batch sizes to appropriate value that would suit the current limitations.

Ok, and does it make a difference. Is your feed processing now?

So far it seems positive – the real test would be when it runs automatically tomorrow.

Alright, let us know if it worked or not.

All running perfectly now. Feeds updating automatically. Thanks.

Perfect, thanks for the heads-up.