|
Drio LLC
|
October 11, 2019 at 10:53 am
I’m having trouble with the button to do a ticket reset. I have had my host do extensive research into why I am getting this error:
PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /wordpress/wp-includes/wp-db.php on line 1972
They have not been able to run a rest without getting an error, even when taken down off line and tested on a local server. They also got a 500 error on Local.
So, they were wondering if it could be that there are nearly 3,000 tickets and it is too resource intensive even for the Local environment to complete.
Please let me know if you can provide any insight here.
|
|
Josh
|
October 11, 2019 at 11:13 am
Hi,
Instead of trying to reset what are possibly months worth of expired transactions in one request, you can install the WPCrontrol plugin, then go to its Tools > Cron Events page and manually trigger the scheduled expired transaction clean up tasks that did not run. On that page, you’ll likely find many tasks named “AHEE__EE_Cron_Tasks__expired_transaction_check”. You’ll click the Run Now links for these.
Then, you’ll need to fix the site so it allows for scheduled tasks. Your host may have disabled wp_cron, or you may need to run an alternative cron. You’ll find some technical tips about fixing wp_cron here:
https://wp-mix.com/wordpress-cron-not-working/
|
|
Drio LLC
|
October 22, 2019 at 8:59 am
From my host:
I’ve just taken a look and can 100% confirm that the cron jobs for this site and our test sites have been working correctly and not outputting any errors, this includes the AHEE__EE_Cron_Tasks__expired_transaction_check as mentioned by the EE Support team.
I’ve manually run these crons and then attempted the button again but it remains that it continues the same errors.
Executed the cron event ‘AHEE__EE_Cron_Tasks__expired_transaction_check’ in 0.003s.
Executed the cron event ‘AHEE__EE_Cron_Tasks__expired_transaction_check’ in 0.001s.
Executed the cron event ‘AHEE__EE_Cron_Tasks__expired_transaction_check’ in 0.001s.
Executed the cron event ‘AHEE__EE_Cron_Tasks__expired_transaction_check’ in 0.001s.
Executed the cron event ‘AHEE__EE_Cron_Tasks__expired_transaction_check’ in 0.001s.
Success: Executed a total of 5 cron events.
We would conclude that this is still an issue with the plugin and perhaps the volume of tickets you have the plugin is struggling with that.
While we would agree the usage of a plugin such as WP Crontrol is a great addition to the site in order to monitor the cron job status etc, it’s not a requirement as all the cron jobs are firing in order as the site has enough traffic to keep that process moving 🙂
I’ve read through all of the notes/tests that the team has performed and we can confirm that in our tests we installed the plugin on a new install and it did work as expected, but any clone of the current site does not work (we have tested across both out Legacy and Cloud platforms to be sure it’s not an incompatibility issue).
Unfortunately and I hate to bounce you back but do think the Event Espresso support team do need to do a little more digging as to why the process either timeout after long durations or keeps chewing through memory and ultimately if they are able to optimize the process that is run when the cleanup button is pressed.
Thank you,
Rachel
|
|
Josh
|
October 22, 2019 at 12:51 pm
Hi,
I’m kind of at a loss to understand what they mean by doing more digging. The plugin would not be what’s struggling, but the server could be struggling if there’s a huge backlog of reserved ticket counts. Possibly at some time before the cron tasks were not firing, and now it cannot catch up.
What you could do is go into the database, and set all TKT_reserved fields in the wp_esp_ticket table to 0. Then do the same for the the DTT_reserved fields in the wp_esp_datetime table.
|
