Unable to upload media, database does not assign index

Thank you for the feedback and advise.

I’ve tried as suggested, still no luck – even with the plugin mentioned renamed in the plugins folder.

Here is the log output now

[19-Aug-2024 12:34:51 UTC] PHP Notice: Trying to access array offset on value of type null in /home/infantat/public_html/wp-content/plugins/js_composer/include/autoload/vc-shortcode-autoloader.php on line 64 [19-Aug-2024 12:34:51 UTC] PHP Notice: Trying to access array offset on value of type null in /home/infantat/public_html/wp-content/plugins/js_composer/include/autoload/vc-shortcode-autoloader.php on line 64 [19-Aug-2024 12:34:51 UTC] PHP Notice: Trying to access array offset on value of type null in /home/infantat/public_html/wp-content/plugins/js_composer/include/autoload/vc-shortcode-autoloader.php on line 64 [19-Aug-2024 12:34:51 UTC] PHP Notice: Trying to access array offset on value of type null in /home/infantat/public_html/wp-content/plugins/js_composer/include/autoload/vc-shortcode-autoloader.php on line 64 [19-Aug-2024 12:34:51 UTC] PHP Notice: Trying to access array offset on value of type null in /home/infantat/public_html/wp-content/plugins/js_composer/include/autoload/vc-shortcode-autoloader.php on line 64 [19-Aug-2024 12:34:51 UTC] PHP Notice: Trying to access array offset on value of type null in /home/infantat/public_html/wp-content/plugins/js_composer/include/autoload/vc-shortcode-autoloader.php on line 64 [19-Aug-2024 12:34:51 UTC] PHP Notice: Trying to access array offset on value of type null in /home/infantat/public_html/wp-content/plugins/js_composer/include/autoload/vc-shortcode-autoloader.php on line 64 [19-Aug-2024 12:34:53 UTC] PHP Fatal error: Uncaught RuntimeException: Unable to release actions from claim id 0. in /home/infantat/public_html/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php:1040 Stack trace: #0 /home/infantat/public_html/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/ActionScheduler_QueueRunner.php(176): ActionScheduler_DBStore->release_claim(Object(ActionScheduler_ActionClaim)) #1 /home/infantat/public_html/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/ActionScheduler_QueueRunner.php(139): ActionScheduler_QueueRunner->do_batch(25, ‘Async Request’) #2 /home/infantat/public_html/wp-includes/class-wp-hook.php(324): ActionScheduler_QueueRunner->run(‘Async Request’) #3 /home/infantat/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(”, Array) #4 /home/infantat/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #5 /home/infantat/public_html/wp-content/plugins/wp-mail-smtp/vend in /home/infantat/public_html/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php on line 1040 [19-Aug-2024 12:34:53 UTC] PHP Fatal error: Uncaught RuntimeException: Unable to release actions from claim id 0. in /home/infantat/public_html/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php:1040 Stack trace: #0 /home/infantat/public_html/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/ActionScheduler_FatalErrorMonitor.php(52): ActionScheduler_DBStore->release_claim(Object(ActionScheduler_ActionClaim)) #1 /home/infantat/public_html/wp-includes/class-wp-hook.php(324): ActionScheduler_FatalErrorMonitor->handle_unexpected_shutdown(”) #2 /home/infantat/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #3 /home/infantat/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #4 /home/infantat/public_html/wp-includes/load.php(1280): do_action(‘shutdown’) #5 [internal function]: shutdown_action_hook() #6 {main}

Hi, @milesmarshall1969 ???? Based on your last reply, it looks like someone may have shared a previous message (?), but it doesn’t appear to exist anymore. At the risk of providing info you’ve already seen, here are some other topics that may relate to your issue:

• Similar error, ultimately resolved by setting auto_increment to the wp_actionscheduler_claims table: https://www.ads-software.com/support/topic/problem-updating-database/
• Unresolved, but includes several things to test for in determining the underlying cause: https://www.ads-software.com/support/topic/fatal-error-actionscheduler_dbstore-php-2/

The error you’ve shared indicates that WP Mail SMTP is using the Action Scheduler library, so you might be able to get more direct support by logging a report over at WP Mail SMTP’s support forum.

If you’ve looked through those topics but still haven’t tracked down the problem, I would suggest making a backup (if you haven’t already), and making sure that your plugins are all updated to their latest versions. You could disable WP Mail SMTP and install the Action Scheduler plugin directly, then go through Tools > Scheduled Actions to find what could be causing the failure.

