I am interested in Foreman so I tried to install it failing miserably on a
fresh debian install. I tried it with a vagrant vm first and with a fully
connected kvm vm afterwards. I am following the quickstart guide from http://theforeman.org/manuals/1.6/quickstart_guide.html#Installation
foreman-installer finishes with some errors:
root@tester:~# grep ERROR /var/log/foreman-installer/foreman-installer.log
[ERROR 2014-10-18 13:34:08 main] Removing mount files: /etc/puppet/files
does not exist or is not a directory
[ INFO 2014-10-18 13:34:19 main] E, [2014-10-18T13:34:19.211850 #810] ERROR
– : 404 Resource Not Found
[ERROR 2014-10-18 13:34:19 main]
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[<FQDN>]: Could not
evaluate: Could not load data from https://tester.midras.de
[ERROR 2014-10-18 13:34:21 main] Repeating errors encountered during run:
[ERROR 2014-10-18 13:34:21 main] Removing mount files: /etc/puppet/files
does not exist or is not a directory
[ERROR 2014-10-18 13:34:21 main]
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[<FQDN>]: Could not
evaluate: Could not load data from https://tester.midras.de
I can log into foreman ui but there is no registered smart proxy. I cannot
add the smart proxy in the ui, I get the following error:
Unable to communicate with the proxy: ERF12-2530
[ProxyAPI::ProxyException]: Unable to detect features
([Errno::ECONNREFUSED]: Connection refused - connect(2)) for proxy
https://<FQDN>:8443/features
Please check the proxy is configured and running on the host.
running puppet agent --test as to the quickguide gives an error, too:
info: Retrieving plugin
err: /File[/var/lib/puppet/lib]: Failed to generate additional resources
using 'eval_generate: Connection refused - connect(2)
err: /File[/var/lib/puppet/lib]: Could not evaluate: Connection refused -
connect(2) Could not retrieve file metadata for puppet://<FQDN>/plugins:
Connection refused - connect(2)
err: Could not retrieve catalog from remote server: Connection refused -
connect(2)
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
err: Could not send report: Connection refused - connect(2)
So obviously I have a problem setting up the smart_proxy. But what's wrong?
Is there a know issue with debian 7.6 and Foreman?
You're probably haveing an entry for your FQDN with 127.0.1.1 in your
/etc/hosts. Change that IP to the one of e.g. your eth0 or delete that
entry and make sure, DNS resolving for your FQDN works forward and
reverse.
No idea about the Puppet issue, but maybe that's also resolved with
changing the name resolution.
Regards
···
On Sat, Oct 18, 2014 at 04:49:07AM -0700, Jochen Haeberle wrote:
> /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[]: Could not
> evaluate: Could not load data from https://tester.midras.de
no such entry in my /etc/hosts.
My reverse host lookup entry was missing/wrong. This is fixed by now but
the installer still throws the error and I can neither add the smartproxy
through web ui
Regards
Jochen
···
2014-10-18 22:35 GMT+02:00 Michael Moll :
On Sat, Oct 18, 2014 at 04:49:07AM -0700, Jochen Haeberle wrote:
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[]: Could
not
evaluate: Could not load data from https://tester.midras.de
You’re probably haveing an entry for your FQDN with 127.0.1.1 in your
/etc/hosts. Change that IP to the one of e.g. your eth0 or delete that
entry and make sure, DNS resolving for your FQDN works forward and
reverse.
No idea about the Puppet issue, but maybe that’s also resolved with
changing the name resolution.
I removed all packages relating to foreman after correcting the reverse dns
and rerun the installer with same result… no smart proxy.
Removing mount files: /etc/puppet/files does not exist or is not a
directory
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[tester.midras.de]:
Could not evaluate: Could not load data from https://tester.midras.de
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[tester.midras.de]:
Failed to call refresh: Could not load data from https://tester.midras.de
When trying to add the smart proxy using web ui the same:
Unable to save
Unable to communicate with the proxy: ERF12-2530
[ProxyAPI::ProxyException]: Unable to detect features
([Errno::ECONNREFUSED]: Connection refused - connect(2)) for proxy https://tester.midras.de:8443/features
Please check the proxy is configured and running on the host.
-Jochen
···
2014-10-19 11:53 GMT+02:00 Jochen Haeberle :
Hi Michael,
no such entry in my /etc/hosts.
My reverse host lookup entry was missing/wrong. This is fixed by now but
the installer still throws the error and I can neither add the smartproxy
through web ui
On Sat, Oct 18, 2014 at 04:49:07AM -0700, Jochen Haeberle wrote:
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[]: Could
not
evaluate: Could not load data from https://tester.midras.de
You’re probably haveing an entry for your FQDN with 127.0.1.1 in your
/etc/hosts. Change that IP to the one of e.g. your eth0 or delete that
entry and make sure, DNS resolving for your FQDN works forward and
reverse.
No idea about the Puppet issue, but maybe that’s also resolved with
changing the name resolution.
···
On Sun, Oct 19, 2014 at 01:58:38PM +0200, Jochen Haeberle wrote:
> When trying to add the smart proxy using web ui the same:
> Unable to save
> Unable to communicate with the proxy: ERF12-2530
> [ProxyAPI::ProxyException]: Unable to detect features
> ([Errno::ECONNREFUSED]: Connection refused - connect(2)) for proxy
> https://tester.midras.de:8443/features
> Please check the proxy is configured and running on the host.
Have a look into /var/log/foreman-proxy/proxy.log, maybe there’s some
hint why the proxy couldn’t start.
