Could not intern from yaml: instance of IO needed

[Monir Miloudi]

Hi everyone,


My setup :

• MASTER :

facter-1.7.1-7.1.x86_64
puppet-2.7.23-1.el6.noarch
puppet-server-2.7.23-1.el6.noarch
ruby-1.8.7.352-12.el6_4.x86_64
ruby-augeas-0.4.1-2.15.x86_64
rubygem-json-1.4.6-3.4.x86_64
rubygems-1.3.7-13.1.noarch
ruby-libs-1.8.7.352-12.el6_4.x86_64
ruby-rgen-0.6.2-4.1.noarch
ruby-shadow-1.4.1-5.1.x86_64

• SLAVE :

facter-1.5.9-1.el4
puppet-0.25.6-1.el4
ruby-1.8.1-18.el4
ruby-augeas-0.4.1-1.el4
ruby-libs-1.8.1-18.el4

When running Puppet agent on my SLAVE machine, I got the following output :
# puppetd --test --debug --trace
[...]
debug: catalog supports formats: marshal pson raw; using pson
/usr/lib/site_ruby/1.8/puppet/indirector/rest.rb:55:in `deserialize'
/usr/lib/site_ruby/1.8/puppet/indirector/rest.rb:69:in `find'
/usr/lib/site_ruby/1.8/puppet/indirector/indirection.rb:202:in `find'
/usr/lib/site_ruby/1.8/puppet/indirector.rb:57:in `find'
/usr/lib/site_ruby/1.8/puppet/configurer.rb:207:in `retrieve_new_catalog'
/usr/lib/site_ruby/1.8/puppet/configurer.rb:206:in `thinmark'
/usr/lib/site_ruby/1.8/puppet/util.rb:403:in `measure'
/usr/lib/ruby/1.8/benchmark.rb:342:in `realtime'
/usr/lib/site_ruby/1.8/puppet/util.rb:403:in `thinmark'
/usr/lib/site_ruby/1.8/puppet/configurer.rb:208:in `retrieve_new_catalog'
/usr/lib/site_ruby/1.8/puppet/configurer.rb:104:in `retrieve_catalog'
/usr/lib/site_ruby/1.8/puppet/configurer.rb:142:in `run'
/usr/lib/site_ruby/1.8/puppet/agent.rb:53:in `run'
/usr/lib/site_ruby/1.8/puppet/agent.rb:53:in `lock'
/usr/lib/site_ruby/1.8/puppet/agent.rb:53:in `run'
/usr/lib/site_ruby/1.8/puppet/agent.rb:53:in `synchronize'
/usr/lib/site_ruby/1.8/puppet/agent.rb:53:in `run'
/usr/lib/site_ruby/1.8/puppet/agent.rb:51:in `with_client'
/usr/lib/site_ruby/1.8/puppet/agent.rb:60:in `run'
/usr/lib/site_ruby/1.8/puppet/application/puppetd.rb:103:in `onetime'
/usr/lib/site_ruby/1.8/puppet/application/puppetd.rb:94:in `onetime'
/usr/lib/site_ruby/1.8/puppet/application.rb:226:in `send'
/usr/lib/site_ruby/1.8/puppet/application.rb:226:in `run_command'
/usr/lib/site_ruby/1.8/puppet/application.rb:217:in `run'
/usr/lib/site_ruby/1.8/puppet/application.rb:217:in `exit_on_fail'
/usr/lib/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 yaml: instance of IO needed
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run

I tried setting multiple variables in the SLAVE puppet.conf (and I validated them by running "puppetd --configprint catalog_format"), such as :
catalog_format = [marshal|pson|raw]
preferred_serialization_format = [marshal|yaml]

I took a look at the following bugs on Puppetlabs tracker and Google'd this error, but to no avail :

• https://projects.puppetlabs.com/issues/3799
• https://projects.puppetlabs.com/issues/3957

Unfortunately, except for the "--trace" option of Puppet agent, I cannot find a way to debug this issue in a more verbose manner.

Do you think this issue could be resolved by :

• upgrading my Puppet agent version (given that it does not exceed the version of the Puppet Master) ?
• upgrading the Ruby package (to maybe 1.8.5) ?

Thanks in advance.

[Andy Parker]

On Mon, Feb 24, 2014 at 8:56 AM, Monir Miloudi <mmil...@gmail.com> wrote:

Hi everyone,


My setup :

• MASTER :

facter-1.7.1-7.1.x86_64
puppet-2.7.23-1.el6.noarch
puppet-server-2.7.23-1.el6.noarch
ruby-1.8.7.352-12.el6_4.x86_64
ruby-augeas-0.4.1-2.15.x86_64
rubygem-json-1.4.6-3.4.x86_64
rubygems-1.3.7-13.1.noarch
ruby-libs-1.8.7.352-12.el6_4.x86_64
ruby-rgen-0.6.2-4.1.noarch

I wouldn't have expected to see ruby-rgen installed on a system with puppet 2.7. Rgen is something used by the puppet 3 series as part of the new parser/evaluator. Do you maybe have a mixed install of puppet? This can happen if you install with the OS's packaging system (rpm) and as a gem. That wouldn't have caused you to get the rgen package in rpm, but maybe something else is going on here.

 

ruby-shadow-1.4.1-5.1.x86_64

• SLAVE :

facter-1.5.9-1.el4
puppet-0.25.6-1.el4

We normally only maintain puppet to keep compatibility one version back, with a bit of added confusion with the switch to semver for puppet 3. It ends up meaning that for the 2.7 system it should be used with 2.6 or 2.7 agents. For Puppet 3.x it should be used with 2.7 agents.

The error is coming from the master. You'll need to run your master with --trace.

 

Do you think this issue could be resolved by :

• upgrading my Puppet agent version (given that it does not exceed the version of the Puppet Master) ?
• upgrading the Ruby package (to maybe 1.8.5) ?

Thanks in advance.

--
You received this message because you are subscribed to the Google Groups "Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/84740fdf-9f00-4ab1-9a1b-b01218288358%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--

Andrew Parker

an...@puppetlabs.com

Freenode: zaphod42

Twitter: @aparker42

Software Developer

Join us at PuppetConf 2014, September 23-24 in San Francisco - http://bit.ly/pupconf14