thanks Brian
I appreciate you coming back to me.
I’ve tried the following
– installing wooCommerce – isn’t used by site but thought lets put it in place and see; that crashed entire site and I had to do a recovery
– I then tried installing ‘action scheduler’ as suggested, that installed fine, but whenever I try and look at the 4 issues it is reporting, I get this “There has been a critical error on this website.”
– I’ve tried disabling SMTP plugin, no joy there

we are trying to reach out to the theme team to see if they have any ideas.

if you’ve any other ideas, please shout – things getting desperate here

Regards

Miles

main culprit remains here:

[Tue Aug 20 18:23:05.156342 2024] [authz_core:error] [pid 609823:tid 609823] [client 41.185.64.175:52108] AH01630: client denied by server configuration: /home/infantat/public_html/.user.ini
[Tue Aug 20 18:17:43.126377 2024] [lsapi:error] [pid 599751:tid 599751] [client 41.185.64.175:53542] [host https://www.infanta4x4.co.za] Backend fatal error: PHP Fatal error: Uncaught RuntimeException: Unable to release actions from claim id 0. in /home/infantat/public_html/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php:1030\nStack trace:\n#0 /home/infantat/public_html/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/ActionScheduler_FatalErrorMonitor.php(52): ActionScheduler_DBStore->release_claim(Object(ActionScheduler_ActionClaim))\n#1 /home/infantat/public_html/wp-includes/class-wp-hook.php(324): ActionScheduler_FatalErrorMonitor->handle_unexpected_shutdown(”)\n#2 /home/infantat/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)\n#3 /home/infantat/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array)\n#4 /home/infantat/public_html/wp-includes/load.php(1280): do_action(‘shutdown’)\n#5 [internal function]: shutdown_action_hook()\n#6 {main}\n thrown in /home/infantat/public_html/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php on line 1030\n

This shouldn’t be a substitute for inquiring with the WP Mail SMTP’s support forum, but my first instinct is to check the wp_actionscheduler_logs and wp_actionscheduler_claims tables in the database. The first may provide more detail on what’s failing, and the second could reveal a “stuck” item in the queue. Remedial steps in the other referenced forum posts refer to clearing transients and queues (but all presume the UI is working as expected), so by my [perhaps naive? ??] reasoning, if there’s anything in that second table, you could try clearing it.

Hello Brian
I trust you are well.

Ok so I have taken a look at both of these.

wp_actionscheduler_logs -> does give me some items as 'action ignored via Async Request' & 'action ignored via WP Cron' 

wp_actionscheduler_actions -> this had 4 pending items, I deleted those, and then tried uploading an image to which it added 3 new pending items

1. wpforms_process_forms_locator_scan - pending
2. wpforms_email_summaries_fetch_info_blocks - pending
3. wpforms_admin_notifications_update - pending

image failed to upload 

checking in the server error log, I see the following, none of those my IP, seems to me to be preventative action (perhaps by word fence) blocking unauthorised bot login attempts

[Tue Aug 27 01:30:53.762732 2024] [access_compat:error] [pid 2701399:tid 2701399] [client 104.239.37.185:38994] AH01797: client denied by server configuration: /home/infantat/public_html/xmlrpc.php
[Tue Aug 27 01:30:51.480877 2024] [access_compat:error] [pid 2739868:tid 2739868] [client 104.239.91.155:57340] AH01797: client denied by server configuration: /home/infantat/public_html/xmlrpc.php
[Tue Aug 27 01:30:49.595615 2024] [access_compat:error] [pid 2690549:tid 2690549] [client 104.239.107.150:51450] AH01797: client denied by server configuration: /home/infantat/public_html/xmlrpc.php
[Tue Aug 27 01:30:46.292850 2024] [access_compat:error] [pid 2649051:tid 2649051] [client 204.44.69.252:32824] AH01797: client denied by server configuration: /home/infantat/public_html/xmlrpc.php
[Tue Aug 27 01:30:42.692378 2024] [access_compat:error] [pid 2739868:tid 2739868] [client 45.41.160.42:39412] AH01797: client denied by server configuration: /home/infantat/public_html/xmlrpc.php
[Tue Aug 27 01:30:40.001976 2024] [access_compat:error] [pid 2677581:tid 2677581] [client 216.173.104.228:44448] AH01797: client denied by server configuration: /home/infantat/public_html/xmlrpc.php


so still scratching my head here.

am I able to create a login for you so that you can poke around and get a first-hand view?

regards 

miles 

If clearing the queue didn’t help, then I’d recommend posting your issue in WP Mail SMTP’s support forum, where you’re likely to get more knowledgable support. Let them know what the error is, and you’ve tried so far (e.g. the scheduler log info seems it would be helpful). It’s clear that the plugin is somehow involved in this, and I’m sure the plugin authors will be able to figure something out.

I agree that those server log entries don’t appear to be related to the upload issue.