All nodes gone unresponsive on console. We have split install configuration. But agent and master can able to communicate.

[nikhil dalshania]

Hi,

We have currently 4 nodes. As we use split installation So database, master and console are on different server. I am able to make communication between agent and master. But on console all 4 nodes are unresponsive.

When I type  puppet agent --test on master I am getting following output:

Warning: Unable to fetch my node definition, but the agent run will continue:

Warning: getaddrinfo: Name or service not known

Info: Retrieving pluginfacts

Error: /File[/home/ndalashania/.puppetlabs/opt/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': getaddrinfo: Name or service not known

Error: /File[/home/ndalashania/.puppetlabs/opt/puppet/cache/facts.d]: Could not evaluate: Could not retrieve file metadata for puppet:///pluginfacts: getaddrinfo: Name or service not known

Info: Retrieving plugin

Error: /File[/home/ndalashania/.puppetlabs/opt/puppet/cache/lib]: Failed to generate additional resources using 'eval_generate': getaddrinfo: Name or service not known

Error: /File[/home/ndalashania/.puppetlabs/opt/puppet/cache/lib]: Could not evaluate: Could not retrieve file metadata for puppet:///plugins: getaddrinfo: Name or service not known

Error: Could not retrieve catalog from remote server: getaddrinfo: Name or service not known

Warning: Not using cache on failed catalog

Error: Could not retrieve catalog; skipping run

Error: Could not send report: getaddrinfo: Name or service not known

Thanks in advance

Nick

[Christopher Wood]

This part is significant, it means that your puppet agent could not find the ip address of your puppetmaster server:

Warning: getaddrinfo: Name or service not known

Check that the server in your puppet.conf is resolvable through dns. If not, you can start looking at your dns issue. If so, check that you do not have an intermittent dns issue (repeat the test a number of times). Once dns is fixed, try again.

(If you're using a hosts file entry, check that for typos.)

> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [1]puppet-users...@googlegroups.com.
> To view this discussion on the web visit
> [2]https://groups.google.com/d/msgid/puppet-users/051fa7cf-178a-43a6-a9da-ca9e39fb8dfe%40googlegroups.com.
> For more options, visit [3]https://groups.google.com/d/optout.
>
> References
>
> Visible links
> 1. mailto:puppet-users...@googlegroups.com
> 2. https://groups.google.com/d/msgid/puppet-users/051fa7cf-178a-43a6-a9da-ca9e39fb8dfe%40googlegroups.com?utm_medium=email&utm_source=footer
> 3. https://groups.google.com/d/optout

[nikhil dalshania]

So basically you want me to add ip and fqdn of all agents on puppet masters puppet.conf RIGHT?

>    1. mailto:puppet-users+unsub...@googlegroups.com

[Christopher Wood]

No, I mean you need to fix your DNS lookups. Puppet relies on correct DNS both to find the puppetmaster as well as checking that the puppetmaster is presenting the correct ssl cert.

> >    email to [1][1]puppet-users...@googlegroups.com.

> >    To view this discussion on the web visit
> >  

>  [2][2]https://groups.google.com/d/msgid/puppet-users/051fa7cf-178a-43a6-a9da-ca9e39fb8dfe%40googlegroups.com.
> >    For more options, visit [3][3]https://groups.google.com/d/optout.
> >
> > References
> >
> >    Visible links
> >    1. mailto:[4]puppet-users...@googlegroups.com
> >    2.
> [5]https://groups.google.com/d/msgid/puppet-users/051fa7cf-178a-43a6-a9da-ca9e39fb8dfe%40googlegroups.com?utm_medium=email&utm_source=footer
> >    3. [6]https://groups.google.com/d/optout

>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to [7]puppet-users...@googlegroups.com.

> To view this discussion on the web visit

> [8]https://groups.google.com/d/msgid/puppet-users/92f1b049-e8a8-41fb-82ad-104143fcce9c%40googlegroups.com.
> For more options, visit [9]https://groups.google.com/d/optout.
>
> References
>
> Visible links
> 1. javascript:
> 2. https://groups.google.com/d/msgid/puppet-users/051fa7cf-178a-43a6-a9da-ca9e39fb8dfe%40googlegroups.com
> 3. https://groups.google.com/d/optout
> 4. javascript:
> 5. https://groups.google.com/d/msgid/puppet-users/051fa7cf-178a-43a6-a9da-ca9e39fb8dfe%40googlegroups.com?utm_medium=email&utm_source=footer
> 6. https://groups.google.com/d/optout
> 7. mailto:puppet-users...@googlegroups.com
> 8. https://groups.google.com/d/msgid/puppet-users/92f1b049-e8a8-41fb-82ad-104143fcce9c%40googlegroups.com?utm_medium=email&utm_source=footer
> 9. https://groups.google.com/d/optout

[jcbollinger]

On Monday, November 16, 2015 at 12:44:57 PM UTC-6, Christopher Wood wrote:

No, I mean you need to fix your DNS lookups. Puppet relies on correct DNS both to find the puppetmaster as well as checking that the puppetmaster is presenting the correct ssl cert.

... and the error message you, Nikhil, reported indicates that essential early step to be failing on the affected nodes.  Verify that a resolvable name for the master is configured in the [agent] section of each node's puppet.conf, and as Christopher said, troubleshoot the name resolution configuration on those nodes for the configured server name.  For this purpose, each node needs to be able to resolve (only) the specified master's name.  The master does not need to be able to resolve nodes' names; it just needs to be willing to trust the SSL certs they present.

Additionally, the configured name for the master must be among the names configured into the certificate the master presents to the agents, but your runs are failing before reaching that check.


John

[nikhil dalshania]

Thanks for the help it resolved now.

[root@abscpptm01p ~]# puppet agent -t

Info: Retrieving pluginfacts

Info: Retrieving plugin

Info: Loading facts

Info: Caching catalog for abscpptm01p.svmintranet.com

Info: Applying configuration version '1447968906'

Notice: Applied catalog in 0.10 seconds

The thing is on console still it not updating. Apart from that everything works fine.

One more question can we able to use live management with puppet new version 4.3.0??

Thanks

Nikhil

--
You received this message because you are subscribed to a topic in the Google Groups "Puppet Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/puppet-users/uNLV06JtMRc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/cfd719bf-a70b-42fd-9121-389206c2e8cd%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.