Am Donnerstag, 21. Januar 2016 12:45:59 UTC+1 schrieb Tiago Delboni:
>
> Hi, I'm revisiting this topic.
>
> Wasn't garbage collector supposed to clean up the old reports and leave
> the last "report-ttl" on disk? Or this is valid only for the reports stored
> in the PuppetDB's database?
>
I wo
Hi, I'm revisiting this topic.
Wasn't garbage collector supposed to clean up the old reports and leave the
last "report-ttl" on disk? Or this is valid only for the reports stored in
the PuppetDB's database?
Regarding "the script way" of removing old reports, we have this line in
cron:
/usr/bi
One thing I found after manually deleting gb's of reports was that they still
exists in dashboard but failed to load when you click on them.
Don't forget to run the command suggested in
http://docs.puppetlabs.com/dashboard/manual/1.2/maintaining.html
Josh
--
You received this message because
Be aware that this will create a file resource/checksum for EVERY file in
that directory and may cause a heavy load on your system if you have a lot
of reports.
Trevor
On Tue, Sep 10, 2013 at 10:12 PM, Andrew wrote:
> Using tidy to clean up logs, this is pretty self-explanatory, so I wont
> bo
Using tidy to clean up logs, this is pretty self-explanatory, so I wont
bother explaining :)
case $hostname {
/^puppet$/: {
tidy { 'puppet::reports':
path => '/var/lib/puppet/reports',
matches => '*',
age => '14d',
backup => false,
