On Mar 11, 1:49 pm, Romain Pelisse <bela...@gmail.com> wrote: > On 11 March 2011 14:41, Luke Bigum <luke.bi...@lmax.com> wrote: > > "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 ?
I don't know webrick much at all to be honest, but I'm sure it can support more than one. Forgive the stupid question but you don't have another host with the same name somewhere that you're confusing log messages with? You could always try spin up another puppetmaster process on a different port and try connect to that - check the command line options, I'm going by memory: puppetmaster --no-daemonize --verbose --server_port=8141 Which should print to stdout, and only be your new server (trying) to connect. That'll confirm/deny a network problem. > > What's the output of "puppetd --test" ? > > puppetd --test > warning: peer certificate won't be verified in this SSL session -- 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.
