Re: Need help! Puppet could not request certificate: No route to host -connect(2)

[Schofield]

Try using "telnet <your_master_fqdn> 8140"  This will validate the network on the proper port.  ping does not use port 8140.

[mart...@gmail.com]

I am able to ssh to both host.  Am now getting the error:  [Could not request certificate:  Connection refused]

This error is different to the first error.  This one seems to deal with IP Tables rules.

[Przemek]

You get also this error when puppet master server is disabled or unresponsive (there is no response to the client and you get error)

Make sure that your puppet master server is running by command:

ps -aux

If process is running and you still get this error message, kill this process (kill 'PID') and try run server in no--damenoize mode by command:

puppet master --no-daemonize --verbose

then try connect again and observe server responses

Best Regards

W dniu wtorek, 23 kwietnia 2013 16:57:02 UTC+2 użytkownik mart...@gmail.com napisał:

Hello,

I am installing puppet and keep getting this error [Puppet could not request certificate:  No route to host -connect(2)]

My DNS is resloving and i can ping the master from the agent. 

I have added this line to the iptables [iptables  -I INPUT -s 192.168.1.20 -m tcp -p tcp --dport 8140 -j ACCEPT], where the IP is my agent.

I have also added my master ip to /etc/puppet/puppet.conf

Why am I still getting this error? 

[Felix Frank]

On 04/24/2013 02:34 PM, Przemek wrote:
> ps -aux

That should just be "ps aux", no dash, actually.

On 04/24/2013 12:24 AM, mart...@gmail.com wrote:
> I am able to ssh to both host. Am now getting the error: [Could not
> request certificate: Connection refused]
>
> This error is different to the first error. This one seems to deal with
> IP Tables rules.

It pretty much says that the port is not open. This may or may not be
iptables related.

On the agent, make extra sure that "puppet" (or whatever you use as
servername) resolves to a valid IP of the master machine.

On the master, use "netstat -tlnp" to verify that there is indeed a
process listening to port 8140, either on 0.0.0.0 or the dedicated
master IP address. In the former case, make sure the master IP is bound
to the machine.

HTH,
Felix

[rony thomas]

Could you add the hostnames and IP addresses of master and client in /etc/hosts on both master and client. On RHEL 5.8, I was able to fix this error  after flushing the iptables with "iptables -F" and then saving it with "service iptables save".

 

 

Kind Regards,

Rony Thomas

[Philip Mosquera]

I was in the exact same situation and found a dirty solution was to simply to use service iptables stop.

It's a bit of a dirty workaround and definitely wouldn't recommend it on an open network but it solved the issue for me to use it on a few internal vms.

Hope it helped.

[Amarinder singh]

Thanks Rony, that worked for me. 

[Amarnath Reddy Manam]

Hi Rony,
I was having the same issue and given iptables -F and service iptables save and it worked. When i gave to open port 8140 on master server in Iptables it did not worked, what exactly these command are doing to make it work?

iptables -F

service iptables save

[Vishal Biyani]

+1 to "iptables -F"

I was saving exactly same issue on a setup I created using Vagrant - one master and some slaves. The agents won't connect to master no matter what ping/ssh etc. said. Telnet didn't work of course in spite of all other right configurations. Thanks for making my day!

[Karel Lenc]

Just for a reference, what worked for me was to reconfigure the firewall:

firewall-cmd --zone=public --add-port=8140/tcp --permanent

firewall-cmd --reload

Source: http://www.unixmen.com/install-puppet-server-centos-7/

No need to flush all iptables rules...

[Swapnil Abnave]

@Karel Lenc

After hours and days of headbang.

That did worked.

Thanks!!!

[SAMBIT NAYAK]

Thanks for the answer . after configuring firewall services  i can able to use  puppet agent -t