PHP Fatal error: Uncaught RuntimeException:

  • Resolved buildblog

    (@buildblog)


    1 year, 1 month ago

    Hi,

    I was automatically being logged out of the WP dashboard whenever I tried to click on anything. i.e. I logged into the dashboard. As soon as I tried to do something, I was automatically logged out.

    I looked at the error_log and saw this:

    PHP Fatal error: Uncaught RuntimeException: Unable to release actions from claim id 0. in /home/kendfost/public_html/wp-content/plugins/wpforms-lite/vendor/woocommerce/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php:1128

    I deleted the WooCommerce plugin via file manage in my hosting account and the issue was resolved.

    I re-added the WooCommerce plugin and the issue came back.

    I was trying to use version 9.8.1.

    My hosting compnay asked me todelete all failed scheduled actions which I did.

    The issue continued to happen.

    I now have delete the WooCommerce plugin (as well as other WooCommerce related plugins: WooCommerce Paypal Payments and add-to-cart-direct-checkout-for-woocommerce – they were also causing the issue).

    Can you help?

    Thanks.

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

Viewing 5 replies - 1 through 5 (of 5 total)
  • Ahir Hemant

    (@hemant-ahir)

    1 year, 1 month ago

    Hi @buildblog

    Have you recently migrate your site from one server to another ? If so please check below points:
    I understand that you’re experiencing an issue with the Action Scheduler in WooCommerce. This issue might be caused by corrupted data or incomplete migration. To resolve this issue, you can try the following steps:

    1. Go to your WordPress Dashboard > WooCommerce > Status > Scheduled Actions. Use the “Clear” button to remove all the actions in the list. This may resolve the issue if there’s a problem with the scheduled actions.
    2. Ensure that the migration process was completed correctly and all the files and database content were transferred successfully. Double-check your settings and make sure the site URL and other configuration options are correctly set to the new domain.
    3. In your WordPress Dashboard, go to Settings > Permalinks, and click “Save Changes” without making any actual changes to the permalink settings. This will refresh the permalink structure for the new domain, which might help resolve the issue.

    If it doesn’t work Could you please share a copy of your site’s System Status? You can find it via WooCommerce > Status. Select “Get system report” and then “Copy for support”. Once you’ve done that, paste it here in your response.


    Another solution might work:
     /tmp dir on the server was full preventing MySQL to perform any proper writes and reads resulting in the error shown.

    Thanks
    Ahir Hemant

    Zee

    (@doublezed2)

    1 year, 1 month ago

    Hello buildblog,

    Thank you for contacting WooCommerce support.

    I understand the issue occurs when you reinstall WooCommerce, you’re immediately logged out of the dashboard.

    May I ask if this issue is happening when only WooCommerce is active alongside a default theme like Twenty Twenty-Five? Also, I’m curious why you removed WooCommerce when the error trace points to the WPforms-Lite plugin’s use of the Action Scheduler.

    To assist you better, please share your System Status Report. You can find it under WooCommerce > Status. Paste the report at https://pastebin.com and share the link here.

    Looking forward to your response. 🙂

    Thread Starter buildblog

    (@buildblog)

    1 year, 1 month ago

    Thaks for replying. I decided to restore the site from a previous backup and all is now working. I think perhaps some databases got corrupted or something like that.

    Thanks again.

    Mahfuzur Rahman

    (@mahfuzurwp)

    1 year, 1 month ago

    Hi @buildblog,

    You’re very welcome, and I’m glad to hear restoring the backup resolved the issue! It does sound like there may have been some database corruption involved, especially with Action Scheduler-related tasks.

    If anything else comes up or if the issue reappears, feel free to reach out. We’re here to help. Wishing you smooth sailing with your site!

    LovingBro (woo-hc)

    (@lovingbro)

    1 year, 1 month ago

    We haven’t heard back from you in a while, so I’m going to mark this as resolved – we’ll be here if and/or when you are ready to continue.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘PHP Fatal error: Uncaught RuntimeException:’ is closed to new replies.