similar to: Migrating from Puppet open-source to Puppet Enterprise

I just installed PE, and notice that it does not use either stored config nor puppetdb. It uses the activerecord to store facts in a mysql db. Why puppetlabs let us to use these but they do not use them in their enterprise version? Thanks. Hai T. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

I''ve seen mention of this error in several places, with different causes. So before I posted here, I attempted to resolve this on my own. I corrected the change from puppet:///files to puppet:/// in my manifests *.pp files. No changes were made to the auth.conf file, and I did note in the ChangeLog that: Auth.conf differentiates between names and IPs – There’s a new allow_ip

Hello, I''m currently trying to deploy puppetdb to my environment but I''m having difficulties and am unsure on how to proceed. I have 1300+ nodes checking in at 15 minute intervals (3.7 million resources in the population). The load is spread across 6 puppet masters. I requisitioned what I thought would be a powerful enough machine for the puppetdb/postgres server. A machine

I''m doing some testing with the puppetlabs/haproxy module on a vagrant box with puppet 3 set up. The module we use requires exported resources to be enabled in order to specify haproxy backends, but I don''t have it configured in puppet. I have our puppet repo checked out to the VM and am using puppet apply, pointed at the specific module path we use for development, to

In our environ, there are several services that are deployed via an NFS mount, so that the executables and configs are consistent across the board. Is there any reason why this couldn''t be done with Puppet? For example, each individual system would contain its own /etc/puppet and rc.d and pid files -- but the primary deployment would come from NFS. For that matter, as Enterprise

We have resources that, from time to time, are selected to be removed (unmanaged). When it comes to ssh keys, fstab... this leaves a lot of stuff behind that we don''t want. Is there a simple way to remove the unmanaged data so we can keep the systems clean. Thanks. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post

I have a requirement to manage membership to groups in /etc/group. These members do not need to be virtual users. I don''t see a way to do this through virtual users @group. How are others doing this? -- 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

Hi, When I run puppet agent --test --environment 42A, I have the following warning : Warning: Local environment: "42A" doesn''t match server specified node environment "production", switching agent to "production". ... The puppet manifest for the environment "42A" isn''t applied. The puppet version is 3.3.1-1puppetlabs1 on agent and

Hi, How can i export all the facts for all the nodes from puppetdb in cvs/xls format. My objective is to us Business Object or some other tool for creating my infrastructure reports. Can someone help/redirect me to the right documentation? Kaustubh -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and

I have FreeBSD-6.1 and it appears the default installation has a full complement of Kerberos5. But, /usr/src/kerberos5/README states: This subtree is world-exportable, as it does not contain any cryptographic code. At the time of writing, it did not even contain source code, only Makefiles and headers. Please maintain this "exportable" status quo. Thanks!

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

I read somewhere recently about problems with Puppet and Ruby 1.9. I''m wondering if this is still an issue? Thanks. -- 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+unsubscribe@googlegroups.com. For

Greetings, we are trying to setup puppetdb, nut our clients get the following error: Warning: Unable to fetch my node definition, but the agent run will continue: Warning: Error 400 on SERVER: Could not retrieve facts for lxa7t.unix.lan: Failed to submit ''replace facts'' command for lxa7t.unix.lan to PuppetDB at puppetdb:8081: Connection refused - connect(2) Info: Retrieving

Hello, I have configured puppet and puppetdb (storeconfig) with postgresql and the service run and the collecting are good for example: I can make query with the next command and responds ok . [.........................] [root@master]# curl -X GET -H ''Accept: application/json'' http://127.0.0.1:8080/v2/facts --data-urlencode ''query=["=", "name",

Hi all, For months now I''ve been using Puppet with PuppetDB backend to manage my Nagios configs. We now have 1200+ services being checked and including servicedependency, host, hostdependency, command and other Nagios resources being managed, that''s about 3000 resources in total. Unfortunately this means the monitoring server takes about 8 minutes to perform a Puppet run.

Puppet 3.3.1 // CentOS release 6.4 (Final) rpm -qa | grep puppet puppetlabs-release-6-7.noarch puppet-3.1.1-1.el6.noarch puppetdb-1.3.0-1.el6.noarch puppet-server-3.1.1-1.el6.noarch puppetdb-terminus-1.3.0-1.el6.noarch Installed from yum packages: Running Transaction Installing : puppetdb-1.3.0-1.el6.noarch

puppet agent --verbose shows a verbose output of the changes done by puppet, such as: notice: /Stage[main]/Logstash::Config/Logstash::Configdir[agent]/File[/etc/logstash/agent/config]/owner: owner changed ''root'' to ''logstash'' notice: /Stage[main]/Varnish/Service[varnish]/ensure: ensure changed ''stopped'' to ''running''

PuppetDB is operating fine, but I can''t figure out how to disable it from listening globally on TCP 1099 or 58722 How do I disable them from listening globally without having to resort to iptables? $ lsof -i -n -P | grep java | grep LISTEN java 30115 puppetdb 22u IPv6 119118 0t0 TCP *:1099 (LISTEN) java 30115 puppetdb 23u IPv6 117236 0t0 TCP *:58772

I have a puppet master install which uses puppetdb. I also have puppet dashboard installed with the inventory service running. I want multiple puppet masters using a single puppetDB server. Puppetdb is installed on separate vm. How can I get the dashboard inventory to use the puppetdb server to get the inventory records? Where do I configure the dashboard inventory so it uses puppetdb? I

Our shop is newly adopting puppet. Our number of nodes is growing and my installation method is thus far manual and tedious. This will change when/if we migrate to Puppet Enterprise. My question is what''s a best practice for managing puppet installations on client nodes? Is it possible to separate out the client portion of the install from the server or is that now fully