search for: b64_zlib_yaml

Should I be concerned of the following error? - Value of ''preferred_serialization_format'' (pson) is invalid for report, using default (b64_zlib_yaml) I''m running 0.25.4 on both server and clients and all are running Red Hat 5.4. Thanks, Clif -- 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 f...

...tificate for ubuntu05.wic.west.com debug: Finishing transaction 70059798542500 debug: Loaded state in 0.00 seconds debug: Using cached certificate for ca debug: Using cached certificate for ubuntu05.wic.west.com debug: Using cached certificate_revocation_list for ca debug: catalog supports formats: b64_zlib_yaml dot marshal pson raw yaml; using pson [snip] debug: Storing state debug: Stored state in 0.01 seconds notice: Finished catalog run in 0.16 seconds Changes: Events: Noop: 2 Total: 2 Resources: Total: 12 Out of sync: 2 Skipped: 6 Time: Fileb...

...: Fact syncing is deprecated as of 0.25 -- use ''pluginsync'' instead info: Retrieving fact debug: Using cached certificate for ca debug: Using cached certificate for puppet-client.ig.local debug: Using cached certificate_revocation_list for ca debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debu...

Hi all. I am testing 0.25.4 to upgrade from 0.23.2. In testing, I found two strange messages on 0.25.4 which I have never found on 0.24.3. So could you tell me what these messages mean and how to fix them. [Environment] Puppetmasterd -version : 0.25.4 -OS : Solaris10 10/09 Puppetd -version : same as Puppetmasterd -OS : same as Puppetmasterd [Strange messages] 1.When Puppetd

...tificate with success but now I''m struggle with apply simple puppet manifest site.pp. When I run Server and Client with no--daemonize and --debug I get error stack trace as fallow: Debug: Finishing transaction -615376128 Debug: Loaded state in 0.00 seconds Debug: node supports formats: b64_zlib_yaml pson raw yaml; using pson Debug: Using cached certificate for ca Debug: Using cached certificate for radkam Debug: Using cached certificate_revocation_list for ca Info: Retrieving plugin Debug: file_metadata supports formats: b64_zlib_yaml pson raw yaml; using pson Debug: Finishing transaction -61...

...et/ssl] debug: Finishing transaction 23934313889260 debug: Using cached certificate for ca debug: Using cached certificate for node12.localdomain notice: Ignoring --listen on onetime run debug: Finishing transaction 23934316140460 debug: Loaded state in 0.00 seconds debug: catalog supports formats: b64_zlib_yaml dot marshal pson raw yaml; using pson debug: Using cached certificate for ca debug: Using cached certificate for node12.localdomain debug: Using cached certificate_revocation_list for ca debug: Puppet::Type::Package::ProviderRpm: Executing ''/bin/rpm -- version'' debug: Puppet::Type...

Hi, On my puppet node, there are many facter variables that are empty in my manifests. But, there are not empty when I start "facter" on the node. why ? ex in a module: class resolver { if $::ipaddress6 { ... } $domainename = "$domain" } In this manifest, $domain and $ipaddress6 are empty In the facter command line, there not empty. -- You received this

...puppet/ssl/certs] debug: Finishing transaction 23912128448160 debug: Using cached certificate for ca debug: Using cached certificate for agent.myexample.org debug: Finishing transaction 23912127941800 debug: Loaded state in 0.02 seconds info: Retrieving plugin debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: Using cached certificate for ca debug: Using cached certificate for agent.myexample.org debug: Using cached certificate_revocation_list for ca err: /File[/var/lib/puppet/lib]: Failed to generate additional resources using ''eval_generate: Connection...

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

Good morning , I could help to debug this problem ? "puppet agent - test" Debug: catalog supports formats: b64_zlib_yaml dot pson raw yaml; using pson Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class pentaho for s <http://srvdev206.cia.stefanini.com/> erver.test.com /usr/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:185:in `is_http_200?'' /usr/lib/ruby/ve...

...sl/certs] debug: Finishing transaction 70313576769180 debug: Using cached certificate for ca debug: Using cached certificate for ubuntu.kna.citycloud.se debug: Finishing transaction 70313576344740 debug: Executing ''/etc/puppet/etckeeper-commit-pre'' debug: catalog supports formats: b64_zlib_yaml dot pson raw yaml; using pson debug: Using cached certificate for ca debug: Using cached certificate for ubuntu.kna.citycloud.se err: Could not retrieve catalog from remote server: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed. This is often beca...

