How do I get Puppet Master to run a manifest against a Puppet Agent node when there are different errors?
<p>I have set up a <code>puppet master and puppet agent server</code> in one network. I have signed the puppet agent's cert request from the puppet master server. I am trying to run a manifest from Puppet Master against the Puppet agent server, but it is failing. The <code>newManifest.p</code>p on both Puppet Master servers calls the Puppet Agent through its <em>FQDN</em>. The <code>/etc/hosts</code> file on both servers has the entries of the FQDN of both servers and their IP addresses. I can ping each server from the other. I can SSH from each server to the other.</p>

<p>All four of these servers in both networks have <code>CentOS 7</code> as the OS with open source <code>Puppet version 3.8.4</code>. The firewalls are turned off on all four machines. These ports are not blocked on any intermediate path: 22, 443, 8140, and 61610 on either network between the Puppet Master and Puppet Agent servers.</p>

<p>In network one, I expect manifests to compile. They never have.</p>

<p>I tried this with sshd_config` to use ports 22, 443, 8140, and 61610 on both the Puppet Master and Puppet agent. When I use this from the puppet master:</p>

<pre><code>puppet agent -t newManifest.pp --server='foobar.acme.com'
</code></pre>

<p>I get an error:</p>

<pre><code>Unable to fetch my node definition, but the agent will continue: Warning: Connection refused - connect(2).
</code></pre>

<p>I tried again with sshdconfig to not use any ports specifically. I recycled the sshdconfig services. I run the same command:</p>

<pre><code>puppet agent -t newManifest.pp --server='foobar.acme.com'
</code></pre>

<p>I get a different error:</p>

<pre><code>Unable to fetch my node definition, but the agent run will continue: connection refused - connect(2).
</code></pre>

<p>I then tried this command (with no explicit server designation):</p>

<pre><code>puppet agent -t newManifest.pp
</code></pre>

<p>This time, I get this error:</p>

<pre><code>Unable to fetch my node definition, but the agent will continue: Network is unreachable.
</code></pre>

<p>In network two, I expect manifests to work. They never have.</p>

<p>I tried this with sshd_config to use ports 22, 443, 8140, and 61610 on both the Puppet Master and Puppet agent. When I use this from the puppet master:</p>

<pre><code>puppet agent -t newManifest.pp --server='foobar.acme.com'
</code></pre>

<p>I get a different error:</p>

<pre><code>   Unable to fetch my node definition, but the agent run will continue: SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello A: unknown protocol.
</code></pre>

<p>I tried again with sshdconfig to not use any ports specifically. I recycled the sshdconfig services. I run the same command:</p>

<pre><code>puppet agent -t newManifest.pp --server='foobar.acme.com'
</code></pre>

<p>I get a different error:</p>

<pre><code> Unable to fetch my node definition, but the agent run will continue: connection refused - connect(2).
</code></pre>

<p>I then tried this command (with no explicit server designation):</p>

<pre><code> puppet agent -t newManifest.pp
</code></pre>

<p>This time, I get this error:</p>

<pre><code> Unable to fetch my node definition, but the agent will continue: No route to host - connect(2).
</code></pre>

<p>The errors between network one and two are different except when sshd_config is not using any specific ports and the command to compile the manifest explicitly sets the FQDN. Why is this? What is wrong? I have tried to set up Puppet twice just to fix the first instance. I cannot completely reproduce the specific problems in the first network.</p>

<p>How do I get the Puppet Master server to compile a manifest? The puppet agents have signed certificates. I don't understand why the compilation of the manifests always fails.</p>