Thanks all. That worked.
On 11/03/2011 08:36 AM, Nigel Kersten wrote:
FWIW the bug was put in as:
https://projects.puppetlabs.com/issues/10442
(adding these comments to it)
On Thu, Nov 3, 2011 at 5
FWIW the bug was put in as:
https://projects.puppetlabs.com/issues/10442
(adding these comments to it)
On Thu, Nov 3, 2011 at 5:19 AM, Luke Bigum wrote:
> FYI this is a lot faster to delete everything from a MySQL table:
>
> TRUNCATE TABLE delayed_job_failures;
>
> On Nov 3, 12:10 pm, Evgeny
FYI this is a lot faster to delete everything from a MySQL table:
TRUNCATE TABLE delayed_job_failures;
On Nov 3, 12:10 pm, Evgeny wrote:
> then only it will help:
>
> delete FROM `delayed_job_failures` WHERE 1
--
You received this message because you are subscribed to the Google Groups
"Puppe
then only it will help:
delete FROM `delayed_job_failures` WHERE 1
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+u
I don't think this will help. I do report cleanup daily to keep only the
last 14 days and it hasn't touched the number of delayed job failures
reported.
On 10/31/2011 12:26 AM, Evgeny wrote:
this will clean all reports, I don't know how to clean only delayed
job failures but it may help
rake
this will clean all reports, I don't know how to clean only delayed
job failures but it may help
rake RAILS_ENV=production reports:prune upto=0 unit=day
On Oct 28, 9:32 pm, "Steven L. Seed" wrote:
> I have a ton of delayed job failures in my dashboard under background tasks.
> They are mostly f
