search for: client_yaml

...;'s a snippet of code that demonstrates my plight: https://gist.github.com/9667ad19762bf20bd947 The above works for only 1 of the 4 nodes, specifically the one that the commands are run on which is also the puppet master. This appears to be down to which files are present in /var/lib/puppet/ client_yaml/catalog. So I think I''m expecting there to be 4 files in that directory, one yaml file for each node. Instead I''m only seeing one. If I duplicate that file with the relevant node names the above code will run. Any pointers to what I''m doing wrong welcome. Cheers Garet...

...: /Stage[main]/Foreman::Config::Enc/File[/var/lib/puppet/yaml/foreman]/ensure: change from absent to directory failed: Cannot create /var/lib/puppet/yaml/foreman; parent directory /var/lib/puppet/yaml does not exist [root@ip-10-170-77-129 config]# mkdir /var/lib/puppet/ clientbucket/ client_data/ client_yaml/ facts/ lib/ ssl/ state/ Should the foreman puppet module be altered to say client_yaml instead of yaml? Was the foreman module was created with an older puppet version in mind? Or is this because I didn''t start my puppetmaster before using the foreman...

...: Could not send report: Error 403 on SERVER: *Forbidden request*: puppetm01.example.com(xxx.xxx.xxx.xxx) access to /report/puppetm01.example.com [save] at line 53 Below is the path to the catalog file to which I believe the error points. [root@puppetm01 ]# find /var/lib/puppet | grep catalog ./client_yaml/catalog ./client_yaml/catalog/puppetm01.example.com.yaml Thanks in advance for any pointers. ---- -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/x...

...Found seltype default ''puppet_var_lib_t'' for /var/lib/puppet/ssl/ private_keys/node13.pem debug: /File[/var/lib/puppet/ssl/private_keys/node13.pem]/selrange: Found selrange default ''s0'' for /var/lib/puppet/ssl/private_keys/ node13.pem debug: /File[/var/lib/puppet/client_yaml]/seluser: Found seluser default ''system_u'' for /var/lib/puppet/client_yaml debug: /File[/var/lib/puppet/client_yaml]/selrole: Found selrole default ''object_r'' for /var/lib/puppet/client_yaml debug: /File[/var/lib/puppet/client_yaml]/seltype: Found seltype default...

Hi All, We are observing frequently issue that Puppet agent intermittently stops without doing any thing when lot of puppet agent hitting puppet master . In our environment , we have configured puppet master over Apache-passenger and we have used LDAP as node classifier. - puppet 5.5 - Apache-passenger 3.0.17 - CentOS 6.3 / 5.5 - OpenLDAP 2.4 Sometimes restarting Apache solves

Hi, I have a problem with running puppet with hiera based data. I am trying to cleanup user accounts on a range of servers (to have the same uid/gid). When I create existing account but with different uid/gid it doesn''t change files group ownership so I need to run a script which cleanups after cleanup ;-) I use the following code: --- :backends: - yaml :hierarchy: -

Hi everyone, Do you if there a way to display a certain ressource attribut. For instance, I want to display the ''require'' of the User[''test''] Regards, JM -- 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

...:links=>:follow, :ensure=>:directory, :backup=>false, :owner=>"puppet", :path=>"/var/lib/puppet/ssl/certificate_requests", :loglevel=>:debug}'' Debug: Using settings: adding file resource ''clientyamldir'': ''File[/var/lib/puppet/client_yaml]{:links=>:follow, :ensure=>:directory, :backup=>false, :mode=>"750", :path=>"/var/lib/puppet/client_yaml", :loglevel=>:debug}'' Debug: Using settings: adding file resource ''hostprivkey'': ''File[/var/lib/puppet/ssl/private_keys/...

...quiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/client_data]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/client_yaml]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/state/graphs]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/ssl/private]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring File[/var/lib/puppet/ssl]...

...ays of scripting an inventory of managed resources on all nodes? I''ve found the inventory script by R.I.Pienaar ( http://www.devco.net/archives/2010/02/26/what_does_puppet_manage_on_a_node-2.php) which does what I want but only locally on each client. Is there any native way of syncing the client_yaml data centrally or any other way of doing this? I need a script-friendly way of checking which clients have this or that configuration, i.e. "which ip addresses are managed by puppet on client X" or "which files..." and so on. Regards, Adam -- You received this message becau...

...=>:directory, :backup=>false, :owner=>"puppet", >> :path=>"/var/lib/puppet/ssl/certificate_requests", :loglevel=>:debug}'' >> Debug: Using settings: adding file resource ''clientyamldir'': >> ''File[/var/lib/puppet/client_yaml]{:links=>:follow, :ensure=>:directory, >> :backup=>false, :mode=>"750", :path=>"/var/lib/puppet/client_yaml", >> :loglevel=>:debug}'' >> Debug: Using settings: adding file resource ''hostprivkey'': >> ''Fi...

