Both the client and the server are allowing port 8140 for tcp and udp. On Jan 10, 11:33 am, Mark Stanislav <[email protected]> wrote: > Any firewall (client or server) perhaps not explicitly allowing the proper > traffic for 8140 to the master? > > -Mark > > On Jan 10, 2011, at 11:27 AM, James Lee wrote: > > > Hi, I'm getting this message "Could not request certificate: No route > > to host - connect(2)" when I'm trying to connect my pclient to > > pmaster. > > > I checked my hostnames for both the pclient and the pmaster: > > [r...@pclient etc]# hostname -f > > pclient.domain > > > [r...@pmaster etc]# hostname -f > > pmaster.domain > > > I tried requesting for certificate: > > [r...@pclient etc]# puppetd --server pmaster.domain --no-daemonize -- > > waitforcert 60 --verbose > > > and all I get is the error message saying no route to host. What seems > > to be the problem? I saw a related discussion but I think I have the > > right server name. > > > I'm running Puppet 0.25.5 retrieved from the EPEL package, and the OS > > is CentOS 5. > > > Thanks, > > James > > > -- > > You received this message because you are subscribed to the Google Groups > > "Puppet Users" 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 > > athttp://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 [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-users?hl=en.
