similar to: Puppet host alias problem

Hi, I''ve been experimenting with Puppet for a few days now, and I really like it. But! I''m having real CPU usage problems. Puppet is still happily eating away 100% CPU for almost an hour at a time, with no apparent things happening. (puppetd -tv --trace --debug, but nothing appearing in the console during this.) I believe the following resource is to blame: file {

Is the host_aliases parameter to sshkey new in 0.25? Jun 1 15:28:48 s_sys@ext3.fr.xxx.com puppetd[20358]: Could not retrieve catalog: Invalid parameter ''host_aliases'' for type ''Sshkey'' at /etc/puppet/manifests/nodes/fr.twofish.com/ext3.pp:19 on node ext3.fr.xxx.com Jun 1 15:28:48 s_sys@ext3.fr.xxx.com puppetd[20358]: Not using cache on failed catalog The

Hey All, I''m running into a problem whereby some nodes are struggling to retrieve the metadata for files. I''ve moved all the nodes across to 0.25.1 to try and eliminate version inconsistencies though they still appear. I''ve also started using asynchronous stored configs as well. I''m wondering if this has anything to do with performance on the box and if there

I have the class below to export host entries. However I wish to override the entry for my host to 127.0.0.1 So for all of the hosts other than foo.bar.com I would like them to have the real IP address but for foo.bar.com I would like to just have the loopback host entry. 2.6.2 doesn''t allow multiple tags and if I put in another entry for localhost there is a collision. Is there any

I''m making a cups manager type and I''m having trouble figuring out where I should parameters and where I should use properties. The file is at http://github.com/kc7zzv/puppet-cups_printer/blob/master/lib/puppet/type/cups_printer.rb . I was accidentally using "newproperty" and "newparameter" interchangeably, and I''d really like to know which I should

Here''s one I learned: I originally had # Ensure /etc/hosts contains the basics host { "${fqdn}": host_aliases => $hostname, ip => $ipaddress, } And thru some trial and error, got down to this (which puppet-lint does not gripe about) # Ensure /etc/hosts contains the basics host { $fqdn: host_aliases => $hostname, ip => $ipaddress, }

We keep getting a variety of these from a random set during each Puppet run: Sat Mar 13 23:46:42 -0500 2010 //cups/File[/etc/cups] (err): Failed to generate additional resources using ''eval_generate'': end of file reached It seems like there is a 30% chance of a host providing this on any given manifest that distributes files. It''s only started since we went from 0.24

Hi, I am running puppet version 0.25.1 on both the server and client and am getting the following error on a puppet run: err: Could not apply complete catalog: Could not retrieve dependency ''Class[http]'' of Class[puppet::http] Class http is defined in the "http" module like so: class http { package { httpd: ensure => installed } file {

Hi i have the running i both sides, client and server sides the puppet 0.25.4 Get this error on server side: puppetmasterd[5363]: Report puppet_dashboard failed: wrong Content-Length format And receive this error on my client side: warning: Value of ''preferred_serialization_format'' (pson) is invalid for report, user default (b64_zlib_yaml) I am getting any reports on my

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello, I read and find a way (well, there seems to be several equal implementations) to collect the ssh keys of machines. However they all give only the choice to choose between the key formats. But is there a way to collect both keys of a machine, the rsa _and_ the dss key (and maybe the rsa1 too)? I didn''t find a way to solve this as

Hi folks, I''m overriding some resource attribute in a subclass. It seems that specifying a resource by its alias doesn''t work in a subclass. Looks like a bug, no ? === module-classes.pp === class module::base { file {"/tmp/test-module": alias => test-module, content => "module::base", } } class

I am running puppet 3.2.1, using the puppetlabs repos, on centos 6.4. I keep getting these messages in the log: (every 30 minutes) Jun 3 11:24:55 yoda puppet-master[20292]: Failed to set SELinux context system_u:object_r:puppet_etc_t:s0 on /etc/puppet/auth.conf Jun 3 11:24:55 yoda puppet-master[20292]: Failed to set SELinux context system_u:object_r:puppet_etc_t:s0 on

I''ve almost finished a pretty simple type/provider to manage RabbitMQ users and virtual hosts. I''m using the ''ensurable'' keyword in my type to save a bit of boilerplate. Type is below (the provider is just a wrapper around the ''rabbitmqctl'' command. Have a feeling there''s a developer guide somewhere I haven''t found (been

Hello... Is this a bug or by design? I''m using exported resources to generate /etc/ssh/ssh_known_hosts. I changed the example from the docs to this: @@sshkey { "$fqdn,$hostname,$ipaddress": type => rsa, key => $sshrsakey, } so that I would get one line per host in the ssh_know_hosts file. What happened was that on each run several (all?)

I''m trying to create a ssh class where the /etc/ssh/ssh_known_hosts and /etc/ssh/shosts.equiv stays updated. The issue i''m finding is that if I include a "tag == anything" in the Collector filter, it collects all resources EXCEPT it''s own. In this case, the known_hosts and .equiv files will have all the other hostnames, but not it''s own hostname.

On a file resource, if the content parameter is set and checksum is set to none, I am getting "Parameter content failed: Munging failed..." This appears to be a bug, but maybe I missed something in the documentation and it isn''t supposed to work. cat test.pp file { "/tmp/foo": checksum => none, content => "this is foo\n", } puppet

On Dec 8, 2010, at 11:09 AM, Ken Barber wrote: > (cross posting here as I originally posted in puppet-users - I figure the question is more of a dev one then for puppet-users) > > Hi everyone, > > I''m experimenting with converting some of my live puppet content to > Ruby DSL and have found a few gaps I wouldn''t mind some advice on. I''m > not sure

Can anyone comment on their experiences with librarian-puppet or using git superproject with per puppet module repositories? We are in the midst of determining which route is optimal for our environment. It seems like using git superprojects would mean one less new tool for everyone to learn. What then would be the advantages of librarian-puppet? Thanks, Ryan Bowlby -- You received this

Can someone tell me the correct way to specify the following require statement in an rspec-puppet test? *require => [Class[''ssl''],Class[''pcre3''],Staging::Extract["nginx-${version}.tar.gz"]]* I tried this: *''require'' =>

I´m trying to utilize the new stdlib module, but got stuck after installation on my puppet server. I´ve tried to use the included test file file_line.pp on the server, but it´s only creating the file - but not managing the content. the same problem on my clients (the new provider file_line has been synced), it´s just not working: file_line { ''puppet master host