Hi Felix, I tried "ping pmaster.domain" and it doesn't work (Destination Host Unreachable). I added an entry to /etc/hosts and it's still reacting the same. What might be wrong with my DNS?
On Jan 10, 11:30 am, Felix Frank <[email protected]> wrote: > On 01/10/2011 05:27 PM, 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. > > The master considering itself to be "pmaster.domain" is alright. > > But you want "ping pmaster.domain" to work for your client. If it > doesn't, this thing won't fly. > > If in doubt, add an entry to /etc/hosts. Otherwise you may want to take > a look at your DNS. > > Cheers, > Felix -- 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.
