Get Fedora 19 client working with CentOS 6.4 master

[xbglowx]

I have a CentOS 6.4 puppet masters that has puppet-server-3.3.1-1.el6.noarch installed. I am trying to get a puppet client fedora19 working, which has puppet-3.3.1-1.fc19.noarch installed.

If I run puppet agent:

/usr/bin/puppet agent --onetime --no-daemonize --verbose --server=<puppet_server> --environment=development --tags <tags> --color=false

I get a bunch of "incorrect header check" like the following during my puppet runs:

Error: /File[/var/lib/puppet/lib/puppet/parser/functions/gsub.rb]/ensure: change from absent to file failed: Could not set 'file' on ensure: incorrect header check
Error: Could not set 'file' on ensure: incorrect header check
Error: Could not set 'file' on ensure: incorrect header check
Wrapped exception:
incorrect header check
Error: /File[/var/lib/puppet/lib/puppet/provider/database_grant/mysql.rb]/ensure: change from absent to file failed: Could not set 'file' on ensure: incorrect header check
Error: Could not set 'file' on ensure: incorrect header check
Error: Could not set 'file' on ensure: incorrect header check
Wrapped exception:
incorrect header check
Error: /File[/var/lib/puppet/lib/puppet/parser/functions/values_at.rb]/ensure: change from absent to file failed: Could not set 'file' on ensure: incorrect header check
Error: Could not set 'file' on ensure: incorrect header check
Error: Could not set 'file' on ensure: incorrect header check
Wrapped exception:
incorrect header check
Error: /File[/var/lib/puppet/lib/puppet/parser/functions/getvar.rb]/ensure: change from absent to file failed: Could not set 'file' on ensure: incorrect header check
Error: Could not set 'file' on ensure: incorrect header check
Error: Could not set 'file' on ensure: incorrect header check

Not sure where to go from here. I see the respective files on the puppet master, but not sure what is going on under the cover.

[Josh Cooper]

The "incorrect header check" is not coming from puppet, but likely the zlib library when puppet tries to decompress the file during pluginsync. Or perhaps the master is claiming that the file is compressed, when it's actually not, or vice-versa?

Do you have `http_compression` set on the agent? Try running with --trace on the agent.

Not sure where to go from here. I see the respective files on the puppet master, but not sure what is going on under the cover.

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/2a7637d3-ba56-4cb1-af4d-44645ff9516f%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--

Josh Cooper

Developer, Puppet Labs

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

Register now and save $350!