similar to: Running puppet as non-root user

Hi all, I''m just starting to look at using Augeas with Puppet to manage some of our configuration files. I thought I would start with a simple task of removing an entry from the /etc/hosts file. I''m not finding it simple though! We have a number of hosts with entries in the /etc/hosts file like this: 127.0.1.1 hostname We would like to remove these lines. Now I know this can

puppet schrieb: > #779: access to inherited variables from within a template > -----------------------------------------+---------------------------------- > Reporter: simu | Owner: luke > Type: enhancement | Status: new > Priority: normal | Milestone: >

I have these three modules with the following structure: |-- modules | |-- create_resources | | |-- LICENSE | | |-- Modulefile | | |-- README | | |-- lib | | | `-- puppet | | | `-- parser | | | `-- functions | | | `-- create_resources.rb | | |-- spec | | | |-- spec.opts | | | |-- spec_helper.rb | | | `-- unit

I have some middleware where the successful configuration of node B is dependent on the successful configuration of node A. Node B must pull additional information from node A during its configuration. Is there any built in functionality in puppet for checking the completion status of other nodes? Right now my intent is to write a custom function to query the puppetdb which is storing

I''m using puppet to manage configs on machines where I don''t have root access. Whenever I use a File resource where the source is a puppet:// resource, I get tons of warnings when I run puppet that look like: Cannot manage ownership unless running as root True enough, I''m not running as root, but I also didn''t specifically mention a "owner"

Could I use my local laptop as a puppet master, and only start up the puppetmaster when I have a change I want to send over to the nodes? Say I only have 1 server, and I don''t want or even need a puppetmaster running all the time. Is this or something close to this type of setup possible? -- You received this message because you are subscribed to the Google Groups "Puppet

Hi, I just wanted to check a few things. I have a build server which is used to run the CI server. It also doubles up as my puppetmaster. Would it be possible to have a puppet client talk to a puppetmaster on the same machine? Cheers, Tom -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

Hi all, I''m doing a new install of my puppet server and I''m doing it like: 1.-) adding epel repo: http://fedoraproject.org/wiki/EPEL/FAQ#howtouse 2.-) yum -y install puppet-server 3.-) rm -rf /etc/puppet 4.-) copy my old puppet conf (from puppet-0.24.5 to 0.24.6) mv /etc/puppet.old /etc/puppet 5.-) start puppetmaster: [gridinstall etc]# /etc/init.d/puppetmaster start

I am attempting to move our test puppet installation from looking for node information in a manifest to LDAP. I followed the instructions at: https://reductivelabs.com/trac/puppet/wiki/LdapNodes and was able to get the puppet schema loaded into our LDAP. I can now query LDAP and modify/load data without any issues using the OpenLDAP tools. e.g. ldapsearch -h ldapdev1.domain.com -x

I had some questions come up today during the Puppet demo here: 1. Is there any way to apply different intervals to different classes? For example, we might want a security baseline manifest to run once a month, package installation files once/day, etc. Since we''re a brokerage, we also don''t want ANY system changes during trading hours. I guess we could cron killing the

Hello, I am having problems with Puppet since upgrading to 3.0.0. When I call an inventory search I get a Error 400. I have used dashboard + Perl Oct 4 08:58:43 puppet01 puppet-master[7008]: Handling request: GET /production/facts_search/search?facts.lsbdistcodename.eq=lenny Oct 4 08:58:43 puppet01 puppet-master[7008]: header too long ii facter

We have a client-server puppetmaster running puppetd and puppetmasterd, however I would like to test configurations locally before committing the changes on the puppetmaster. Running the puppet config locally with /usr/bin/puppet mostly works. The thing that fails ( which I have commented out on my local copy to test everything else ) is a erb template for puppet.conf that includes:

Hi, we are currently managing our puppet modules with one SVN workspace for each admin. The post commit hook script updates /etc/puppet/ directory and triggers the puppet kick of the correct server. The problem we have with this solution is that sometimes there are many small checkins to one change, because the admin forgot to change small details in the config file, e.g. forgot to change

Hi, I am new to Puppet. I need to monitor a file for changes on a server and if it does, copy it immediately to the clients. But it has permissions 640, and must retain these. Can anyone suggest a manifest for this? Thanks a lot. M -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit

Hello all, I recently switched to running puppet master using Passenger. However, I am seeing agents unable to send reports after a bunch of ''master'' processes starting to accumulate and eat all the RAM and swap space. Error: Could not send report: Error 500 on SERVER: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head>

I have very strange problem. I set up puppet client on serveral servers but have problem with one of them. When I invoke: root@www ~ # puppet agent --server puppetmaster.domain.ltd --test notice: Ignoring --listen on onetime run info: Caching catalog for puppetclient.domain.ltd info: Applying configuration version ''1326444431'' notice: Finished catalog run in

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

I''m trying to come up with a way to manage /etc/puppet on the Puppet server from my workstation. My idea was to place all of /etc/puppet into subversion, check it out to my workstation, commit via ssh, and then use a post-commit to update /etc/puppet. That way any time I made a change in /etc/puppet it would be immediately updated and ready for the next puppetd run. Problem is the

i thought i would run up a fedora 8 installation and take a look around, my default kickstart installation includes puppet which shouldn''t be a problem however the puppet client fails with Certificates were not trusted: hostname was not match with the server certificate The cause is obvious, the hostname of my puppetmaster is ''puppet1.mydomain.com'' and

Hello Puppet list, I am taking over the puppet configuration of a sysadmin who left, and am having troubles deploying puppet to a new node. We are using puppet v2.7.3 both on the client and the puppetmaster, on Ubuntu 10.10. The node asks for a certificate fine, and I signed it on the puppetmaster. For the following logs extract I ve replaced the FQDN of my node by puppet.example.com. When doing