Hi,
all of a sudden I''m getting this error "No support for http method
HEAD"
and I can''t figure why.
Full error message:
err: /Stage[main]/Unix/File[/etc/nsswitch.conf]/content: change from
{md5}581cc593069e5a59cde886d7491e9cf4 to {md5}7daae810b9cd3fb6cb21de13ceee9b2a
failed: Could not back up /etc/nsswitch.conf: Error 400 on SERVER: No support
for http method HEAD
Backing up files used to work for other nodes.
Im running 2.6.2 (Debian squeeze) on the puppetmaster, and just added a
SUSE Linux Enterprise 11 node running 2.6.17. Version mismatch issues?
thanks,
chakl
--
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.
Bernd Adamowicz
2012-Nov-12 12:47 UTC
RE: [Puppet Users] "No support for http method HEAD"
The versions might be the reason. Never run agents with a higher version than
the master. Try upgrading your master or downgrading your agent. Most presumably
this will solve the problem. If not, just get back to the list.
Bernd
-----Original Message-----
From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] On
Behalf Of Olaf Schreck
Sent: Montag, 12. November 2012 13:14
To: puppet-users@googlegroups.com
Subject: [Puppet Users] "No support for http method HEAD"
Hi,
all of a sudden I''m getting this error "No support for http method
HEAD"
and I can''t figure why.
Full error message:
err: /Stage[main]/Unix/File[/etc/nsswitch.conf]/content: change from
{md5}581cc593069e5a59cde886d7491e9cf4 to {md5}7daae810b9cd3fb6cb21de13ceee9b2a
failed: Could not back up /etc/nsswitch.conf: Error 400 on SERVER: No support
for http method HEAD
Backing up files used to work for other nodes.
Im running 2.6.2 (Debian squeeze) on the puppetmaster, and just added a SUSE
Linux Enterprise 11 node running 2.6.17. Version mismatch issues?
thanks,
chakl
--
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.
On Mon, Nov 12, 2012 at 01:47:33PM +0100, Bernd Adamowicz wrote:> The versions might be the reason. Never run agents with a higher version than the master. Try upgrading your master or downgrading your agent. Most presumably this will solve the problem. If not, just get back to the list.Thanks Bernd, that did the trick. In case someone is running Debian squeeze and having issues with the dated puppet-2.6.2: enable squeeze-backports and get puppet-2.7.18. Which also works with 2.7.17 agents on Novell SLE 11 SP1 nodes. -- 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.