search for: preferred_serialization_format

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...

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 /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 y...

...[update]/returns: executed successfully err: //aguu/Exec[upgrade]/returns: change from notrun to 0 failed: apt-get upgrade -y returned 100 instead of one of [0] at /etc/puppet/modules/aguu/manifests/init.pp:11 notice: //testmodule1/File[/tmp/testmodule]/ensure: created warning: Value of ''preferred_serialization_format'' (pson) is invalid for report, using default (marshal) notice: Finished catalog run in 3.60 seconds Apt-get should be returning 100 in case of an error, but if i run the exact same command from command line it runs fine. Any suggestions what should be going wrong? -- You received this...

...ing: path / auth any allow * And here’s the puppet.conf (the same on master and all agents) [main] logdir = /var/log/puppet rundir = /var/run/puppet ssldir = $vardir/ssl [agent] server = <hidden> classfile = $vardir/classes.txt report = true listen = true localconfig = $vardir/localconfig preferred_serialization_format = yaml [master] certname = <hidden> reports = http, store reporturl = http://<hidden>:3000/reports/upload pluginsync = true storeconfigs = true dbadapter = mysql dbuser = root dbpassword = dbserver = localhost dbsocket = /var/lib/mysql/mysql.sock I don''t know how to go about...

...ed in a future version. *Error: Could not retrieve local facts: undefined method `get_uptime'' for Facter::Util::Uptime:Module Error: Failed to apply catalog: Could not retrieve local facts: undefined method `get_uptime'' for Facter::Util::Uptime:Module* Debug: Value of ''preferred_serialization_format'' (pson) is invalid for report, using default (yaml) *Debug: report supports formats: b64_zlib_yaml raw yaml; using yaml /usr/lib/ruby/gems/1.8/gems/puppet-3.1.1/lib/puppet/agent.rb:89:in `exit'': no implicit conversion from nil to integer (TypeError)* *from /usr/lib/ruby/gems/1.8...

...Package: 0.00 Exec: 0.00 Config retrieval: 0.44 Total: 0.45 Last run: 1313600473 debug: Using cached certificate for ca debug: Using cached certificate for ubuntu05.wic.west.com debug: Using cached certificate_revocation_list for ca 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 Master Log: info: Expiring the node cache of ubuntu05.wic.west.com info: Not using expired node for ubuntu05.wic.west.com from cache; expired at...

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

...= /var/lib/puppet/ssl rundir = /var/run/puppet factpath = $vardir/lib/facter pluginsync = true templatedir = $confdir/templates [agent] report = true environment = production preferred_serialization_format = yaml [master] modulepath = /etc/puppet/environments/$environment/modules:/etc/puppet/modules manifest = /etc/puppet/manifests/site.pp environment = production autosign = false ssl_client_header = SSL_CLIENT_S_DN ssl_client_...

...fdir/environments/$environment/manifests/site.pp modulepath=$confdir/environments/$environment/modules storeconfigs = true thin_storeconfigs = true dbadapter = mysql dbuser = puppet dbpassword = puppetpass dbserver = db.mydomain pluginsync = true graph = true preferred_serialization_format = yaml And Ive got plugins in modules/custom_facts/lib/facter/ Running this: puppet apply --environment=$PUPPET_ENV --modulepath=/etc/puppet/environments/$PUPPET_ENV/modules --pluginsync --storeconfigs /etc/puppet/environments/$PUPPET_ENV/manifests/site.pp --verbose --factsync --debug but there...

After updating master from 2.7.12 to 3.0.1 I noticed, that agents began spending more time on "File" resources, which I can see from --summarize output: about 40-45 seconds now, and about 25-30 before update. What could cause this problem? I also noticed, that "preferred_serialization_format = b64_zlib_yaml" doesn''t work anymore and "pson" is used by default, so could the absence of compression cause this problem ? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web v...

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 {

...Using cached certificate for puppet.domain.com debug: Using cached certificate_revocation_list for ca *err: Could not retrieve catalog from remote server: 403 "Forbidden"* warning: Not using cache on failed catalog *err: Could not retrieve catalog; skipping run* debug: Value of ''preferred_serialization_format'' (pson) is invalid for report, using default (yaml) debug: report supports formats: b64_zlib_yaml raw yaml; using yaml *err: Could not send report: 403 "Forbidden"* -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To...

...talog from remote server: Error 400 on SERVER: Is a directory - /etc/puppet/modules/network/templates/ at /etc/puppet/modules/network/manifests/hosts.pp:10 on node template.datacenter2 warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run debug: Value of ''preferred_serialization_format'' (pson) is invalid for report, using default (marshal) debug: report supports formats: b64_zlib_yaml marshal raw yaml; using marshal The 2 datacenter are connected by VPN and normally everything is open from datacenter2 to datacenter1 but datacenter1 can''t access datacenter2 exc...

...in noop = false onetime = false passfile = /var/lib/puppet/ssl/private/password path = none pidfile = /var/run/puppet/apply.pid plugindest = /var/lib/puppet/lib pluginsignore = .svn CVS .git pluginsource = puppet://puppet/plugins pluginsync = true postrun_command = /etc/puppet/etckeeper-commit-post preferred_serialization_format = pson prerun_command = /etc/puppet/etckeeper-commit-pre privatedir = /var/lib/puppet/ssl/private privatekeydir = /var/lib/puppet/ssl/private_keys publickeydir = /var/lib/puppet/ssl/public_keys puppetdlockfile = /var/lib/puppet/state/puppetdlock puppetdlog = /var/log/puppet/puppetd.log puppetport =...

...certificate B: certificate verify failed. This is often because the time is out of sync on the server or client warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run debug: Executing ''/etc/puppet/etckeeper-commit-post'' debug: Value of ''preferred_serialization_format'' (pson) is invalid for report, using default (b64_zlib_yaml) debug: report supports formats: b64_zlib_yaml raw yaml; using b64_zlib_yaml err: Could not send report: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed. This is often because the...

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/puppe...

...d for getting facts from Facter warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run debug: Using cached certificate for ca debug: Using cached certificate for puppet-client.ig.local debug: Using cached certificate_revocation_list for ca debug: Value of ''preferred_serialization_format'' (pson) is invalid for report, using default (marshal) debug: report supports formats: b64_zlib_yaml marshal raw yaml; using marshal Puppet version is 2.7.6 on debian Squeeze. Configs are copied from currently running system, only changes are done with stored configs (which works, DB was...

...pson err: Could not retrieve catalog from remote server: Connection refused - connect(2) info: Not using expired catalog for agent.myexample.org from cache; expired at Tue Jun 05 13:43:17 -0400 2012 notice: Using cached catalog err: Could not retrieve catalog; skipping run 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 err: Could not send report: Connection refused - connect(2) ------------------------------------------------------------------------------ “Some...

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

...and `resource` endpoints. # listen = false # Where puppet agent stores the last run report summary in yaml format. # The default value is ''$statedir/last_run_summary.yaml''. lastrunfile = /var/lib/puppet/state/last_run_summary.yaml # (Deprecated for ''preferred_serialization_format'') What format to # use to dump the catalog. Only supports ''marshal'' and ''yaml''. Only # matters on the client, since it asks the server for a specific format. # The default value is ''''. # catalog_format = # Where to...