2.0.23 Cron Job Times Out – Makes Server Die Dead

@jrmuir
And trust me, its no fun to clean up this f*%&$ mess.

Btw the developer reverted the plugin to a stable release (2.0.21) one-half hour before – aha, that′s realy funny, thanks a lot. 2 days in update hell and they reverting to a previous version! They had probably not been sufficiently tested the svn, right?

Yes, i′m realy upset, but i′ve to admit that the 2.0.21 version works for me “almost” without a flaw. Now I am satisfied and can′t wait till the next update to ruin a whole day.

[rant removed…] my fault, the current released version v2.0.25 is actually the v2.0.21 codebase.

Thanks for the plug on FFF Cron Manager. That made it easy to cleanup after falling back. A little humor… if you go to nextgen-gallery.com right now, they are experiencing a database connection error. Must be finally testing 2.0.23! ??

2.0.25 is 2.0.21 – I asked them to bump the version to upgrade people and get you out of trouble somewhat :/

mcgeedon, yes! nextgen-gallery.com is down! $)

To help fix this, if you have binlog enabled on your mysql server(s) you can pretty quickly find your bad cron tables:

mysqlbinlog --verbose --base64-output=DECODE-ROWS mysql-bin.000001 | less

Just search through for ngg_delete. Once you find one, scroll up to get the database/tablename. To get to the next, search for UPDATE once, then again for ngg_delete (hint, / in less is the search, so /ngg_delete<enter> to search for ngg_delete).

Good for monitoring that you actually caught them all as well.

And thanks to SH101 for the script, that seems to be doing the trick. I was going down a similar route but hadn’t gotten there yet.

All – We do apologize for all of this. We are working as fast as possible to develop a patch; get a lot of eyes on it for validation; and release it as soon as we can.

We cannot imagine the frustration this is causing and can only beg for your patience as we work to get this resolved. Please bear with us …

– Cais.

I’ve applied the new version (2.0.25) to all installations on one of my servers BUT the NextGen generated wp-cron jobs keep coming up non-stop…

Any one know how to help stop all of the NextGen generated wp-cron jobs?

All – Please update to version 2.0.27 as soon as you are able to. This should resolve the CRON jobs issue that was recently introduced.

Again, we do apologize for all of these inconveniences and the frustration we have brought to you.

Just go to your Dashboard and if a notice for the update is not shown then go to the Updates panel, it should be there.

If you need to download this version specifically for manual installation/updates, here is the direct link: https://downloads.www.ads-software.com/plugin/nextgen-gallery.2.0.27.zip

– Cais.

Is there a chance 2.0.27 is flawed? Just had my site crash and am dealing with my host now while they try to figure out what is hogging the CPU. They had me optimize the DB, a few minutes later the site was up and then crashed again.

Something took the site out and it sounds like a cron job run amok.

The difference between the two sites is that one was promoted to a special interest community and the traffic reflected an immediate impact on the traffic.

I updated to 2.0.27 but the cron is still causing the server to crash.

bhargavy, .27 is stable. Maybe you need to purge the WP cron?

I just downgraded to .21. I think I’ll wait for a few days before updating but How can I purge the WP cron?

bhargavy,

You can use the FFF cron manager plugin or workaround that was recommended in another topic:

What I did – in addition:
1. I added this line to functions.php. It deletes all photocrati mess rather quickly: wp_clear_scheduled_hook( ‘ngg_delete_transients’ );
2. I checked with fff cron manager and all NGG lines were gone.
3. I reactivated NGG and now I start looking for an alternative. Enough is enough.

There are so many ngg_delete_expired_transients in wp cron that chrome is getting stuck before it finishes loading.

I tried adding wp_clear_scheduled_hook( 'ngg_delete_expired_transients' );

to functon.php of the theme but if I do that the website is not loading at all.

I tried to edit my post, but it didn’t take..
It was .23 that punked my site, but fortunately I pointed the host here because their automated process sent a generic report after it disconnected the database. So far .27 has not been an issue.

Having said that, over 8 million downloads out there so the NGG team ought to review itself and figure out a better process.