Issue #3799 has been updated by Dan Bode.

Category changed from reports to serialization

I have seen this same error message when I have a fact that ends in a ':'

<pre>
info: Retrieving plugin
info: Loading facts in env
info: Loading facts in home
info: Loading facts in env
info: Loading facts in home
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:55:in `deserialize'
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:69:in `find'
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:202:in `find'
/usr/lib/ruby/site_ruby/1.8/puppet/indirector.rb:51:in `find'
/usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:208:in `retrieve_new_catalog'
/usr/lib/ruby/site_ruby/1.8/puppet/util.rb:418:in `thinmark'
/usr/lib/ruby/gems/1.8/gems/activesupport-2.2.2/lib/active_support/core_ext/benchmark.rb:8:in
 `realtime'
/usr/lib/ruby/site_ruby/1.8/puppet/util.rb:417:in `thinmark'
/usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:207:in `retrieve_new_catalog'
/usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:104:in `retrieve_catalog'
/usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:142:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:53:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/agent/locker.rb:21:in `lock'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:53:in `run'
/usr/lib/ruby/1.8/sync.rb:229:in `synchronize'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:53:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:134:in `with_client'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:51:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/application/puppetd.rb:103:in `onetime'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in `send'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in `run_command'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in `exit_on_fail'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run'
/usr/sbin/puppetd:160
err: Could not retrieve catalog from remote server: Error 400 on SERVER: Could 
not intern from b64_zlib_yaml: syntax error on line 31, col 459: `    
env_ls_colors: 
no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:ex=01;32:*.cmd=01;32:*.exe=01;32:*.com=01;32:*.btm=01;32:*.bat=01;32:*.sh=01;32:*.csh=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.bz=01;31:*.tz=01;31:*.rpm=01;31:*.cpio=01;31:*.jpg=01;35:*.gif=01;35:*.bmp=01;35:*.xbm=01;35:*.xpm=01;35:*.png=01;35:*.tif=01;35:'
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run

</pre>

this is created by the following fact (from the puppetmaster training course):

<pre>
require 'facter'
ENV.each do |k, v|
  Facter.add("env_#{k.downcase}") do
    setcode do
      v
    end
  end
end
</pre>
----------------------------------------
Bug #3799: Reporting failed: "could not intern from yaml" if output ends in 
colon
http://projects.puppetlabs.com/issues/3799

Author: Alan Harder
Status: Unreviewed
Priority: High
Assigned to: 
Category: serialization
Target version: 
Affected version: 0.25.5
Keywords: 
Branch: 


One of our recipes we gets this with 0.25.5, ruby 1.8.7 on Solaris 10:

<pre>err: Reporting failed: Error 400 on SERVER: Could not intern from yaml: 
syntax error on line 2819, col 61: `      message: You can find a log of this 
install session at:'</pre>

The "message" listed above is part of the output from the recipe, from an exec 
resouce with logoutput => true.  I can reproduce the problem with this simple 
test case:

<pre>exec { 'echo foo:': logoutput => true }</pre>

To workaround the warning message in the log about serialization format (which 
I understand in 0.25.5 final release is now "debug" level, yay), we had added 
this in puppet.conf:
<pre>preferred_serialization_format = marshal</pre>
I've now tried yaml, b64_zlib_yaml and pson instead but got the same error 
(specifying pson results in b64_zlib_yaml being used).  raw got a different 
error.



-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en.

Reply via email to