...false, :path=>"C:/Documents and Settings/All Users/Application Data/PuppetLabs/puppet/etc/ssl/private"}'' Debug: Using settings: adding file resource ''clientyamldir'': ''File[C:/Documents and Settings/All Users/Application Data/PuppetLabs/puppet/var/client_yaml]{:loglevel=>:debug, :ensure=>:directory, :links=>:follow, :mode=>"750", :backup=>false, :path=>"C:/Documents and Settings/All Users/Application Data/PuppetLabs/puppet/var/client_yaml"}'' Debug: Using settings: adding file resource ''confdir...

1. I get the following error when I run “puppet device’ err: Could not request certificate: Could not write /var/opt/lib/pe-puppet/devices/certname/ssl/private_keys/certname.pem to privatekeydir: Permission denied - /var/opt/lib/pe-puppet/devices/certname/ssl/private_keys/certname.pem Any thought? Thanks, -- You received this message because you are subscribed to the Google Groups

...#39;'File[/var/lib/puppet/lib]{:links=>:follow, :ensure=>:directory, :back up=>false, :loglevel=>:debug, :path=>"/var/lib/puppet/lib"}'' Debug: Using settings: adding file resource ''clientyamldir'': ''File[/var/lib/puppet/client_yaml]{:links=>:follow, :ensure=>:direc tory, :backup=>false, :mode=>"750", :loglevel=>:debug, :path=>"/var/lib/puppet/client_yaml"}'' Debug: Puppet::Type::Group::ProviderPw: file pw does not exist Debug: Failed to load library ''ldap...

...puppet] debug: /File[/var/lib/puppet/state/last_run_summary.yaml]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/client_yaml]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring File[/var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/ssl/public_keys/vusion-production.pem]: Autorequiring File[/var/...

...ath=>"/Users/zach/.puppet/var/state/state.yaml", :mode=>"660", :ensure=>:file, :loglevel=>:debug, :links=>:follow, :backup=>false}'' Debug: Using settings: adding file resource ''clientyamldir'': ''File[/Users/zach/.puppet/var/client_yaml]{:path=>"/Users/zach/.puppet/var/client_yaml", :mode=>"750", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'' Debug: Using settings: adding file resource ''client_datadir'': ''File[/Users/zach/.puppet...

...iring File[/ var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/ puppet] debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/ puppet] debug: /File[/var/lib/puppet/ssl/private]: Autorequiring File[/var/lib/ puppet/ssl] debug: /File[/var/lib/puppet/client_yaml]: Autorequiring File[/var/lib/ puppet] debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring File[/var/ lib/puppet/ssl] debug: /File[/var/lib/puppet/clientbucket]: Autorequiring File[/var/ lib/puppet] debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring File[/var/lib/ puppet/ssl] debug: /F...

I too have been pushed into Puppet 3.0. Clients and PuppetMaster are now at 3.0.0. Not sure if this is a version change or syntax error that I am experiencing. We''ll use ''ntp'' as the example and the "build" host is a VM. The old way: class baseline::ntpd { package { "ntp": ensure => $virtual ? { physical => present,

Puppet 2.7.8rc1 is available. 2.7.8rc1 contains everything that was being previewed in the 2.7.7rc series as well as some new content. Key highlight in this release (beyond items from 2.7.7rc series) are: * Allow providers to be selected in the run they become suitable * Showdiff is now not auto-enabled when running in noop mode * Provide default subjectAltNames while bootstrapping

...ug: /File[/var/puppet/ssl/certs]: Autorequiring File[/var/puppet/ssl] debug: /File[/var/puppet/ssl/public_keys]: Autorequiring File[/var/puppet/ssl] debug: /File[/var/puppet/log]: Autorequiring File[/var/puppet] debug: /File[/var/puppet/ssl]: Autorequiring File[/var/puppet] debug: /File[/var/puppet/client_yaml]: Autorequiring File[/var/puppet] debug: /File[/var/puppet/run/puppetd.pid]: Autorequiring File[/var/puppet/run] debug: /File[/var/puppet/facts]: Autorequiring File[/var/puppet] debug: /File[/var/puppet/ssl/private_keys]: Autorequiring File[/var/puppet/ssl] debug: /File[/var/puppet/ssl/private]: Au...