On Apr 4, 2011, at 3:33 AM, FRLinux wrote: > Hello, > > I have another quick one about puppet dashboard. We are using the > Debian one for Squeeze (1.0.4) and as the database has significantly > grown, if/when we click on a list of unresponsive nodes to check them, > the web interface sits there doing nothing then the puppetmaster > process starts timing out for all nodes compiling their catalogs. > > Has anyone got a workaround for this? Does it involve cleaning the > database from time to time? > > The box is a VM with 3G of allocated RAM, our ibdata1 file is pretty > big, reached 8G recently. > > So what do others do?
I run: cd /usr/share/puppet-dashboard/ nice -n +1 rake RAILS_ENV=production reports:prune upto=1 unit=mon && nice -n +1 rake RAILS_ENV=production db:raw:optimize This removes all entires older than a month, which keeps it small enough for me. My machine is a P4 with 1GB of RAM, and serves 80 nodes. Note that with MySQL, the size of the ibdata1 file won't actually shrink. The explanation is complicated, and can be found using google. If you want to get the space back, an easy way is to wipe the whole database. Put this into your config: [mysqld] innodb_file_per_table=true Then the db:raw:optimize command will actually be able to shrink the DB. Note, that attribute will cause all tables to be stored in separate files. -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
