Ask Your Question
0

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

asked 2014-05-23 05:08:37 -0500

fbarison gravatar image

"puppet agent -t" call in PE monolithic server outputs this:

[root@puppetmaster ~]# puppet agent -t
Warning: Unable to fetch my node definition, but the agent run will continue:
Warning: 403 "Forbidden"
Info: Retrieving plugin
Error: /File[/var/opt/lib/pe-puppet/lib]: Failed to generate additional resources using 'eval_generate': 403 "Forbidden"
Error: /File[/var/opt/lib/pe-puppet/lib]: Could not evaluate: 403 "Forbidden" Could not retrieve file metadata for puppet://puppetmaster.xxx.xxx/plugins: 403 "Forbidden"
Info: Loading facts in /opt/puppet/share/puppet/modules/firewall/lib/facter/iptables_persistent_version.rb
Info: Loading facts in /opt/puppet/share/puppet/modules/firewall/lib/facter/iptables_version.rb
Info: Loading facts in /opt/puppet/share/puppet/modules/firewall/lib/facter/ip6tables_version.rb
Info: Loading facts in /opt/puppet/share/puppet/modules/pe_staging/lib/facter/staging_http_get.rb
Info: Loading facts in /opt/puppet/share/puppet/modules/stdlib/lib/facter/root_home.rb
Info: Loading facts in /opt/puppet/share/puppet/modules/stdlib/lib/facter/facter_dot_d.rb
Info: Loading facts in /opt/puppet/share/puppet/modules/stdlib/lib/facter/pe_version.rb
Info: Loading facts in /opt/puppet/share/puppet/modules/stdlib/lib/facter/puppet_vardir.rb
Info: Loading facts in /opt/puppet/share/puppet/modules/pe_puppetdb/lib/facter/pe_puppetdb_server_status.rb
Warning: Could not load fact file /opt/puppet/share/puppet/modules/pe_puppetdb/lib/facter/pe_puppetdb_server_status.rb: cannot load such file -- puppet/util/pe_puppetdb_validator
Info: Loading facts in /opt/puppet/share/puppet/modules/pe_postgresql/lib/facter/pe_postgres_default_version.rb
Info: Loading facts in /opt/puppet/share/puppet/modules/postgresql/lib/facter/postgres_default_version.rb
Info: Loading facts in /opt/puppet/share/puppet/modules/puppet_enterprise/lib/facter/pe_build.rb
Info: Loading facts in /opt/puppet/share/puppet/modules/puppet_enterprise/lib/facter/windows.rb
Info: Loading facts in /opt/puppet/share/puppet/modules/concat/lib/facter/concat_basedir.rb
Info: Loading facts in /opt/puppet/share/puppet/modules/auth_conf/lib/facter/custom_auth_conf.rb
Error: Could not retrieve catalog from remote server: 403 "Forbidden"
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
Error: Could not send report: 403 "Forbidden"

puppet --version:

[root@puppetmaster ~]# puppet --version
3.4.3 (Puppet Enterprise 3.2.3)

I cannot troubleshoot this, even with --debug switch:

[root@puppetmaster ~]# puppet agent -t --debug
Debug: Using settings: adding file resource 'confdir': 'File[/etc/puppetlabs/puppet]{:path=>"/etc/puppetlabs/puppet", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist
Debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dsimport does not exist
Debug: Puppet::Type::User::ProviderLdap: true value when expecting false
Debug: Puppet::Type::User::ProviderPw: file pw does not exist
Debug: Puppet::Type::Group::ProviderDirectoryservice: file /usr/bin/dscl does not exist
Debug: Puppet::Type::Group::ProviderLdap: true value when expecting false
Debug: Puppet::Type::Group::ProviderPw: file pw does not exist
Debug: Using settings: adding file resource 'vardir': 'File[/var/opt/lib/pe-puppet]{:path=>"/var/opt/lib/pe-puppet", :owner=>"pe-puppet", :group=>"pe-puppet", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'logdir ...
(more)
edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

answered 2014-12-08 12:54:37 -0500

Mark Wunschel gravatar image

I was getting a similar error on a newly installed Puppet Agent Node. The Puppet Master had signed the certificate and the Agent was showing up in the Console, but it was not reporting. What I found was a discrepancy in the certname on the Puppet Master and the Puppet Agent.

The certificate was signed by the master as xxx.example.local, but the puppet.conf file on the agent had the certname as XXX.example.local and it was under the [agent] section. I removed the XXX.example.local from the [agent] section and added certname = xxx.example.local to the [main] section.

I ran puppet agent -t again. The error went away and the node started to report.

edit flag offensive delete link more

Comments

@fbarison did it turn out that the capitalization was the issue, where making them match fixes your problem? Tons of pageviews on this question, so it would be nice to be able to mark this as the correct answer, if it is!

fnaard gravatar imagefnaard ( 2015-01-02 13:28:34 -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

Stats

Asked: 2014-05-23 05:08:37 -0500

Seen: 22,270 times

Last updated: Dec 08 '14