Ask Your Question
0

Error with Agents connecting to Master

asked 2016-03-30 05:39:51 -0500

bprudence gravatar image

Hello all,

Quite new to puppet. I had an issue of all puppet agents had a revoked certificate including the master itself. I decided to recreate the ssl directory on the master so the only cert now is the puppet server itself.

When I try and connect an agent I do the following:

rm -rf /var/lib/puppet/ssl

puppet agent -t

Then get the following: Info: Creating a new SSL key for bacula.grpdom.vwuk.corp Info: Caching certificate for ca Info: csrattributes file loading from /etc/puppet/csrattributes.yaml Info: Creating a new SSL certificate request for bacula.grpdom.vwuk.corp Info: Certificate Request fingerprint (SHA256): 21:FE:F9:ED:B0:64:A2:AB:08:D9:16:2B:15:F4:E6:79:29:15:AA:DF:56:83:9E:80:F9:C0:41:7D:5D:9C:A0:C3 Info: Caching certificate for bacula.grpdom.vwuk.corp Info: Caching certificaterevocationlist for ca Info: Caching certificate for ca Warning: Unable to fetch my node definition, but the agent run will continue: Warning: Error 400 on SERVER: Failed to find bacula.grpdom.vwuk.corp via exec: Execution of '/etc/puppet/node.rb bacula.grpdom.vwuk.corp' returned 1: Info: Retrieving plugin Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/puppetvardir.rb Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/roothome.rb Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/facterdotd.rb Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/peversion.rb Info: Loading facts in /etc/puppet/modules/puppi/lib/facter/lastrun.rb Info: Loading facts in /etc/puppet/modules/puppi/lib/facter/puppiprojects.rb Info: Loading facts in /etc/puppet/modules/puppi/lib/facter/windowscommonappdata.rb Info: Loading facts in /var/lib/puppet/lib/facter/puppetvardir.rb Info: Loading facts in /var/lib/puppet/lib/facter/roothome.rb Info: Loading facts in /var/lib/puppet/lib/facter/facterdotd.rb Info: Loading facts in /var/lib/puppet/lib/facter/peversion.rb Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed when searching for node bacula.grpdom.vwuk.corp: Failed to find bacula.grpdom.vwuk.corp via exec: Execution of '/etc/puppet/node.rb bacula.grpdom.vwuk.corp' returned 1: Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run

Any help is much appriciated.

Thanks

BP

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
1

answered 2016-03-30 11:14:21 -0500

Hello

Are you using foreman and puppet open source by any chance?

If you are then with foreman when an agent runs it gets it's list of classes and other bits by running the node.rb script on the puppet master which makes a call to foreman to pull all that back and it would appear that's the bit that's not working.

You can run that node.rb script manually like this: sudo -u puppet /etc/puppet/node.rb [the name of a node, eg agent.local]

Have a look at the foreman manual and search the page for node.rb and check that it's all set up properly. I believe it has to be executable and owned by the puppet user and the foreman service it calls also needs to be running and accessible with no firewalls or DNS issues in the way etc

http://theforeman.org/manuals/1.10/in...

edit flag offensive delete link more

Comments

We don't have `/etc/puppet/node.rb` here on the client. How can this be? Or is this file only present on the masters?

UnitedMarsupials gravatar imageUnitedMarsupials ( 2016-04-05 22:27:16 -0500 )edit

node.rb lives on the master. Sorry for the late reply. I couldn't log in after puppetlabs did all the rebranding.

Binky gravatar imageBinky ( 2016-04-14 04:47:27 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2016-03-30 05:39:51 -0500

Seen: 62 times

Last updated: Mar 30 '16