Yes, I installed that way because the puppet server including postgresql are installed on the same server.
You mentioned apache config and after checking the certs listed were the same as in foreman.yaml I restarted the service just in case and now the error is gone, this is good!!
Now the issue is that I do not see the report being sent to foreman but only to puppetdb and I do not see the host
listed on Foreman dashboard
store_report’ command for testinstance_i-0e7c5e1b886615560.domain.lan submitted to PuppetDB
This is how I configured puppet.conf ( server side )
I, [2018-01-07T15:06:39.836762 ] INFO -- : Started puppet class cache initialization
I, [2018-01-07T15:06:39.837494 ] INFO -- : Successfully initialized 'puppet_proxy_puppet_api'
I, [2018-01-07T15:06:39.837815 ] INFO -- : Successfully initialized 'puppet'
I, [2018-01-07T15:06:39.837921 ] INFO -- : Successfully initialized 'logs'
I, [2018-01-07T15:06:39.860489 ] INFO -- : WEBrick 1.3.1
I, [2018-01-07T15:06:39.860596 ] INFO -- : ruby 2.0.0 (2015-12-16) [x86_64-linux]
W, [2018-01-07T15:06:39.861756 ] WARN -- : TCPServer Error: Address already in use - bind(2)
I, [2018-01-07T15:06:39.862730 ] INFO -- :
I, [2018-01-07T15:06:39.865016 ] INFO -- : WEBrick::HTTPServer#start: pid=23530 port=8443
E, [2018-01-07T15:06:39.999486 ] ERROR -- : Error while retrieving puppet classes for 'production' environment
W, [2018-01-07T15:06:40.000206 ] WARN -- : Failed to initialize puppet class cache, deferring initialization. Is puppetserver running?
And still seeing:
[W] No smart proxy server found on ["puppetserver.domain.lan", "puppet", "puppetserver.domain.lan", "puppet.domain.com", "puppetserver-f799dfc2a5c4c927.elb.us-east-1.amazonaws.com"] and is not in trusted_puppetmaster_hosts
Sounds like you haven’t added the proxy to the Foreman UI - do you have a proxy under Smart Proxies, with a URL that matches the certificate, and has the Puppet feature enabled?
I, [2018-01-07T15:33:14.188370 ] INFO -- : WEBrick::HTTPServer#start: pid=30073 port=8443
E, [2018-01-07T15:33:14.305108 ] ERROR -- : Error while retrieving puppet classes for 'production' environment
W, [2018-01-07T15:33:14.305904 ] WARN -- : Failed to initialize puppet class cache, deferring initialization. Is puppetserver running?
What I do not see is a configuration file under /etc/http/conf.d/ for the proxy itself, there should be something ? is that created automatically when creating the proxy from the foreman UI?
Any idea what’s could be wrong?
Thanks for your time and support, really appreciated.
Timeout suggests that either the hostname is wrong, the DNS can’t resolve it, or there’s a firewall in the way.
Whilst this is only a warning, it’s probably worth checking. The proxy doesn’t run in Apache - you’ll find its config in /etc/foreman-proxy - can you post the contents of settings.d/puppet.yml?
2018-01-07 16:32:46 9cc17610 [app] [I] Failed to save: Unable to communicate with the proxy: ERF12-2530 [ProxyAPI::ProxyException]: Unable to detect features ([RestClient::RequestTimeout]: Request Timeout) for proxy https://puppetserver.domain.lan/features, Please check the proxy is configured and running on the host.