• Resolved TadeasKula

    (@tadeaskula)


    Hello,
    we have already gone through https://adtribes.io/help-my-feed-processing-is-stuck and all the threads here. My feeds are stuck after moving to a different server and my hosting Cloudways says everything on server level is fine. Ive enabled logs logging, our domain is displayed at the top, can you please help?

    With wp crontrol i can see only woosea_cron_hook, ive disabled it multiple times, buts it doesnt create more events. Could this be a problem?

    Wp-Cron enabled. Batch size also enabled with 400 value.

    Our site has 30k products, but that hasnt been a problem anytime before the transfer and this is a stronger server.

    • This topic was modified 2 years, 8 months ago by TadeasKula.
    • This topic was modified 2 years, 8 months ago by TadeasKula.
    • This topic was modified 2 years, 8 months ago by TadeasKula.
    • This topic was modified 2 years, 8 months ago by TadeasKula.

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

Viewing 15 replies - 1 through 15 (of 22 total)
  • Hi,

    Thanks for using our plugin and reaching out to us.

    Migrating your website and feed configuration is probably the main reason for this. A lot of things can go wrong with that and our plugin saves a lot of its settings and feed configurations in databases. Migrating our plugin is probably not going to work.

    I would advice you to start from scratch. So remove all previous configured feeds, remove our plugin completely and do a fresh install. It is probably a lot faster then tracking down what might have happened during the migration that caused this.

    Thread Starter TadeasKula

    (@tadeaskula)

    Ive tried that also, but it just doesnt work. 🙁 Dont know what to do.

    Thread Starter TadeasKula

    (@tadeaskula)

    Can I somehow share the logs with you?

    Perhaps your new server has some stricter restrictions in terms of allowed CPU usage and/or maximum allowed execution times.

    Did you already check out the WooCommerce fatal error logs of the last couple of days to see if there is anything in there that might indicate the plugin ran into one of those restrictions? This is where you can find those WooCommerce fatal error logs: https://docs.woocommerce.com/document/finding-php-error-logs/

    Thread Starter TadeasKula

    (@tadeaskula)

    Server: We are on a stronger server. We went from Digital Ocean to Vultr High Frequency and in sence of performence its better.

    Logs: There are no error logs for Product Feed Pro. Where is your plugin saving the log?

    I am not referring to logs from our plugin but the general WooCommerce fatal error logs of the last couple of days. https://docs.woocommerce.com/document/finding-php-error-logs/

    Thread Starter TadeasKula

    (@tadeaskula)

    Yes yes, i know. Nothing that connects with your plugin.

    It doesn’t have to refer to our plugin, the name of it most likely isn’t in the error logs. Are there any maximum execution time errors or maximum CPU usage errors in the logs?

    Thread Starter TadeasKula

    (@tadeaskula)

    They are not :/

    Then we are a bit out of options I am afraid. What happens when you configure a complete new feed, does that work correctly?

    Thread Starter TadeasKula

    (@tadeaskula)

    So what to do when i deactivate and remove plugin, do fresh install and feeds are still there? I deleted them, but it feels like your plugin is not removing the plugin properly. Because the crons are also not refreshing. I still have one visible via wp crontrol and you always say: cronS will refresh. It does not for our site 🙁

    Hi,

    On the “manage feeds” section of our plugin you would need to add &force-clean=true so the URL will look something like this:
    ../wp-admin/admin.php?page=woosea_manage_feed&force-clean=true

    That will get rid of all previously configured feeds.

    Thread Starter TadeasKula

    (@tadeaskula)

    I did that right now again, but again no luck.

    Also i always get this – could it be a problem? (In your log)

    [no_found_rows] => 1

    And the problem still remains, it gets stuck in few percentages..

    could it be a problem? (In your log)

    –> No, that is not related.

    Can you list the cron hooks that start all start with woosea_ in your cron hooks list?

    Thread Starter TadeasKula

    (@tadeaskula)

    Only this one: woosea_cron_hook

Viewing 15 replies - 1 through 15 (of 22 total)
  • The topic ‘Feed creation stuck’ is closed to new replies.