Running the latest version of Puppet on the Windows client and Puppet master is version 4.5.3. The agent used to work correctly but no longer shows any information on Foreman while other machines work correctly.
The machine reports the following error.
Unable to fetch my node definition, but the agent run will continue:
Error 500 on SERVER: {"message":"Server Error: Failed to find host via exec: Execution of '/etc/puppetlabs/puppet/node.rb host' returned 1: ","issue_kind":"RUNTIME_ERROR","stacktrace":["file:/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/puppetserver-lib/puppet/server/execution.rb:44:in `execute'","file:/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/puppetserver-lib/puppet/server/execution.rb:14:in `initialize_execution_stub'","org/jruby/RubyProc.java:281:in `call'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/execution.rb:194:in `execute'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/node/exec.rb:33:in `execute'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/exec.rb:19:in `find'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/node/exec.rb:17:in `find'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:194:in `find'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:121:in `do_find'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:48:in `call'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:in `override'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:240:in `override'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:47:in `call'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:82:in `process'","org/jruby/RubyArray.java:1613:in `each'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:81:in `process'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:87:in `process'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:87:in `process'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/handler.rb:60:in `process'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler/around_profiler.rb:58:in `profile'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler.rb:51:in `profile'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/handler.rb:58:in `process'","file:/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/puppetserver-lib/puppet/server/master.rb:42:in `handleRequest'","Puppet$$Server$$Master_920325718.gen:13:in `handleRequest'","request_handler_core.clj:273:in `invoke'","jruby_request.clj:46:in `invoke'","jruby_request.clj:31:in `invoke'","request_handler_service.clj:34:in `handle_request'","request_handler.clj:3:in `invoke'","request_handler.clj:3:in `invoke'","core.clj:2515:in `invoke'","master_core.clj:411:in `invoke'","ring.clj:21:in `invoke'","ring.clj:12:in `invoke'","comidi.clj:249:in `invoke'","ring_middleware.clj:284:in `invoke'","core.clj:168:in `invoke'","core.clj:211:in `invoke'","core.clj:45:in `invoke'","core.clj:343:in `invoke'","core.clj:51:in `invoke'","ringutils.clj:83:in `invoke'","legacy_routes_core.clj:114:in `invoke'","legacy_routes_core.clj:94:in `invoke'","legacy_routes_core.clj:184:in `invoke'","legacy_routes_core.clj:130:in `invoke'","ring.clj:21:in `invoke'","ring.clj:12:in `invoke'","comidi.clj:249:in `invoke'","jetty9_core.clj:424:in `invoke'","normalized_uri_helpers.clj:80:in `invoke'"]}
Running /etc/puppetlabs/puppet/node.rb host yields the following message.
No such file or directory - /opt/puppetlabs/puppet/cache/yaml/facts/host.yaml
Node.rb produces the correct response for the other hosts. All the machines have the same puppet.conf.
We tried removing all files related to Puppet and reinstalling, as well as cleaning the cert on the master and the client and obtaining a new one. A new cert is obtained, but the issue is not resolved. The environment has a default node defined as well as a node defined for the host itself.
Performing the change outlined [here](https://ask.puppet.com/question/28990/error-500-on-server-server-error-failed-when-searching-for-node-host/) caused the error to spread to our CentOS/RedHat and MacOS machines as well.
Any ideas on what could be causing this issue?
↧