Error 400 on SERVER: No support for http method POST

[rjl]

Hi All,
I found a post from last year similar to this but it did not provide
me with a solution.

I just upgraded from 2.6.7 to 2.7.10. My clients that are still
running the older 2.6.7 version are working fine. However, my clients
that I have upgraded to 2.7.10 are throwing the following error:

Could not retrieve catalog from remote server: Error 400 on SERVER: No
support for http method POST

I am running passenger 3.0.5 on the puppet master.

Any help would be greatly appreciated.

[Craig White]

----
that seems to be the common error when the clients are running a puppet version that is newer than the puppet master.

Upgrade the puppet master, problem will be solved.

Craig

[rjl]

The puppet master is at the same version.

[root@stsdev-pri conf.d]# rpm -qa | grep puppet
puppet-server-2.7.10-1.el5
level3-osp-puppetmaster-2.2.07-el5
puppet-2.7.10-1.el5

[Shawn]

I noticed this problem today with a 2.6.3 client which was upgraded today to 2.7.10. Master is 2.6.3
Sent via BlackBerry

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

[rjl]

Thanks everyone. Seems like having an older version of Master causes
this problem but I do not have an older version. My clients and Master
are both 2.7.10.

Any ideas would be greatly appreciated. Thanks in advance.

[Craig White]

On Feb 8, 2012, at 9:40 AM, rjl wrote:

> Thanks everyone. Seems like having an older version of Master causes
> this problem but I do not have an older version. My clients and Master
> are both 2.7.10.

----
I'm thinking that perhaps you have more than 1 version of ruby/puppet installed on the server or possibly you never restarted the puppet master after the upgrade.

Craig

[Peter Berghold]

I ran into an issue a while back on my puppet master where I had upgraded puppet and the result put the puppet executables in a different directory than I expected.  The /etc/init.d script that I used to start puppet master was looking in the old directory and starting the wrong version.

Be sure you don't have something similar here.   In my case /usr/bin vs. /usr/sbin  (not sure which was right now..)

 

Craig

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

--
Peter L. Berghold
Owner, Shark River Technical Solutions LLC

[Nick Fagerlund]

And if you suspect this, you can test which version the agents are
ACTUALLY talking to by using a notify resource to log a message
containing the magic $serverversion variable. (http://
docs.puppetlabs.com/guides/faq.html#are-there-variables-available-
other-than-those-provided-by-facter)