Stop processing

  • Resolved lonewolf70

    (@lonewolf70)


    4 years, 3 months ago

    Hello,

    we test your plugin but have the Problem, that always stops processing the feed at 37%. We proceed a feed with Variations and a filter for a specific Product Name.

    Cronjob is enabled / Wordfence disabled / Cache disabled

    The only cronjob with woosea we have is woosea_cron_hook. PHP Version is 7.4 and the limit is 2048.

    Other Feed Plugis we´ve tested works all without problems. But we want yours, because we find it has the best range of functions.

    Can you help us with these Problem. We don’t know anymore

    Log: https://reitsport-schill.com/wp-content/uploads/woo-product-feed-pro/logs/debug.log

    The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 16 total)
1 2
  • supportadtribes

    (@supportadtribes)

    4 years, 3 months ago

    Hi,

    Thanks for using our plugin and reaching out to us.

    Did you already check your WooCommerce fatal error log of today so you can see if there are errors in there? You should specifically be looking for errors such as maximum execution time error and maximum allowed CPU/memory usage errors.

    This is where you can find these logs:
    https://woocommerce.com/document/finding-php-error-logs/

    Thread Starter lonewolf70

    (@lonewolf70)

    4 years, 3 months ago

    Thanks for your fast reply.

    There are no errors like this for today.

    https://xxxxxxxxxxxxxxx

    • This reply was modified 4 years, 3 months ago by lonewolf70.
    supportadtribes

    (@supportadtribes)

    4 years, 3 months ago

    The link is not working for us?

    Thread Starter lonewolf70

    (@lonewolf70)

    4 years, 3 months ago

    2022/02/03 15:04:09 [error] 14230#14230: *32432 FastCGI sent in stderr: “PHP message: gcp was called incorrectly. Produkteigenschaften sollten nicht direkt abgerufen werden. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_get_refreshed_fragments’), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::get_refreshed_fragments, woocommerce_mini_cart, wc_get_template, include(‘/plugins/woocommerce/templates/cart/mini-cart.php’), apply_filters(‘woocommerce_cart_item_name’), WP_Hook->apply_filters, wc_gzd_cart_product_delivery_time, WC_GZD_Product->get_delivery_time_html, WC_GZD_Product->hide_shopmarks_due_to_missing_price, WC_Product->get_price_html, apply_filters(‘woocommerce_get_price_html’), WP_Hook->apply_filters, ign_gc_pricer->filter_suggested_price, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0” while reading response header from upstream, client: 109.42.115.146, server: reitsport-schill.com, request: “POST /?wc-ajax=get_refreshed_fragments HTTP/2.0”, upstream: “fastcgi://unix:/var/run/wordpress.php-fpm.sock:”, host: “xxxxxxxx”, referrer: “xxxxxxxxxxxxxx
    2022/02/03 14:16:50 [error] 14231#14231: *31392 FastCGI sent in stderr: “PHP message: PHP Warning: php_uname() has been disabled for security reasons in /home/wp/disk/wordpress/wp-content/plugins/woocommerce-gateway-stripe/includes/class-wc-stripe-api.php on line 72” while reading response header from upstream, client: 77.21.253.135, server: reitsport-schill.com, request: “GET /wp-admin/admin.php?page=woosea_manage_feed&debug=true HTTP/2.0”, upstream: “fastcgi://unix:/var/run/wordpress.php-fpm.sock:”, host: “reitsport-schill.com”
    2022/02/03 13:39:56 [error] 14230#14230: *31148 FastCGI sent in stderr: “PHP message: gcp was called incorrectly. Produkteigenschaften sollten nicht direkt abgerufen werden. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_get_refreshed_fragments’), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::get_refreshed_fragments, woocommerce_mini_cart, wc_get_template, include(‘/plugins/woocommerce/templates/cart/mini-cart.php’), apply_filters(‘woocommerce_cart_item_name’), WP_Hook->apply_filters, wc_gzd_cart_product_delivery_time, WC_GZD_Product->get_delivery_time_html, WC_GZD_Product->hide_shopmarks_due_to_missing_price, WC_Product->get_price_html, apply_filters(‘woocommerce_get_price_html’), WP_Hook->apply_filters, ign_gc_pricer->filter_suggested_price, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.PHP message: gcp was called incorrectly. Produkteigenschaften sollten nicht direkt abgerufen werden. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_get_refreshed_fragments’), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::get_refreshed_fragments, woocommerce_mini_cart, wc_get_template, include(‘/plugins/woocommerce/templates/cart/mini-cart.php’), apply_filters(‘woocommerce_cart_item_name’), WP_Hook->apply_filters, wc_gzd_cart_product_delivery_time, WC_GZD_Product->get_delivery_time_html, WC_GZD_Product->hide_shopmarks_due_to_missing_price, WC_Product->get_price_html, apply_filters(‘woocommerce_get_price_html’), WP_Hook->apply_filters, ign_gc_pricer->filter_suggested_price, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.PHP message: gcp was called incorrectly. Produkteigenschaften sollten nicht direkt abgerufen w

    • This reply was modified 4 years, 3 months ago by lonewolf70.
    supportadtribes

    (@supportadtribes)

    4 years, 3 months ago

    Thanks for sharing this but I am not entire sure if this really is the content of your WooCommerce fatal error log? It typically had a different (time) format than the one you just shared. Did you retrieve the log from this page? https://www.dropbox.com/s/dktby2rikvrch86/woo-fatal-error-log.png?dl=0

    Thread Starter lonewolf70

    (@lonewolf70)

    4 years, 3 months ago

    Ah sorry. That was the server error log. There is no fatal-error-log in woo for today. We test your Plugin the last days with the same problem and there isn´t a fatal-error-log for the last days too.

    • This reply was modified 4 years, 3 months ago by lonewolf70.
    supportadtribes

    (@supportadtribes)

    4 years, 3 months ago

    Did you already try lowering the batch size of the plugin? The default batch size is 750 products per batch, try lowering it to 250. See: https://adtribes.io/batch-size-configuration-product-feed/

    Thread Starter lonewolf70

    (@lonewolf70)

    4 years, 3 months ago

    Yes. i checked this yesterday

    • This reply was modified 4 years, 3 months ago by lonewolf70.
    supportadtribes

    (@supportadtribes)

    4 years, 3 months ago

    Ok, we are running a bit out of options here. A bit of a longshot but are you perhaps using some sort of caching mechanism/plugin that could be causing this?

    Also, when the feed is still “processing” you should be seeing more cron hooks that start with woosea. The woosea_cron_hook cannot be the only one, there should be a “batch” one too.

    Thread Starter lonewolf70

    (@lonewolf70)

    4 years, 3 months ago

    We use server caching, no plugin. Caching is deactivated. I refresh the feed processing now and it stand by 1 % since the last 10 Minutes. I have only the woosea_cron_hook with woosea at the beginning

    • This reply was modified 4 years, 3 months ago by lonewolf70.
    supportadtribes

    (@supportadtribes)

    4 years, 3 months ago

    Than I still suspect there is something wrong with your WP-cron.

    When you kick-off the feed manually the first batch of products is being processed. When the first batch is done a new cron hook is created that will execute the next batch of products. This cycle continues until it processed all products.

    In your case the batch cron hooks do not seem to be there / not created. They should look something like this: https://www.dropbox.com/s/ny0k61wtgaifdwj/batch_hooks.png?dl=0

    Are you sure your WP-cron is functioning correctly and/or do you have some security/firewall plugin in place that prevents new cron hooks from getting created?

    Thread Starter lonewolf70

    (@lonewolf70)

    4 years, 3 months ago

    Somtehing new.

    We checked this tonight again.

    At the beginning of the process, we have 3 Cronjobs from woosea

    woosea_create_batch
    woosea_update_project
    woosea_cron_hook

    The processing works always till 36% and than it stops. When it stops, the only cron is woosea_cron_hook. The other ones are away.

    • This reply was modified 4 years, 3 months ago by lonewolf70.
    supportadtribes

    (@supportadtribes)

    4 years, 3 months ago

    Yes, so that does indicate there is an issue with the WP-cron. Not allowing enough new cron hooks to be created. I do see you have > 44k products which is quit a lot of course.

    What you can try is increasing the batch size of the plugin so it processes more products per batch so less batches are needed. Perhaps it is enough to take you to 100% then. The issue with increasing batches is that it might cause the plugin to run into your server configuration limitations (such as CPU/memory limits and so on).

    Can you try increasing the batch size to 1500 (default is 750). This is how you can do so: https://adtribes.io/batch-size-configuration-product-feed/

    Hope this makes a difference?

    Thread Starter lonewolf70

    (@lonewolf70)

    4 years, 3 months ago

    Ok, i test this.

    But i don´t create a feed for all the Products. I generate i feed with the filter for 2 Products with 300 Variations. Can be this the problem?

    Thread Starter lonewolf70

    (@lonewolf70)

    4 years, 3 months ago

    Nothing changes. It stops at 37% again. Unfortunately, I’ll have to look elsewhere. Pity.

    Many thanks for your help.

Viewing 15 replies - 1 through 15 (of 16 total)
1 2

The topic ‘Stop processing’ is closed to new replies.