2.0.23 Cron Job Times Out – Makes Server Die Dead

Reverted to 2.0.21 to resurrect our site from the dead

John –

This is very serious, we would really appreciate it if you could submit a Bug Report here: https://www.nextgen-gallery.com/report-bug/

I’m asking for the sole purpose of having you be able to provide us log in credentials to your WordPress installation as well as FTP credentials to the WordPress installation folder so our developers can look at why this may have happened to you and your site.

Thanks!

– Cais.

I can confirm this. I just upgraded to 2.0.23 and within 5 minutes, my site was dead with too many processes running. I had to have my host kill the processes and the confirmed that it was the wp-cron.

I can also confirm. After updating, my entire server went down

I am also can confirm. After upgrade NGG create too many cron process: ngg_delete_expired_transients

I am downgrade to .21 ??

I did not do a downgrade.
I am just commented in nextgen-gallery/nggallery.php this code:

// Delete displayed gallery transients periodically
		// add_action('ngg_delete_expired_transients', array(&$this, 'delete_expired_transients'));
		// if (!wp_next_scheduled('ngg_delete_transients')) {
		//	wp_schedule_event(time(), 'hourly', 'ngg_delete_expired_transients');
		// }

Same on my side…

Mysql service hogs as 99% CPU…

Mytop returns:

Query SELECT autoload FROM wp_options WHERE option_name = '_transient_timeout_f99ae0f68e864d0fb9b92adb74792d27'
Query DELETE FROM wp_options WHERE option_name LIKE 'displayed_galleries_f99ae0f68e864d0fb9b92adb74792d27'
Query SELECT autoload FROM wp_options WHERE option_name = '_transient_f99ae0f68e864d0fb9b92adb74792d27'
Query DELETE FROM wp_options WHERE option_name LIKE 'displayed_galleries_2f7e7149f8adf497c0759f05d19f7990'
Query DELETE FROM wp_options WHERE option_name LIKE 'displayed_galleries_f99ae0f68e864d0fb9b92adb74792d27'

After some time, memory is exhausted and my server dies…

Matej

All – Just an FYI, this issue is being addressed immediately. We will release a new update related to this as soon as possible.

We apologize for the inconveniences this has caused.

– Cais.

Photocrati, once the errant inserts are fixed you are still left with all those bogus entries in wp_options ‘cron’ field. We are scripting a select, deserialize, remove bogus entries, reserialize and insert to apply globally on our system. However you’ll want to do this in your plugin update as well for others.

Josh, Any chance you’ll be releasing that script?

@phikai on your own risk – try this (on commandline: $ php whateverfilename.php)

<?php
$rov = array();
$roventry = unserialize('SERIALISED DATA FROM WP_OPTIONS(cron)');
foreach($roventry as $entry)
{
	if(key($entry) == 'ngg_delete_expired_transients')
	{
		echo 'GO_AWAY_NGG';
	} else {
		array_push($rov,$entry);
	}
	echo '=============='. "\r\n";
}
echo 'PASTE THIS BACK TO YOUR CRON' . "\r\n";
echo serialize($rov);
?>

I used the plugin FFF Cron Manager for cleaning WP cron

It’s pretty impressive when you can load up 1180+ cron entries for the same thing in a site. Add that across multiple sites running on the same db server(s) in a replication setup, and you can take 3-4 G of db content and turn that into 50+ G of binlog data in under 5 minutes, break replication, and corrupt databases.

This was a really, really bad update Cais.