similar to: Announce: Puppet 2.7.18 Available [ Security Release ]

Dear Puppet Enterprise Users, Puppet Enterprise 2.5.2 is now available. This is a maintenance release of PE with bug fixes and security updates. All users of Puppet Enterprise 2.5 are strongly encouraged to upgrade when possible to Puppet Enterprise 2.5.2. Puppet Enterprise 2.5.2 includes fixes to address CVE-2012-3864, CVE-2012-3865, CVE-2012-3866 and CVE-2012-3867. For more information, please

I am finding that the puppetlabs-apache module is somehow adding 30-60 seconds onto a host''s catalog compile time when the puppetmaster has no other hosts contacting or generating catalogs. The Puppetmaster is setup to use Puppet-2.7.18 - Apache & Passenger. RIght now only 2 hosts are even configured to use this new PM, the PM itself and a Foreman host. With neither hosts

Hello, Running into a problem when wanting to daemon-ize the agent. It doesnt seems to do anything: - cannot find any daemon process with (ps aux | grep puppet) - the config is not updated after editing some params on the master - /var/log/puppet stay empty... while, when logged as root, it is working without issue with $puppet agent --test. ##Conf Ubuntu 12.04 Puppet 2.7.11 ## Daemon is

Hi, I wrote a little "hello world" script and I am a little concerned by execution that hangs for long periods of time. *computer:* Windows XP Professional Service Pack 3 Intel(R) Xeon(R) CPU W3550 @ 3.07GHz 3.07GHz, 3.50 GB of RAM *init.pp:* class hello { notice(''Hello world!'') } *command line:* puppet apply --debug -e ''include hello''

Howdy, Trying to install dmg files with puppet. However, after running my manifest the .dmg file is never downloaded by curl. I tried pkgdmg and appdmg. I also tried using a local directory as the source. It seems to ignore any path I give as the source even totally bogus ones. 1 define pkg_deploy($sourcedir = false) { 2 $sourcedir_real = $sourcedir ? { 3 false

I could use some help debugging a bazaar PuppetDB problem. Exported resources seem to be working fine everywhere except for on the Puppet Masters themselves. Whenever I run the puppet agent on them everything seems to go fine and I see the catalog getting submitted to PuppetDB in the logs. However, when I run puppet on the node that should collect these resources they aren''t

Hi! Before anything, here is my hardware/software informations : Hardware : -IBM x345, 1 CPU, 1G RAM, IBM ServeRAID controlle -6 HD used with LVM, 2 volume group, 12 logical volumes all running ext3 Software : -RedHat Linux Enterprise AS (Academic) 3.0 update 1 -Kernel 2.4.21-4.0.2.EL -samba-3.0.2-6.3E -Running an apache 2 web server -On normal use, there is only 10-15 computers

Hello, It seems that, for one reason or another, two thing happened: the postgres for puppetdb was dead, and the puppetmaster service was started, even though it''s run from apache. After a bit of cleanup, everything works now. Thanks for your suggestion, and sorry for the stupid issue. On Tue, Mar 26, 2013 at 11:43 AM, Keith Burdis <keith@burdis.org> wrote: > The agent only

Hi all I''m trying to set up a separate puppet master and client on EC2. I''ve used two instances of CentOS5.4 with nothing other than the base install and have installed puppet via the ruby gems. Puppet is at 2.6.4 on both machines. I''ve been following the guide to get a basic configuration working (http://docs.puppetlabs.com/guides/configuring.html) with a little tweak

All- Poking around in the bug database it looks like storeconfigs is being actively worked on. I am using 2.7.6 on my master as well as all the clients. I have clients boot , start puppet and get a signed cert via auto signing. The nagios module (and currently the only thing puppet does) complains a lot during compile time about not having storeconfigs enabled, which is not the case in my

Hi all, Could anyone help me at least start debugging this issue? All agents have the same error, but i can''t find anything on the master-side logs. And the agent-side logs are non-existent (/var/log/puppet is empty). Thanks. Versions: Master: Red Hat Enterprise Linux Server release 6.3 puppet-server-3.1.0-1.el6.noarch puppetdb-1.1.1-1.el6.noarch puppetdb-terminus-1.1.1-1.el6.noarch

Hi, My platform is Ubuntu 12.04. The hostname is puppet and this is a Virtual Machine in Vmware 5.0. This is a lab server and it is behind a proxy. I am having a problem with the installer. Any ideas what is going on? root@puppet:/home/rbgonza/puppet/puppet-enterprise-2.8.0-all# ./puppet-enterprise-installer

Hi, I have a puppetmaster - agent architecture. I have a module for the vsftpd configuracion in the agents. The configuration of the value ''max_per_ip'' in the agents may vary. This is a line of the manifest: $max_per_ip = hiera(''max_per_ip'',10) I want to specify different values for each agent using hiera. The problem is I am only able to specify the

Hi all, I''m behind a proxy squid server with authentication. I have set environment variables http_proxy and https_proxy, something like http://user:passwd@ip_proxy:3128. I upgraded to 2.7.18 puppet version recently. Then i''d getting in error when trying to install stdlib module : puppet module install puppetlabs-stdlib Preparing to install into /etc/puppet/modules ...

Hello All, Unable to install Puppet Enterprise v2.0.0 for RHEL 5-x86_64. [root@1801 puppet-enterprise-2.0.0-el-5-x86_64]# ./puppet-enterprise- installer -a answers/full_suite.answer.sample ============================================================================================================================ Puppet Enterprise v2.0.0 installer for el-5-x86_64

I''m getting these errors when running ''puppet agent --test'' after doing a new installation of an agent: err: /Stage[main]/Pe_mcollective::Plugins/File[/opt/puppet/libexec/mcollective/mcollective/security/sshkey.rb]/content: change from {md5}512f42272699eaa085c83d2cc67c27ea to {md5}8fa3e9125fd917948445e3d2621d40e5 failed: Could not back up

on my puppet master server (v 2.7.17 , both server and client version) , the puppet agent can''t connect to itself. other clients connected to this puppet server are working fine. the hostname is puppet.domain.com [root@puppet /]# cat /etc/puppet/puppet.conf [main] # The Puppet log directory. # The default value is ''$vardir/log''. logdir = /var/log/puppet

Hi there, after using Foreman successful on our clusters for more than a year. I'd like to reinstall a 90 node cluster with Centos 7.4. It's now running on Centos 7.3 . I'm not able to just update to 7.4 because of zfsonlinux dependencies and well - some nodes died and had to bare metal install them. So I was able to install these nodes successfully by pxe-booting and using a

I''m using puppet 3.0 i install puppet by these two command: sudo rpm -i http://yum.puppetlabs.com/el/5/products/i386/puppetlabs-release-5-6.noarch.rpm sudo yum install puppet-server as http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#for-red-hat-enterprise-linux-and-derivatives and

Hello group, I am trying to run a puppet agent v3.2.2 against a puppet master with version 2.7.18, and I get this weird error: Warning: Unable to fetch my node definition, but the agent run will continue: Warning: Could not intern from pson: source ''"#<Puppet::Node:0x7f'' not in PSON! The run fails with "module not found", which is definitely there and