Issue #3133 has been updated by Glenn Aaldering.
Hi guys,
Im not exactly sure if my problem is related to bug 3133 but it was the only
bug that shows the same error as i am seeing. We have a custom made module,
with a custom fact in it. This specific fact seems to create very long URL's.
My setup is build on nginx using mongrel instead of webrick.
This is the error im receiving:
err: Could not retrieve catalog from remote server: wrong status line:
"<HTML>"
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
According to bug 3133 this will be fixed in version 0.25.5. After trying the
latest source code via git, the problem still exists. Although the bug was
accepted, I managed to fix my problem because in my case, it was an nginx
issue. According to nginx documentation the default setting which gives me the
error is:
large_client_header_buffers 4 4k/8k
I solved my problem by adding a line in /etc/nginx/nginx.conf file at the http
section:
large_client_header_buffers 8 16k
And reloading nginx.
Thanks, Glenn
----------------------------------------
Bug #3133: On a failed request puppet error message is not very helpful
http://projects.puppetlabs.com/issues/3133
Author: Peter Meier
Status: Accepted
Priority: Normal
Assigned to:
Category:
Target version: 0.25.5
Affected version: 0.25.4
Keywords:
Branch:
After upgrading to 0.25.4 my OpenBSD clients failed to get the catalog. The
error I received was:
<pre>
err: Could not retrieve catalog from remote server: wrong status line: "<html>"
</pre>
The @--trace@@ looks like:
<pre>
info: Loading facts in xen
/usr/local/lib/ruby/1.8/net/http.rb:2031:in `read_status_line'
/usr/local/lib/ruby/1.8/net/http.rb:2018:in `read_new'
/usr/local/lib/ruby/1.8/net/http.rb:1059:in `request'
/usr/local/lib/ruby/1.8/net/http.rb:1046:in `request'
/usr/local/lib/ruby/1.8/net/http.rb:547:in `start'
/usr/local/lib/ruby/1.8/net/http.rb:1044:in `request'
/usr/local/lib/ruby/1.8/net/http.rb:781:in `get'
/usr/local/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:69:in `find'
/usr/local/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:195:in `find'
/usr/local/lib/ruby/site_ruby/1.8/puppet/indirector.rb:51:in `find'
/usr/local/lib/ruby/site_ruby/1.8/puppet/configurer.rb:106:in `retrieve_catalog'
/usr/local/lib/ruby/site_ruby/1.8/puppet/util.rb:418:in `thinmark'
/usr/local/lib/ruby/1.8/benchmark.rb:293:in `measure'
/usr/local/lib/ruby/1.8/benchmark.rb:307:in `realtime'
/usr/local/lib/ruby/site_ruby/1.8/puppet/util.rb:417:in `thinmark'
/usr/local/lib/ruby/site_ruby/1.8/puppet/configurer.rb:105:in `retrieve_catalog'
/usr/local/lib/ruby/site_ruby/1.8/puppet/configurer.rb:162:in `run'
/usr/local/lib/ruby/site_ruby/1.8/puppet/agent.rb:53:in `run'
/usr/local/lib/ruby/site_ruby/1.8/puppet/agent/locker.rb:21:in `lock'
/usr/local/lib/ruby/site_ruby/1.8/puppet/agent.rb:53:in `run'
/usr/local/lib/ruby/1.8/sync.rb:229:in `synchronize'
/usr/local/lib/ruby/site_ruby/1.8/puppet/agent.rb:53:in `run'
/usr/local/lib/ruby/site_ruby/1.8/puppet/agent.rb:134:in `with_client'
/usr/local/lib/ruby/site_ruby/1.8/puppet/agent.rb:51:in `run'
/usr/local/lib/ruby/site_ruby/1.8/puppet/application/puppetd.rb:103:in `onetime'
/usr/local/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in `send'
/usr/local/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in `run_command'
/usr/local/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run'
/usr/local/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in `exit_on_fail'
/usr/local/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run'
/usr/local/sbin/puppetd:159
err: Could not retrieve catalog from remote server: wrong status line: "<html>"
</pre>
After debugging a while I found out that using webrick it works, hence I
thought that the problem is related to my fronted proxy nginx. And yeah looks
like I encounter the famous 414 Request URI too long. However this was only
noted in the nginx-logs. I think puppet should a) at least print the status
code it received (414) and b) maybe be more verbose, so one could find the
error earlier and the error message makes more sense.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
