On 05/05/17 09:57, James Denton wrote: > 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)* [..] > > Why is it sending the report to itself and not to the foreman master?
Check the value of :url in /etc/puppetlabs/puppet/foreman.yaml is correct. This is the configuration file for the report processor and ENC. > 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...) The underlying part of the message (RestCli...) is truncated, check /var/log/foreman/production.log for the whole message. It may indicate an unusual HTTP response from the smart proxy, in which case, check/reply with the smart proxy logs while performing the import again to find the cause. -- Dominic Cleal [email protected] -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
