That is good information, though I find that the prune command for puppet-dashboard doesn't really seem to have a major impact on disk usage.
I did find this as yet another directory where reports are stored /usr/share/puppet-dashboard/spool Looks like that may need the same attention /var/lib/puppet/reports needs. On Wednesday, October 15, 2014 1:07:49 PM UTC-4, Dhaval Thakar wrote: > > Hi, > > I run following commands to clean reports from mysql & filesystem. > > I am still learning puppet, try this on your test setup. For my > requirement dashboard reports for three days is enough. > > cd /usr/share/puppet-dashboard ; export RAILS_ENV=production ; rake > reports:prune upto=3 unit=day > cd /usr/share/puppet-dashboard ; export RAILS_ENV=production ; rake > reports:prune:orphaned > find /var/lib/puppet/reports/ -mmin +300 -type f -print0 | xargs -0 -r rm > > /dev/null 2>&1 > > On 15 October 2014 9:41:36 pm IST, Mark Rosedale <mros...@vivox.com > <javascript:>> wrote: >> >> Hello, >> >> I'm running puppet with puppetdb and puppet-dashboard all on my master. >> >> I want to make sure that I don't get overrun with disk usage by either >> the master (storing reports) or the dbs for puppetdb (I'm running postgres) >> or puppet-dashboard (mysql). >> >> I'm wondering what some people do to manage disk usage for each of these? >> >> Thanks, >> mjr >> >> >> > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/0da1cd61-3794-4df5-b51f-24e5ff3fd4bd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
