Foreman-proxy fails to run an fresh install of foreman 1.7 on CentOS 6.6

Installed Foreman on 1.7 on CentOS 6.6. Get the following error. Changed
the domain name in the output below, but other than that, error message is
as presented.

[root@Foreman ~]# foreman-installer
Could not start Service[foreman-proxy]: Execution of '/sbin/service
foreman-proxy start' returned 1: Starting foreman-proxy: [FAILED]
/Stage[main]/Foreman_proxy::Service/Service[foreman-proxy]/ensure: change
from stopped to running failed: Could not start Service[foreman-proxy]:
Execution of '/sbin/service foreman-proxy start' returned 1: Starting
foreman-proxy: [FAILED]
Installing Done
[100%] […]
Something went wrong! Check the log for ERROR-level output

  • Foreman is running at https://Foreman.*.org
    Initial credentials are admin / ***
  • Foreman Proxy is running at https://Foreman.*.org:8443
  • Puppetmaster is running at port 8140
    The full log is at /var/log/foreman-installer/foreman-installer.log

The foreman-proxy definitely failed to start… and when I run puppet agent
test on foreman server:

Warning: Unable to fetch my node definition, but the agent run will
continue:
Warning: Error 400 on SERVER: Failed to find foreman..org via exec:
Execution of '/etc/puppet/node.rb foreman.dachshund-digital.org' returned 1:
Info: Retrieving pluginfacts
Info: Retrieving plugin
Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
Failed when searching for node foreman.
.org: Failed to find foreman..org
via exec: Execution of '/etc/puppet/node.rb foreman.
.org' returned 1:
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

DNS and IP for foreman server are correct:

nslookup foreman.dachshund-digital.org

Server: 192.168.1.9
Address: 192.168.1.9#53
Name: foreman.*.org
Address: 192.168.1.241

Foreman is up and running but not the proxy. Found a few issues that seem
close via the forum and google, but nothing that seemed a good parallel.
Any assistance welcome.

Please try running "service foreman-proxy start" and provide
/var/log/foreman-proxy/proxy.log.

Also try running "sudo -u foreman-proxy
/usr/share/foreman-proxy/bin/smart-proxy" - hopefully one of these will
report a usable error.

··· On 30/03/15 22:10, Schorschi Decker wrote: > Installed Foreman on 1.7 on CentOS 6.6. Get the following error. > Changed the domain name in the output below, but other than that, error > message is as presented. > > [root@Foreman ~]# foreman-installer > Could not start Service[foreman-proxy]: Execution of '/sbin/service > foreman-proxy start' returned 1: Starting foreman-proxy: [FAILED] > /Stage[main]/Foreman_proxy::Service/Service[foreman-proxy]/ensure: > change from stopped to running failed: Could not start > Service[foreman-proxy]: Execution of '/sbin/service foreman-proxy start' > returned 1: Starting foreman-proxy: [FAILED] > Installing > Done [100%] > [.......................................................] > Something went wrong! Check the log for ERROR-level output > * Foreman is running at https://Foreman.*.org > Initial credentials are admin / *** > * Foreman Proxy is running at https://Foreman.*.org:8443 > * Puppetmaster is running at port 8140 > The full log is at /var/log/foreman-installer/foreman-installer.log > > The foreman-proxy definitely failed to start...


Dominic Cleal
Red Hat Engineering