On Tue, Dec 28, 2010 at 4:07 PM, Adam Nielsen <a.niel...@shikadi.net> wrote: > Hi all, > > I'm trying to do exactly the same thing as described on this bug report, and > I'm having exactly the same problem: > > http://projects.puppetlabs.com/issues/4762
Adam, can you vote or watch that bug please so we know other people are being affected by it? Updating the worklog to also say "I'm having this problem under these conditions" also lets the person who it is assigned to know that it's still an issue, and is affecting more than just the original reporter. > > The bug report seems to suggest that "editing the line on the puppet master" > will fix the problem, but I don't know what this means. Is this the > configtimeout or filetimeout config option? It's actually suggesting that you edit the puppet source code. Obviously this is not a long term solution, but it would be very helpful if you had success doing this and could let us know in the ticket. Depending upon your platform and installation, the puppet source code may live in various locations, but it's likely to be something like: /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb or /usr/lib/ruby/1.8/puppet/network/http/webrick.rb Are you actually using webrick as the puppet master? We do highly suggest that people set up Passenger or Mongrel with Apache for production environments, as webrick hits scalability limits rather quickly. http://projects.puppetlabs.com/projects/1/wiki/Using_Passenger http://projects.puppetlabs.com/projects/puppet/wiki/Using_Mongrel That's not to suggest this shouldn't be resolved for webrick however. > At the moment this is all I get when connecting to a puppetmaster (which > works fine with hosts on the same LAN, but this server is on the other side > of the world, ping time approx 175ms): > > # puppetd --server localhost --waitforcert 60 --test > warning: peer certificate won't be verified in this SSL session > err: Could not request certificate: SSL_connect SYSCALL returned=5 errno=0 > state=SSLv2/v3 read server hello A > > After this the server says: > > [2010-12-29 09:57:28] ERROR RuntimeError: Client disconnected before > connection could be established > /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:43:in > `listen' > /usr/lib/ruby/1.8/webrick/server.rb:173:in `call' > /usr/lib/ruby/1.8/webrick/server.rb:173:in `start_thread' > /usr/lib/ruby/1.8/webrick/server.rb:162:in `start' > /usr/lib/ruby/1.8/webrick/server.rb:162:in `start_thread' > /usr/lib/ruby/1.8/webrick/server.rb:95:in `start' > /usr/lib/ruby/1.8/webrick/server.rb:92:in `each' > /usr/lib/ruby/1.8/webrick/server.rb:92:in `start' > /usr/lib/ruby/1.8/webrick/server.rb:23:in `start' > /usr/lib/ruby/1.8/webrick/server.rb:82:in `start' > /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:42:in > `listen' > /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:41:in > `initialize' > /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:41:in > `new' > /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:41:in > `listen' > /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:38:in > `synchronize' > /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:38:in > `listen' > /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:127:in `listen' > /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:142:in `start' > /usr/lib/ruby/site_ruby/1.8/puppet/daemon.rb:124:in `start' > /usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:114:in > `main' > /usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:46:in > `run_command' > /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:287:in `run' > /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:393:in > `exit_on_fail' > /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:287:in `run' > /usr/bin/puppetmasterd:4 > > I assume the connection is working then, because if I try to telnet to port > 8140 on the puppetmaster I get disconnected before I can type a single > letter. Normally you get a few minutes before getting disconnected, so > either it's not working or the timeout defaults to a value far too low for > Puppet to work when the servers are a long distance apart. > > Any suggestions as to how I might get Puppet working with hosts on different > continents? > > Many thanks, > Adam. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@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-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
