Jira (PDB-24) Support for Puppet Environments
Title: Message Title Simon Croome commented on an issue Re: Support for Puppet Environments Adding a use case: We release Puppet changes to the masters as separate environments, each from a git tag. The ENC controls the clients' environments. Prior to updating the ENC we check the impact by doing a --noop run against the new environment and then collating the results (x hosts will update resource y). We currently do this with MCollective but the results need parsing and we have to re-try nodes that already had runs in progress. If the events endpoint had the environment we'd be able to use PuppetDB to collate the results, though we'd lose some of the detail (e.g. file diffs). Add Comment PuppetDB / PDB-24 Support for Puppet Environments PuppetDB doesn't currently have any support for Puppet environments. It needs to. :) I expect that this won't be tremendously difficult on the storage side of things (although it may conceivably require changes to puppet itself to make sure the environment name is exposed to the fact catalog termini, and to the report processor, if it's not alrea... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-336) Investigage - PuppetDB won't start: OutOfMemoryError: Java heap space
Title: Message Title Simon Croome commented on an issue Re: Investigage - PuppetDB won't start: OutOfMemoryError: Java heap space Sorry for the delay... PE Version: pe-puppet-enterprise-release-3.1.0-0.pe.el6.noarch pe-puppetdb-1.5.1.pe-1.el6.noarch pe-activemq-5.8.0-5.pe.el6.noarch Distro: CentOS release 6.4 (Final) Linux master 2.6.32-358.el6.x86_64 #1 SMP Fri Feb 22 00:31:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Java: (no other runtime installed) # /opt/puppet/bin/java -version java version 1.7.0_19-icedtea OpenJDK Runtime Environment (PE Java 1.7.0.19) OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode) This was installed with https://github.com/adrienthebo/oscar, with config: $ cat config/vms.yaml --- vms: - name: master box: centos-64-x64-vbox4210-nocm roles: - pe-puppet-master - name: node0 box: centos-64-x64-vbox4210-nocm roles: - pe-puppet-agent $ cat config/pe_build.yaml --- pe_build: version: 3.1.0 I've not had a repeat and it's only a scratch environment - I don't need a fix, just wanted to report in case it was a wider issue. Add Comment PuppetDB / PDB-336 Investigage - PuppetDB won't start: OutOfMemoryError: Java heap space
Jira (PDB-336) PuppetDB won't start: OutOfMemoryError: Java heap space
Title: Message Title Simon Croome commented on an issue Re: PuppetDB won't start: OutOfMemoryError: Java heap space Hi Ken, this is on startup - it crashes a second or two after it starts listening on port 8081, every time. I'm pretty sure it's not processing any catalogs, only trying to recover the KahaDB datastore. The datastore should be relatively empty as there are only two nodes with the default PE classes. I'm sure you guys have better things to do, so feel free to close this if you think it's a one-off. Cheers Add Comment PuppetDB / PDB-336 PuppetDB won't start: OutOfMemoryError: Java heap space Every attempt, PuppetDB was failing to start with: java.lang.OutOfMemoryError: Java heap space Dumping heap to /var/log/pe-puppetdb/puppetdb-oom.hprof ... Heap dump file created [62635185 bytes in 0.552 secs] java.lang.OutOfMemoryError: Java heap space at org.apache.kahadb.journal.DataFileAccessor.readRecord (DataFileAccessor.java:87) org.apa... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to
Jira (PDB-336) PuppetDB won't start: OutOfMemoryError: Java heap space
Title: Message Title Simon Croome updated an issue PuppetDB / PDB-336 PuppetDB won't start: OutOfMemoryError: Java heap space KahaDB-broken should be extracted to /opt/puppet/share/puppetdb/mq/localhost/KahaDB Change By: Simon Croome Attachment: puppetdb-oom.hprof.bz2 Attachment: KahaDB-broken.tar.bz2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-336) PuppetDB won't start: OutOfMemoryError: Java heap space
Title: Message Title Simon Croome created an issue PuppetDB / PDB-336 PuppetDB won't start: OutOfMemoryError: Java heap space Issue Type: Bug Affects Versions: 1.5.1 Assignee: Unassigned Components: PE Created: 18/Jan/14 8:37 AM Environment: PE test environment, installed with Oscar on centos-64-x64-vbox4210-nocm Priority: Normal Reporter: Simon Croome Every attempt, PuppetDB was failing to start with: java.lang.OutOfMemoryError: Java heap space Dumping heap to /var/log/pe-puppetdb/puppetdb-oom.hprof ... Heap dump file created [62635185 bytes in 0.552 secs] java.lang.OutOfMemoryError: Java heap space at org.apache.kahadb.journal.DataFileAccessor.readRecord (DataFileAccessor.java:87) org.apache.kahadb.journal.Journal.read (Journal.java:604) org.apache.activemq.store.kahadb.MessageDatabase.load (MessageDatabase.java:924) org.apache.activemq.store.kahadb.MessageDatabase.recoverProducerAudit (MessageDatabase.java:596) org.apache.activemq.store.kahadb.MessageDatabase.recover (MessageDatabase.java:523) org.apache.activemq.store.kahadb.MessageDatabase.open
Jira (MCO-161) Investigate possible loss of parity between standard Puppet Labs packaging and mco plugin package
Title: Message Title Simon Croome commented on an issue Re: Investigate possible loss of parity between standard Puppet Labs packaging and mco plugin package As PE customers we use mco plugin package. I agree with RI that there should be a single method for packaging. I don't know anything about the new method but am willing to give it a try given a pointer to some docs on how I need to setup my environment. In the meantime, I hope mco plugin package doesn't lose favour. Add Comment MCollective / MCO-161 Investigate possible loss of parity between standard Puppet Labs packaging and mco plugin package User feedback has brought up the fact that if plugin packaging moves to the standard Puppet Labs packaging methods mco plugin package becomes devalued. We need to have the discussion here if we should review moving forward with standardising packaging or move back to using mco plugin package. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it,
