On 11 March 2011 14:41, Luke Bigum <luke.bi...@lmax.com> wrote: > > I actually tried --waitforcert 480000 ! But it still hang and end up into > a > > certificate timeout : puppetd[2078]: Could not request certificate: > > Connection refused - connect(2) > > "Connection refused" sounds like networking or a firewall is in your > way. On your new Puppet client, can you "telnet puppetmaster.domain > 8140"? Assuming your Puppet Master is running on the default port of > 8140. >
Yep it does sounds like that, but as I can see the notice with the new instance name appears on the puppetmaster side I assume it wasn't the firewall. However, if I telnet on port 8140 I can't connect... I'm starting to wonder if my puppetmaster can't just handle the 4 instances starting up at the same time. It's far from being a big scale but I'm still using only on instance of puppetmasterd running with webbrick... Can this default setup supports more than one client at the time ? > What's the output of "puppetd --test" ? > puppetd --test warning: peer certificate won't be verified in this SSL session and then the certificate error. -- Romain PELISSE, *"The trouble with having an open mind, of course, is that people will insist on coming along and trying to put things in it" -- Terry Pratchett* http://belaran.eu/wordpress/belaran -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