...erver 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 /var/lib/puppet/reports. -- Marley Bacelar Project Fedora Ambassador VCP, VSP. VTSP., ITILF, IBM 000-076, IBM 000-330, IBM 000-331 marleybacelar@gmail.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" grou...

...sl/crl.pem]: Autorequiring File[/var/lib/puppet/ssl] debug: Finishing transaction 23702910393880 debug: Using cached certificate for ca debug: Using cached certificate for template.datacenter2 debug: Finishing transaction 23702909931920 info: Retrieving plugin debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: Using cached certificate for ca debug: Using cached certificate for template.datacenter2 debug: Using cached certificate_revocation_list for ca debug: Finishing transaction 23702909767560 info: Loading facts in puppet_vardir info: Loading facts in meminbytes...

Greetings. I am trying to set up a test puppet server in my environment to evaluate windows clients. On the server side, I am using puppet 2.7.14 (from the repos). I''m using the 2.7.14 windows 64 bit on the client (windows 2008 R2). I have another puppetmaster already using "puppet" hostname in DNS (running a very old version of puppet - can''t upgrade yet for various

...I run on a puppet agent: puppet agent —test And I got the error: "warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run" In the puppet server access_log I have: "GET /production/catalog/puppet.agent.domain?facts=eNqVV2… &facts_format=b64_zlib_yaml HTTP/1.1" *404* 343 "-" "-" And in the error_log I have: File does not exist: /usr/share/puppet/rack/puppetmasterd/public/production /usr/share/puppet/rack/puppetmasterd/public is empty. I just create it as part of the installation. What I''m missing? -- You r...

...315412980 debug: Loaded state in 0.04 seconds debug: Executing ''/etc/puppet/etckeeper-commit-pre'' debug: Using cached certificate for ca debug: Using cached certificate for pavml1.example.local debug: Using cached certificate_revocation_list for ca debug: catalog supports formats: b64_zlib_yaml dot marshal pson raw yaml; using pson info: Caching catalog for pavml1.example.local debug: Puppet::Type::Service::ProviderGentoo: file /sbin/rc-update does not exist debug: Puppet::Type::Service::ProviderRunit: file /usr/bin/sv does not exist debug: Puppet::Type::Service::ProviderDaemontools: file...

...g transaction -615437368 debug: Using cached certificate for ca debug: Using cached certificate for vagrant1.localdomain debug: Finishing transaction -615696088 debug: Loaded state in 0.00 seconds debug: Executing ''/etc/puppet/etckeeper-commit-pre'' debug: catalog supports formats: b64_zlib_yaml dot pson raw yaml; using pson debug: Using cached certificate for ca debug: Using cached certificate for vagrant1.localdomain debug: Using cached certificate_revocation_list for ca err: Could not retrieve catalog from remote server: Error 400 on SERVER: cannot generate tempfile `/var/lib/puppet/y...

Both the server and the client in this example are running 2.6.5: One class seems to be causing the error: debug: Value of ''preferred_serialization_format'' (pson) is invalid for report, using default (b64_zlib_yaml) debug: report supports formats: b64_zlib_yaml marshal raw yaml; using b64_zlib_yaml /var/lib/gems/1.8/gems/puppet-2.6.5/lib/puppet/resource.rb:396:in `extract_type_and_title'' /var/lib/gems/1.8/gems/puppet-2.6.5/lib/puppet/resource.rb:191:in `initialize'' /var/lib/gems/1.8/gems/pup...

...hat we''re finding is that often times the catalog is getting chopped off at some seemingly random point in the file. If you run puppet agent multiple times in a row each time it will cut off at always different parts. The error manifests itself like this: Debug: node supports formats: b64_zlib_yaml pson raw yaml; using pson Debug: Using cached certificate for ca Debug: Using cached certificate for ds0.lab.avere.net Debug: Using cached certificate_revocation_list for ca Info: Retrieving plugin Debug: file_metadata supports formats: b64_zlib_yaml pson raw yaml; using pson Debug: Finishing tran...

..., it comes up as an empty list. Moreover, /var/lib/puppet/facts is persistently empty. This has been happening with every client that I have checked. If run a packet capture on the puppetmaster paying attention to the puppetmaster ports, then I definitely see the puppetmaster receive the facts in b64_zlib_yaml format. I can even decode the facts string and get the correct set of facts. So the puppetmaster is definitely receiving the facts. However, in the same packet capture, I see the puppetmaster return json for resources as if it had not received any facts at all. I have even gone so far as to blo...