Puppet users - Jan 2011 - Could not request certificate: No route to host?

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:
[root@pclient etc]# hostname -f
pclient.domain

[root@pmaster etc]# hostname -f
pmaster.domain

I tried requesting for certificate:
[root@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 puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

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:
> [root@pclient etc]# hostname -f
> pclient.domain
> 
> [root@pmaster etc]# hostname -f
> pmaster.domain
> 
> I tried requesting for certificate:
> [root@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 puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

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:
> [root@pclient etc]# hostname -f
> pclient.domain
> 
> [root@pmaster etc]# hostname -f
> pmaster.domain
> 
> I tried requesting for certificate:
> [root@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 puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
puppet-users+unsubscribe@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-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Both the client and the server are allowing port 8140 for tcp and
udp.

On Jan 10, 11:33 am, Mark Stanislav <mark.stanis...@gmail.com>
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:
> > [root@pclient etc]# hostname -f
> > pclient.domain
>
> > [root@pmaster etc]# hostname -f
> > pmaster.domain
>
> > I tried requesting for certificate:
> > [root@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 puppet-users@googlegroups.com.
> > To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
> > 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 puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

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 <felix.fr...@alumni.tu-berlin.de>
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:
> > [root@pclient etc]# hostname -f
> > pclient.domain
>
> > [root@pmaster etc]# hostname -f
> > pmaster.domain
>
> > I tried requesting for certificate:
> > [root@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 puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On 01/10/2011 05:41 PM, James Lee wrote:
> 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?
Your master is not available network-wise. This can have any number of
reasons (IP not bound, routing issues etcpp.)

Impossible to debug from here without much more info. Are you
responsible for network infrastructure? If not, get someone who is and
make him debug this for you.

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 puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Thanks for the tip, I think I will figure it out :)

On Jan 10, 11:52 am, Felix Frank <felix.fr...@alumni.tu-berlin.de>
wrote:
> On 01/10/2011 05:41 PM, James Lee wrote:
>
> > 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?
>
> Your master is not available network-wise. This can have any number of
> reasons (IP not bound, routing issues etcpp.)
>
> Impossible to debug from here without much more info. Are you
> responsible for network infrastructure? If not, get someone who is and
> make him debug this for you.
>
> 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 puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Hi James,

 Since you are getting a "Destination Host Unreachable"  from the ping
command, do a netstat -nr command
and verify that you have a default route for your primary NIC. If not, then add
one with the route command.

Good Luck,

Mike

-----Original Message-----
From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] On
Behalf Of James Lee
Sent: Monday, January 10, 2011 11:42 AM
To: Puppet Users
Subject: [Puppet Users] Re: Could not request certificate: No route to host?

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 <felix.fr...@alumni.tu-berlin.de>
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:
> > [root@pclient etc]# hostname -f
> > pclient.domain
>
> > [root@pmaster etc]# hostname -f
> > pmaster.domain
>
> > I tried requesting for certificate:
> > [root@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 puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.


_____________________________________________________________________
PLEASE NOTE: Florida has a very broad public records law (F. S. 119).
All e-mails to and from County Officials are kept as a public record.
Your e-mail communications, including your e-mail address may be
disclosed to the public and media at any time.

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.