Hi

I have recently updated both our Foreman master and a seperate foreman 
proxy to version 1.14. I have noticed though that the proxy no longer sends 
reports to the master and gives the following error in messages:

*May  5 09:51:43 foremanproxy puppet-master[3950]: Report processor failed: 
Could not send report to Foreman at 
https://foremanproxy.test.dmz/api/config_reports: Connection refused - 
connect(2)*
May  5 09:51:43 foremanproxy puppet-master[3950]: 
["/usr/share/ruby/net/http.rb:878:in `initialize'", 
"/usr/share/ruby/net/http.rb:878:in `open'", 
"/usr/share/ruby/net/http.rb:878:in `block in connect'", 
"/usr/share/ruby/timeout.rb:52:in `timeout'", 
"/usr/share/ruby/net/http.rb:877:in `connect'", 
"/usr/share/ruby/net/http.rb:862:in `do_start'", 
"/usr/share/ruby/net/http.rb:851:in `start'", 
"/usr/share/ruby/net/http.rb:1373:in `request'", 
"/usr/share/ruby/vendor_ruby/puppet/reports/foreman.rb:65:in `process'", 
"/usr/share/ruby/vendor_ruby/puppet/indirector/report/processor.rb:37:in 
`block in process'", 
"/usr/share/ruby/vendor_ruby/puppet/indirector/report/processor.rb:53:in 
`block in processors'", 
"/usr/share/ruby/vendor_ruby/puppet/indirector/report/processor.rb:51:in 
`each'", 
"/usr/share/ruby/vendor_ruby/puppet/indirector/report/processor.rb:51:in 
`processors'", 
"/usr/share/ruby/vendor_ruby/puppet/indirector/report/processor.rb:30:in 
`process'", 
"/usr/share/ruby/vendor_ruby/puppet/indirector/report/processor.rb:14:in 
`save'", 
"/usr/share/ruby/vendor_ruby/puppet/indirector/indirection.rb:283:in 
`save'", "/usr/share/ruby/vendor_ruby/puppet/network/http/api/v1.rb:160:in 
`do_save'", 
"/usr/share/ruby/vendor_ruby/puppet/network/http/api/v1.rb:50:in `block in 
call'", "/usr/share/ruby/vendor_ruby/puppet/context.rb:64:in `override'", 
"/usr/share/ruby/vendor_ruby/puppet.rb:246:in `override'", 
"/usr/share/ruby/vendor_ruby/puppet/network/http/api/v1.rb:49:in `call'", 
"/usr/share/ruby/vendor_ruby/puppet/network/http/route.rb:82:in `block in 
process'", "/usr/share/ruby/vendor_ruby/puppet/network/http/route.rb:81:in 
`each'", "/usr/share/ruby/vendor_ruby/puppet/network/http/route.rb:81:in 
`process'", 
"/usr/share/ruby/vendor_ruby/puppet/network/http/handler.rb:63:in `block in 
process'", 
"/usr/share/ruby/vendor_ruby/puppet/util/profiler/around_profiler.rb:58:in 
`profile'", "/usr/share/ruby/vendor_ruby/puppet/util/profiler.rb:51:in 
`profile'", 
"/usr/share/ruby/vendor_ruby/puppet/network/http/handler.rb:61:in 
`process'", "/usr/share/ruby/vendor_ruby/puppet/network/http/rack.rb:21:in 
`call'", 
"/usr/share/gems/gems/passenger-4.0.18/lib/phusion_passenger/rack/thread_handler_extension.rb:77:in
 
`process_request'", 
"/usr/share/gems/gems/passenger-4.0.18/lib/phusion_passenger/request_handler/thread_handler.rb:140:in
 
`accept_and_process_next_request'", 
"/usr/share/gems/gems/passenger-4.0.18/lib/phusion_passenger/request_handler/thread_handler.rb:108:in
 
`main_loop'", 
"/usr/share/gems/gems/passenger-4.0.18/lib/phusion_passenger/request_handler.rb:441:in
 
`block (3 levels) in start_threads'"]

Why is it sending the report to itself and not to the foreman master? 

Also another slight issue - On the front end under  infrastructure --> 
smart proxies although all features for the seperate smart proxy are listed 
as ok however under puppet --> environments I received the following error:



*Failure: ERF50-5345 [Foreman::WrappedException]: Unable to connect 
([ProxyAPI::ProxyException]: ERF12-2749 [ProxyAPI::ProxyException]: Unable 
to get environments from Puppet ([RestCli...)*I have checked the 
permissions on the dirs under puppet/environments and they all seem to be 
ok. 

Any help would be appreciated!

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to