Puppet users - Apr 2012 - Puppet Server 2.6.9 and Puppet Client 2.7.6 (Mac)

Hi Folks, 

Our Mac clients are running Puppet 2.7.6 (via Mac Ports) but get the following
error when trying to connect to our 2.6.9 server:
> err: Could not retrieve catalog from remote server: Error 400 on SERVER: No
support for http method POST
> info: Not using expired catalog for client.example.com from cache; expired
at Wed Feb 22 23:30:29 -0800 2012
> notice: Using cached catalog
> err: Could not retrieve catalog; skipping run 




Two questions:

1) are there any tweaks to our existing Puppet server config files that will fix
this?

2) is upgrading our server to 2.7.6 a fairly significant project?

Thanks for your help and suggestions. 

Best, Doug


-- 
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 from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

For me, the server upgrade was as easy as using apt.puppetlabs.com (or
yum.puppetlabs.com) and doing ''apt-get install puppetmaster-passenger;
apt-get remove puppetmaster''. That gave me the Puppet Labs passenger
install instead of the Debian-packaged puppetmaster. (Albeit that I did these
steps using puppet rather than manually.)

I haven''t had any issues with my manifests save having to "require
''digest/md5''" in two erb templates in a single module.



On Tue, Apr 10, 2012 at 11:30:36AM -0700, Doug Niven
wrote:
> Hi Folks, 
> 
> Our Mac clients are running Puppet 2.7.6 (via Mac Ports) but get the
following error when trying to connect to our 2.6.9 server:
> 
> > err: Could not retrieve catalog from remote server: Error 400 on
SERVER: No support for http method POST
> > info: Not using expired catalog for client.example.com from cache;
expired at Wed Feb 22 23:30:29 -0800 2012
> > notice: Using cached catalog
> > err: Could not retrieve catalog; skipping run 
> 
> 
> 
> 
> 
> Two questions:
> 
> 1) are there any tweaks to our existing Puppet server config files that
will fix this?
> 
> 2) is upgrading our server to 2.7.6 a fairly significant project?
> 
> Thanks for your help and suggestions. 
> 
> Best, Doug
> 
> 
> -- 
> 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 from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
> 
> 
-- 
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 from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.