similar to: preferred serialization format

Just upgraded to 2.7.6 and the yumrepo type does not write out our yum configs correctly, anyone experiencing this? Documentation hasn''t changed from what I can tell for this type. # facter -version 1.6.2 # puppetd --version 2.7.6 # facter architecture x86_64 # facter operatingsystem Fedora # facter operatingsystemrelease 14 ==== My manifest ==== yumrepo {

Does facter support NICs that are not named ethX? I happen to use custom names on my systems. Just a quick look at the code I don''t see why it wouldn''t but the behavior I am seeing is very different. -- 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

How come this doesnt work? I write this in a normal ruby script it works just fine. <% for cpu in (0..processorcount) %> I want to loop through the number of processor so a specific action can be taken to generate content for a file. I get an error on the master of: bad value for range at /etc/puppet" -Chris -- You received this message because you are subscribed to the Google

Seeing an error that I didn''t get in .24 since my recent upgrade today. I have pluginsync set to true, my fileserver conf is pointing to /etc/puppet/plugins and my config file is using the default pluginsource of puppet://puppet/plugins yet the client fails saying it can''t find it. Did the behaviour change in .25 from .24? [puppetd] pluginsync = true pluginsource =

Hi, We''re using puppet from longer time, but now want to switch into stored configs. When I ran locally puppet on puppetmaster server, ie: puppet /var/lib/puppet/manifests/nodes.pp --debug it works smooth. When running client with debug I get message: root@puppet-client:~# puppet agent -v --fqdn=puppet-client.ig.local -- waitforcert 60 --onetime --no-daemonize --logdest console --test

Hi. I have a client and server running Puppet 2.7.1 from GEMS (though the same problem occurs using the Ubuntu Lucid standard packages). I try to update the client against the server, and it freezes at this line: debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson Any idea what would cause that? I''m afraid I didn''t recognize any usable

----- lists@truthisfreedom.org.uk wrote: > We have a team of system administrators within our organisation who love the > look and power of MCollective but are currently "unable" to utilise it fully > as they don''t know ruby (for some reason Python is the language of > choice here!). > > I''m writing a new web interface for our change management

I''m not really sure the problem is a Plugin problem!! Note than a puppet client was installed, i change the setting of ip/hosname and try to re inscription the node to puppetmaster. I would like to understand what happen. The errors/warnings messages are not very easy to understand and sometime i''m lost. thank you for you advice. Eric Puppet version: 0.25.4-2ubuntu6

Hi all, I''d like to comment my puppetd --debug output with some expert or other admin cause I see some thing that I don''t understand. 1.-) Defaults. I define my defaults in site.pp like: case $operatingsystem { ''RedHat'' , ''CentOS'' : { [...] Package { provider => yum,

possibly related to (or the same as) issues 4830 and 2244, i''m getting errors when adding a custom fact and provider to a module to propagate to clients. am i missing something here? i tried the workaround of adding a fileserver.conf to the master (referenced below and in the tickets) with no change. thanks for any help. here''s a pile of details: puppetmaster 2.6.9 is running

I now have it listed in the console but I am now getting new errors err Could not retrieve catalog; skipping run Puppet 2012-04-05 10:22 EDT err Could not retrieve catalog from remote server: Error 400 on SERVER: No matching value for selector param ''undef'' at /opt/puppet/ share/puppet/modules/pe_mcollective/manifests/init.pp:89 on node <agent> Puppet 2012-04-05 10:22

Has anyone seen this come up, I am using 0.24.8 version of puppet. I followed the directions on the wiki and installed passenger correctly from what I can tell. [Wed Mar 17 09:07:56 2010] [notice] Apache/2.2.14 (Unix) DAV/2 Phusion_Passenger/2.2.5 mod_python/3.3.1 Python/2.5.2 mod_ssl/2.2.14 OpenSSL/0.9.8g mod_perl/2.0.4 Perl/v5.10.0 configured -- resuming normal operations

Hi, i was testing puppet postrun_command option and i found that it will be executed even if puppet run fails to complete successfully as seen in this snippets : debug: Executing ''rm /root/file'' > debug: catalog supports formats: b64_zlib_yaml dot marshal pson raw yaml; > using pson > err: Could not retrieve catalog from remote server: Error 400 on SERVER: > Could

Hi everyone, I have a puppet master/client infrastructure setup with apache. When on the same datacenter I don''t have any problem. I am trying to use another datacenter, so I setup the fileserver.conf as followed: # Files in the /path/to/files directory will be served # at puppet:///mount_point/. [modules] allow *.datacenter1 allow *.datacenter2 [plugins]

I am having issues with filebucket. I have looked through the puppet users google groups with similar issues but have not found a solution that works. I am trying to setup a central filebucket on the puppetmaster server. I am replacing the client''s /etc/puppet/puppet.conf file with a preconfigured version. The server delivers a copy of the puppet.conf file to the client, but the backup

I''m working on a system for auto-resigning certificates for our clients and Iv''e basically got it working .. but I notice that Puppet uses an inventory file and a serial # file that seem to be differently formatted than the openssl toolkit uses? The serial number file that puppet generates has a 4 digit number starting with 0000... but openssl tracks its serial numbers in a hex

OK. What did I booger up this time ? agent.myexample.org and puppetmaster.myexample.org are the same server. ---------------------------------------------------------------------------- # puppetd --no-daemonize --onetime --debug --noop debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not

Hello, I am running a puppet master version 2.7.5 on Centos 5.7 and a puppet agent version 2.7.5. I am simply trying to apply changes to files by defining a file resource in my manifest. When I execute my puppet agent to do the installation it complains it can not find the file meta data. Here is my manifest. class neospeech::config { file { "/usr/vwmrcpd/vwmrcpd/vwmrcpd":

Anyone know what this is? It doesn''t seem related to puppet but I''m stumped. info: Loading facts in dmidecode info: Loading facts in cpuinfo debug: catalog supports formats: b64_zlib_yaml marshal pson raw yaml; using pson /usr/lib64/ruby/site_ruby/1.8/puppet/indirector/rest.rb:55:in `deserialize'' /usr/lib64/ruby/site_ruby/1.8/puppet/indirector/rest.rb:69:in

Hello, I''m newbie for puppet. I would appreciate someone tells me how to use "shedule". What I want to do is puppet client( puppetd ) tries to syncronize /etc/ hosts permission as 644, and puppetd tries to check every 3 minutes. ( I know 3 min is so quick, this is just a test of "schedule") So I wrote manifests/site.pp, > node default { > schedule {