My log file is cycling at 32 MB $ date;du -sk * Thu Feb 14 19:35:38 UTC 2013 24288 db-12257.log 360 db.data 124 db.redo 0 lock
$ date;du -sk * Thu Feb 14 19:37:29 UTC 2013 32816 db-12257.log 1820 db-12258.log 360 db.data 124 db.redo 0 lock $ date;du -sk * Thu Feb 14 19:37:47 UTC 2013 3660 db-12258.log 360 db.data 124 db.redo 0 lock $ date;du -sk * Thu Feb 14 19:40:00 UTC 2013 15520 db-12258.log 360 db.data 124 db.redo 0 lock $ date;du -sk * Thu Feb 14 19:42:41 UTC 2013 33024 db-12258.log 364 db-12259.log 360 db.data 124 db.redo 0 lock $ ps auxw | grep puppetdb |grep -v grep puppetdb 1486 24.6 11.7 2406524 459636 ? Sl Feb09 2050:43 /usr/bin/java -XX:OnOutOfMemoryError=kill -9 %p -Xmx1024m -jar /usr/share/puppetdb/puppetdb.jar services -c /etc/puppetdb/conf.d $ rpm -qi puppetdb Name : puppetdb Relocations: (not relocatable) Version : 1.1.1 Vendor: (none) Release : 1.el6 Build Date: Fri 01 Feb 2013 10:21:27 AM UTC Install Date: Sat 09 Feb 2013 12:08:35 AM UTC Build Host: rpm-builder.delivery.puppetlabs.net Group : System Environment/Daemons Source RPM: puppetdb-1.1.1-1.el6.src.rpm Size : 19736313 License: ASL 2.0 Signature : RSA/SHA1, Mon 04 Feb 2013 06:51:33 PM UTC, Key ID 1054b7a24bd6ec30 URL : http://github.com/puppetlabs/puppetdb Summary : Puppet Centralized Storage Daemon Description : Puppet Centralized Storage. On Wednesday, February 13, 2013 12:00:40 PM UTC-6, Ken Barber wrote: > > Hi all, > > I've been looking at a potential problem, as documented here: > > http://projects.puppetlabs.com/issues/19241 > > To do with a leak within the KahaDB persistence layer of ActiveMQ. > Specifically, there are reports of the db.data file growing unbounded: > > https://issues.apache.org/jira/browse/AMQ-3956 > > I'm hoping to find out information from other PuppetDB users to see if > this is happening in the wild. What I'm hoping is that users can > provide me with information around the size of the files in > /var/lib/puppetdb/localhost/KahaDB. For example, here is the size on > my test machine: > > root@puppetdb1:/var/lib/puppetdb/mq/localhost/KahaDB# pwd > /var/lib/puppetdb/mq/localhost/KahaDB > root@puppetdb1:/var/lib/puppetdb/mq/localhost/KahaDB# du -sk * > 5552 db-1.log > 32 db.data > 32 db.redo > 0 lock > root@puppetdb1:/var/lib/puppetdb/mq/localhost/KahaDB# > > And an indication of how long its been running: > > $ ps auxw | grep java > puppetdb 52606 0.3 3.6 1536236 216136 ? Sl 13:34 0:55 > /usr/bin/java -XX:OnOutOfMemoryError=kill -9 %p -Xmx1g > -XX:+HeapDumpOnOutOfMemoryError > -XX:HeapDumpPath=/var/log/puppetdb/puppetdb-oom.hprof -jar > /usr/share/puppetdb/puppetdb.jar services -c /etc/puppetdb/conf.d > > And the version of PuppetDB: > > # dpkg -l puppetdb > ... > ii puppetdb 1.1.1-1puppetlab all PuppetDB > Centralized Storage. > > (rpm -qi puppetdb on Redhat based machines). > > I've so far had 1 suspected case of this (the directory was reported > at 17 GB), but no data to back it up - if you use PuppetDB and have > the time and inclination, I'd appreciate some outputs from your > PuppetDB hosts like the ones shown above (scrubbing private > information of course) - even if it looks fine - as it will help us > decide on the priority of this bug. > > Thanks in advance! > > ken. > -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
