similar to: Puppet client - could not parse YAML data

I am working on building a facter tag based node classifier similar to https://github.com/jordansissel/puppet-examples/tree/master/nodeless-puppet/. However, I have run into an issue where I cannot use puppet''s require file ability to push the yaml file containing the facts file to the client because it would require two runs of puppet to pickup changes. Consequently, I have written into

I keep on getting this message: err: Too many open files - /var/lib/puppet/state/state.yaml.tmp Does anybody know what might be causing it? I''m also getting "err: State got corrupted". Everything does seem to be kind of working, but it''s sort of worrying getting these new errors. -- You received this message because you are subscribed to the Google Groups

Hi, I reinstalled puppet-server and am now getting these error messages from clients: err: /File[/var/lib/puppet/facts]: Failed to generate additional resources during transaction: No such file or directory - /var/lib/puppet/yaml/node err: /File[/var/lib/puppet/facts]: Failed to retrieve current state of resource: No such file or directory - /var/lib/puppet/yaml/node Could not describe /facts:

Hi folks, When running puppetd --environment whatever, the environment is not taken into account on the puppetmaster. This bug appeared after ticket #1130 got resolved and is certainly due to caching of the node terminus. Looking through the code didn''t help me understand how this yaml cache should get refreshed. On the puppetmaster, the cache files located in

While running puppetd on a linux client I get the following, the actual spot that the segfault happens varies, but it always happens. This is on ubuntu with the stock apt ruby1.8.4 package. Puppet also installed from apt. Puppet version 0.18.4 It seems very likely that this isnt a bug in puppet per se, but it is tickling a yaml bug (regardless of where it fails, it is always yaml). But I

Hello, A quick search showed some people may have got this working. Anyone got a Python (or Perl) script to parse the Puppet reports and put them into a human readable format ? Might be able to knock something together myself but not used PyYAML too much and might need some pointers. Thanks -- You received this message because you are subscribed to the Google Groups "Puppet

Hi, i''m a newbie about Puppet( 1 month ~) i got error on generate temp file, i''ll explain my situation: -i have a puppetmaster(version: 3.3.0),executed on root and a puppet agent(version 2.7) provisioning by vagrant,executed on root -my site.pp, where webserv is a parametrized class, and typews is a parameter to choice nginx or lamp module, -i have my Enc node with path

err: /Settings[top]/Settings[main]/File[/usr/local/.aqadmin/puppet/var/yaml]: Failed to retrieve current state of resource: Could not find user puppet debug: Finishing transaction 75413780 with 2 changes since i put the last version on this test server i cannot launch puppet manualy: mkdir -m 700 -p /usr/local/.aqadmin/puppet/conf/ssl; \ mkdir -m 700 -p /usr/local/.aqadmin/puppet/var/facts; \

Hi, I was wondering what people out there are doing to monitor puppetd in large environments. I''d love to hear what the best practices are around this. We have a few hundred hosts and are currently looking at the timestamps on the yaml files in /var/lib/puppet/yaml/facts/ on puppetmasters to make sure all clients are alive. Is it true that for a given client the fact file on the

Has anyone else ran into this? debug: /Stage[main]/Mcollective/File[/var/tmp/facts.yaml]/content: Executing ''diff -u /var/tmp/facts.yaml /tmp/puppet-file20121214-13448-933j3r-0'' notice: /Stage[main]/Mcollective/File[/var/tmp/facts.yaml]/content: --- /var/tmp/facts.yaml 2012-12-14 00:53:20.000000000 +0000 +++ /tmp/puppet-file20121214-13448-933j3r-0 2012-12-14

Hi, I exposed few days ago this situation on the IRC, but unfortunately I haven''t found a way to solve it yet. I run the Puppet Master with multiple environments, and everything is working good but a couple of nodes that are causing me some troubles. These nodes are pointing to my production environment and I need to point them back to development to grab some changes I made. I

For some reason I am unable to run "dry runs" of the puppet client on my puppetmaster server. Running puppetd with the --test, --noop and verbose / debug flags results in nothing for about a minute or two then this output... $ time puppetd --test --noop -v err: Could not retrieve catalog from remote server: execution expired warning: Not using cache on failed catalog err: Could not

I change my ubuntu to mac os, and rsync my puppet file to the puppet server. I run puppetd -tv in the client, and then this error happens puppetd -tv err: Could not retrieve catalog: Could not parse for environment production: Could not find file /etc/puppet/manifests/site.pp warning: Not using cache on failed catalog -- You received this message because you are subscribed to the Google Groups

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

Hello all, After banging my head against my desk for a few hours, I''m posting here (after being told this isn''t a bug). I''m trying to use puppet to install some packages on my fedora clients, som on my puppet master i created a class with the following contents: class fedora-ws { include atrpms-repo $packages = ["subversion"] package

Greetings, I''ve two questions for y''all. 1) I''ve setup an alternate installation path for puppet in a site local directory outside of ''the usual places''. Puppetd seems to insist that /etc/puppet/namespaceauth.conf exists despite setting :authconfig in both puppet and puppetd. As a result part of my installation now includes a symlink to point

Hey Nick, what's the status on YAML IO? The other thread seems to have died. -- Sean Silva

Hi, I have run into an issue using puppet in an ldap environment and I am wondering if anyone else has run into the same issue. A number of the puppet clients in my testing environment are failing to apply new configurations because the puppet client is getting an ldap error. Currently, I am attempting to push a new bash_profile to my home directory and then set my username/group to then own the

On Oct 22, 2012, at 4:40 PM, Sean Silva wrote: > Hey Nick, what's the status on YAML IO? The other thread seems to have died.\ I'm waiting on Michael Spencer's feedback. The issues I know of right now are: 1) Should we structure YAML I/O to be a more general I/O utility that could support reading and writing other data formats such as JSON or plists. RIght now, all the code is

Anyone have a more extensive yaml file for jqgrid than the one that''s shown with the example Jqgrid Demos page? Also, I''ve been successful in just using the straight jQuery javascript code, rather than invoking the yaml file to produce it), but sometimes get an "unitialized class variable @@grid_name" error. I was doing this because all the code I see on the web to