RHEL7 installation

Duncan_Innes · June 26, 2014, 9:13pm

HI folks,

Am going to have a poke around with Foreman nightlies on RHEL7 - unless
there are any obvious gotchas?

Wondering if the install method is the same as for RHEL6 (with RHSCL1 etc),
or if there are any differences to watch out for.

Cheers

D

Dominic_Cleal · June 26, 2014, 9:18pm

> HI folks,
>
> Am going to have a poke around with Foreman nightlies on RHEL7 - unless
> there are any obvious gotchas?

There are a couple in the installer, which is why I've held off
announcing it so far.

https://github.com/theforeman/puppet-foreman/pull/195 is a patch for
/usr/share/foreman-installer/modules/foreman/

/usr/share/foreman-installer/modules/postgresql needs replacing with the
latest from https://github.com/puppetlabs/puppetlabs-postgresql/

There are also two SELinux issues, but it should work fine in permissive
for now (linked to issue #4447).

> Wondering if the install method is the same as for RHEL6 (with RHSCL1
> etc), or if there are any differences to watch out for.

Yep, exactly the same.

Looking forward to your feedback, thanks!

···

On 26/06/14 22:13, Duncan Innes wrote:

–
Dominic Cleal
Red Hat Engineering

Duncan_Innes · July 1, 2014, 7:28am

Guys,

All was going well until I tried to install a Smart Proxy for controlling
my libvirt. When starting up the service I get:

[root@laptop.local ~]# systemctl enable foreman-proxy.service
ln -s '/usr/lib/systemd/system/foreman-proxy.service'
'/etc/systemd/system/multi-user.target.wants/foreman-proxy.service'
[root@laptop.local ~]# systemctl start foreman-proxy.service
Job for foreman-proxy.service failed. See 'systemctl status
foreman-proxy.service' and 'journalctl -xn' for details.
[root@laptop.local ~]# systemctl status foreman-proxy.service
foreman-proxy.service - Foreman Proxy
Loaded: loaded (/usr/lib/systemd/system/foreman-proxy.service; enabled)
Active: failed (Result: exit-code) since Tue 2014-07-01 08:20:05 BST;
8s ago
Process: 31648 ExecStart=/usr/share/foreman-proxy/bin/smart-proxy (code=exited,
status=1/FAILURE)

Jul 01 08:20:05 laptop.local smart-proxy[31648]: from
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:53:in require' Jul 01 08:20:05 laptop.local smart-proxy[31648]: from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:53:inrequire'
Jul 01 08:20:05 laptop.local smart-proxy[31648]: from
/usr/share/foreman-proxy/lib/smart_proxy.rb:44:in <module:Proxy>' Jul 01 08:20:05 laptop.local smart-proxy[31648]: from /usr/share/foreman-proxy/lib/smart_proxy.rb:26:in<top (required)>'
Jul 01 08:20:05 laptop.local smart-proxy[31648]: from
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:53:in require' Jul 01 08:20:05 laptop.local smart-proxy[31648]: from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:53:inrequire'
Jul 01 08:20:05 laptop.local smart-proxy[31648]: from
/usr/share/foreman-proxy/bin/smart-proxy:5:in `<main>'
Jul 01 08:20:05 laptop.local systemd[1]: foreman-proxy.service: control
process exited, code=exited status=1
Jul 01 08:20:05 laptop.local systemd[1]: Failed to start Foreman Proxy.
Jul 01 08:20:05 laptop.local systemd[1]: Unit foreman-proxy.service
entered failed state.
[root@laptop.local ~]#

I'll raise a ticket if necessary, but just wondered if this is something
else I've just got wrong rather than a ticket.

I had a look for similar issues and there don't appear to be any at this
point. Just thought I'd post here before raising a ticket.

journalctl doesn't provide any extra information & all I get in
/var/log/foreman-proxy/proxy.log is a line saying the logfile was created
by logger.rb.

Is this RHEL7 related, or Duncan related?

Cheers

D

Duncan_Innes · June 27, 2014, 9:48pm

Think I did things right (couple beers and a bottle of wine blurring the
lines a tad)

Getting the error (twice):

[ERROR 2014-06-27 22:43:16 main] No preferred version defined or
automatically detected. at
/usr/share/foreman-installer/modules/postgresql/manifests/params.pp:173 on
node foreman.rhel7.local

in /var/log/foreman-installer/foreman-installer.log

when running foreman-installer

Apologies if I've obviously screwed this up myself. Willing to batter on
and help get to the bottom of this, but not sure how.

Cheers

D

Dominic_Cleal · July 1, 2014, 7:33am

Does the journal store the top of that stack trace reported in
systemctl? The first few lines are most important, as they'll list
which file it's trying to load.

We had a big change to the proxy packaging recently, I might have
forgotten to update something on the RHEL7 side.

···

On 01/07/14 08:28, Duncan Innes wrote: > Guys, > > All was going well until I tried to install a Smart Proxy for > controlling my libvirt. When starting up the service I get: > > [root@laptop.local ~]# systemctl enable foreman-proxy.service > ln -s '/usr/lib/systemd/system/foreman-proxy.service' > '/etc/systemd/system/multi-user.target.wants/foreman-proxy.service' > [root@laptop.local ~]# systemctl start foreman-proxy.service > Job for foreman-proxy.service failed. See 'systemctl status > foreman-proxy.service' and 'journalctl -xn' for details. > [root@laptop.local ~]# systemctl status foreman-proxy.service > foreman-proxy.service - Foreman Proxy > Loaded: loaded (/usr/lib/systemd/system/foreman-proxy.service; enabled) > Active: *failed* (Result: exit-code) since Tue 2014-07-01 08:20:05 > BST; 8s ago > Process: 31648 ExecStart=/usr/share/foreman-proxy/bin/smart-proxy > *(code=exited, status=1/FAILURE)* > > Jul 01 08:20:05 laptop.local smart-proxy[31648]: from > /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:53:in `require' > Jul 01 08:20:05 laptop.local smart-proxy[31648]: from > /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:53:in `require' > Jul 01 08:20:05 laptop.local smart-proxy[31648]: from > /usr/share/foreman-proxy/lib/smart_proxy.rb:44:in `' > Jul 01 08:20:05 laptop.local smart-proxy[31648]: from > /usr/share/foreman-proxy/lib/smart_proxy.rb:26:in `' > Jul 01 08:20:05 laptop.local smart-proxy[31648]: from > /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:53:in `require' > Jul 01 08:20:05 laptop.local smart-proxy[31648]: from > /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:53:in `require' > Jul 01 08:20:05 laptop.local smart-proxy[31648]: from > /usr/share/foreman-proxy/bin/smart-proxy:5:in `' > Jul 01 08:20:05 laptop.local systemd[1]: *foreman-proxy.service: control > process exited, code=exited status=1* > Jul 01 08:20:05 laptop.local systemd[1]: *Failed to start Foreman Proxy.* > Jul 01 08:20:05 laptop.local systemd[1]: *Unit foreman-proxy.service > entered failed state.* > [root@laptop.local ~]# > > I'll raise a ticket if necessary, but just wondered if this is something > else I've just got wrong rather than a ticket. > > I had a look for similar issues and there don't appear to be any at this > point. Just thought I'd post here before raising a ticket. > > journalctl doesn't provide any extra information & all I get in > /var/log/foreman-proxy/proxy.log is a line saying the logfile was > created by logger.rb.

–
Dominic Cleal
Red Hat Engineering

ekohl · June 28, 2014, 7:17pm

Are you sure you updated the puppet postgresql module to the latest git
version?

···

On Fri, Jun 27, 2014 at 02:48:13PM -0700, Duncan Innes wrote: > Think I did things right (couple beers and a bottle of wine blurring the > lines a tad) > > Getting the error (twice): > > [ERROR 2014-06-27 22:43:16 main] No preferred version defined or > automatically detected. at > /usr/share/foreman-installer/modules/postgresql/manifests/params.pp:173 on > node foreman.rhel7.local > > in /var/log/foreman-installer/foreman-installer.log > > when running foreman-installer > > Apologies if I've obviously screwed this up myself. Willing to batter on > and help get to the bottom of this, but not sure how.

Duncan_Innes · July 1, 2014, 8:05am

Sorry - I had seen this, but thought it was in the clip I pasted earlier.

Jul 01 08:20:05 laptop.local systemd[1]: Starting Foreman Proxy…
Jul 01 08:20:05 laptop.local smart-proxy[31648]:
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:53:in require': cannot load such file -- puppet (LoadError) Jul 01 08:20:05 laptop.local smart-proxy[31648]: from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:53:inrequire'
Jul 01 08:20:05 laptop.local smart-proxy[31648]: from
/usr/share/foreman-proxy/modules/puppetca/puppetca.rb:8:in
<module:PuppetCa>' Jul 01 08:20:05 laptop.local smart-proxy[31648]: from /usr/share/foreman-proxy/modules/puppetca/puppetca.rb:4:in<top
(required)>'
Jul 01 08:20:05 laptop.local smart-proxy[31648]: from
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:53:in require' Jul 01 08:20:05 laptop.local smart-proxy[31648]: from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:53:inrequire'
Jul 01 08:20:05 laptop.local smart-proxy[31648]: from
/usr/share/foreman-proxy/lib/smart_proxy.rb:44:in <module:Proxy>' Jul 01 08:20:05 laptop.local smart-proxy[31648]: from /usr/share/foreman-proxy/lib/smart_proxy.rb:26:in<top (required)>'
Jul 01 08:20:05 laptop.local smart-proxy[31648]: from
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:53:in require' Jul 01 08:20:05 laptop.local smart-proxy[31648]: from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:53:inrequire'
Jul 01 08:20:05 laptop.local smart-proxy[31648]: from
/usr/share/foreman-proxy/bin/smart-proxy:5:in `<main>'
Jul 01 08:20:05 laptop.local systemd[1]: foreman-proxy.service: control
process exited, code=exited status=1
Jul 01 08:20:05 laptop.local systemd[1]: Failed to start Foreman Proxy.
Jul 01 08:20:05 laptop.local systemd[1]: Unit foreman-proxy.service
entered failed state.

Cheers

D

···

On Tuesday, 1 July 2014 08:34:00 UTC+1, Dominic Cleal wrote: > > > Does the journal store the top of that stack trace reported in > systemctl? The first few lines are most important, as they'll list > which file it's trying to load. > > We had a big change to the proxy packaging recently, I might have > forgotten to update something on the RHEL7 side. > > -- > Dominic Cleal > Red Hat Engineering >

Dominic_Cleal · July 1, 2014, 8:18am

Ah okay, so our foreman-proxy package doesn't depend on Puppet as it's a
soft dependency. I think we'll change this in the future and use
sub-packages so we can use hard dependencies as the 1.6 proxy is modular.

You can either disable the Puppet and Puppet CA modules under
/etc/foreman-proxy/settings.d/, or install Puppet.

···

On 01/07/14 09:05, Duncan Innes wrote: > Sorry - I had seen this, but thought it was in the clip I pasted earlier. > > Jul 01 08:20:05 laptop.local systemd[1]: Starting Foreman Proxy... > Jul 01 08:20:05 laptop.local smart-proxy[31648]: > /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:53:in `require': > cannot load such file -- puppet (LoadError)

–
Dominic Cleal
Red Hat Engineering

Duncan_Innes · June 30, 2014, 8:03am

In the cold light of day, I made a near inexplicable series of errors.
Will revisit this morning and update this topic.

D

Duncan_Innes · June 30, 2014, 8:53am

OK - managed to checkout from github properly this time.

Have tried both master and 3.4.x branches so far and get the following
error:

[root@foreman modules]# foreman-installer
Invalid parameter port on Postgresql_psql[Check for existence of db
'foreman'] at
/usr/share/foreman-installer/modules/postgresql/manifests/server/database.pp:58
on node foreman.rhel7.local
Invalid parameter port on Postgresql_psql[Check for existence of db
'foreman'] at
/usr/share/foreman-installer/modules/postgresql/manifests/server/database.pp:58
on node foreman.rhel7.local
Preparing installation Done
Something went wrong! Check the log for ERROR-level output
The full log is at /var/log/foreman-installer/foreman-installer.log
[root@foreman modules]#

I am sober this time.

D

Duncan_Innes · July 1, 2014, 8:48am

OK - installed Puppet (it'll be on all clients anyway come production
rollout) and checked the statuses in puppet.yml and puppetca.yml. They
look disabled already to me, but now Puppet is installed, I get a longer
pause, still a failure, but less information:

[root@laptop.local ~]# cat /etc/foreman-proxy/settings.d/puppet.yml

···

--- :enabled: false # valid providers: # puppetrun (for puppetrun/kick, deprecated in Puppet 3) # mcollective (uses mco puppet) # puppetssh (run puppet over ssh) # salt (uses salt puppet.run) # customrun (calls a custom command with args) #:puppet_provider: puppetrun

Customrun command details

Set :customrun_cmd to the full path of the script you want to run,

instead of /bin/false
:customrun_cmd: /bin/false

Set :customrun_args to any args you want to pass to your custom script.

The hostname of the

system to run against will be appended after the custom commands.

:customrun_args: -ay -f -s

:puppet_conf: /etc/puppet/puppet.conf

whether to use sudo before the ssh command

:puppetssh_sudo: false

the command which will be sent to the host

:puppetssh_command: /usr/bin/puppet agent --onetime --no-usecacheonfailure

With which user should the proxy connect

#:puppetssh_user: root
#:puppetssh_keyfile: /etc/foreman-proxy/id_rsa

Which user to invoke sudo as to run puppet commands

#:puppet_user: root
[root@laptop.local ~]# cat /etc/foreman-proxy/settings.d/puppetca.yml

:enabled: false
#:ssldir: /var/lib/puppet/ssl
#:puppetdir: /etc/puppet
#:puppetca_use_sudo: true
#:sudo_command: /usr/bin/sudo
[root@laptop.local ~]# rpm -qa | grep puppet
puppet-3.6.2-1.el7.noarch
[root@laptop.local ~]# systemctl start foreman-proxy.service
Job for foreman-proxy.service failed. See ‘systemctl status
foreman-proxy.service’ and ‘journalctl -xn’ for details.
[root@laptop.local ~]# systemctl status foreman-proxy.service
foreman-proxy.service - Foreman Proxy
Loaded: loaded (/usr/lib/systemd/system/foreman-proxy.service; enabled)
Active: failed (Result: exit-code) since Tue 2014-07-01 09:35:08 BST;
21s ago
Process: 6068 ExecStart=/usr/share/foreman-proxy/bin/smart-proxy (code=exited,
status=1/FAILURE)

Jul 01 09:35:08 laptop.local systemd[1]: foreman-proxy.service: control
process exited, code=exited status=1
Jul 01 09:35:08 laptop.local systemd[1]: Failed to start Foreman Proxy.
Jul 01 09:35:08 laptop.local systemd[1]: Unit foreman-proxy.service
entered failed state.
[root@laptop.local ~]# journalctl -xn
– Logs begin at Mon 2014-06-30 20:13:02 BST, end at Tue 2014-07-01
09:35:21 BST. –
Jul 01 09:33:33 laptop.local systemd[1]: foreman-proxy.service: control
process exited, code=exited status=1
Jul 01 09:33:33 laptop.local systemd[1]: Failed to start Foreman Proxy.
– Subject: Unit foreman-proxy.service has failed
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

– Unit foreman-proxy.service has failed.

– The result is failed.
Jul 01 09:33:33 laptop.local systemd[1]: Unit foreman-proxy.service
entered failed state.
Jul 01 09:34:57 laptop.local dnsmasq-dhcp[3064]: DHCPREQUEST(virbr0)
192.168.122.129 52:54:00:00:00:02
Jul 01 09:34:57 laptop.local dnsmasq-dhcp[3064]: DHCPACK(virbr0)
192.168.122.129 52:54:00:00:00:02 foreman
Jul 01 09:35:07 laptop.local systemd[1]: Starting Foreman Proxy…
– Subject: Unit foreman-proxy.service has begun with start-up
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

– Unit foreman-proxy.service has begun starting up.
Jul 01 09:35:08 laptop.local systemd[1]: foreman-proxy.service: control
process exited, code=exited status=1
Jul 01 09:35:08 laptop.local systemd[1]: Failed to start Foreman Proxy.
– Subject: Unit foreman-proxy.service has failed
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

– Unit foreman-proxy.service has failed.

– The result is failed.
Jul 01 09:35:08 laptop.local systemd[1]: Unit foreman-proxy.service
entered failed state.
Jul 01 09:35:21 laptop.local puppet-agent[5842]: Could not request
certificate: getaddrinfo: Name or service not known
[root@laptop.local ~]# cat /var/log/foreman-proxy/proxy.log

Logfile created on 2014-06-30 21:05:04 +0100 by logger.rb/41954

E, [2014-07-01T09:30:17.043551 #5377] ERROR – : Both http and https are
disabled, unable to start.
E, [2014-07-01T09:33:33.282286 #5900] ERROR – : Both http and https are
disabled, unable to start.
E, [2014-07-01T09:35:08.776432 #6068] ERROR – : Both http and https are
disabled, unable to start.
[root@laptop.local ~]#
systemctl status httpd.service
httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled)
Active: active (running) since Mon 2014-06-30 20:13:31 BST; 13h ago
Main PID: 1752 (httpd)
Status: "Total requests: 0; Current requests/sec: 0; Current traffic:
0 B/sec"
CGroup: /system.slice/httpd.service
├─1752 /usr/sbin/httpd -DFOREGROUND
├─2736 /usr/sbin/httpd -DFOREGROUND
├─2737 /usr/sbin/httpd -DFOREGROUND
├─2738 /usr/sbin/httpd -DFOREGROUND
├─2739 /usr/sbin/httpd -DFOREGROUND
└─2740 /usr/sbin/httpd -DFOREGROUND

Jun 30 20:13:31 laptop.local httpd[1752]: AH00557: httpd:
apr_sockaddr_info_get() failed for laptop.local
Jun 30 20:13:31 laptop.local httpd[1752]: AH00558: httpd: Could not
reliably determine the server’s fully qualified domain name, using
127.0.0.1. Set the 'Serv…his message
Jun 30 20:13:31 laptop.local systemd[1]: Started The Apache HTTP Server.
Hint: Some lines were ellipsized, use -l to show in full.
[root@laptop.local ~]#

Is this a failure to recognise that httpd is running?

Cheers

D

On Tuesday, 1 July 2014 09:18:10 UTC+1, Dominic Cleal wrote:

On 01/07/14 09:05, Duncan Innes wrote:

Sorry - I had seen this, but thought it was in the clip I pasted
earlier.

Jul 01 08:20:05 laptop.local systemd[1]: Starting Foreman Proxy…
Jul 01 08:20:05 laptop.local smart-proxy[31648]:
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:53:in `require’:
cannot load such file – puppet (LoadError)

Ah okay, so our foreman-proxy package doesn’t depend on Puppet as it’s a
soft dependency. I think we’ll change this in the future and use
sub-packages so we can use hard dependencies as the 1.6 proxy is modular.

You can either disable the Puppet and Puppet CA modules under
/etc/foreman-proxy/settings.d/, or install Puppet.

–
Dominic Cleal
Red Hat Engineering

Dominic_Cleal · July 1, 2014, 8:52am

Here's the issue:

[root@laptop.local ~]# cat /var/log/foreman-proxy/proxy.log

Logfile created on 2014-06-30 21:05:04 +0100 by logger.rb/41954

E, [2014-07-01T09:30:17.043551 #5377] ERROR – : Both http and https are
disabled, unable to start.

You need to uncomment either http_port or https_port (+ ssl*) in
/etc/foreman-proxy/settings.yml to enable HTTP or HTTPS.

···

-- Dominic Cleal Red Hat Engineering

On 01/07/14 09:48, Duncan Innes wrote:

OK - installed Puppet (it’ll be on all clients anyway come production
rollout) and checked the statuses in puppet.yml and puppetca.yml. They
look disabled already to me, but now Puppet is installed, I get a longer
pause, still a failure, but less information:

[root@laptop.local ~]# cat /etc/foreman-proxy/settings.d/puppet.yml

:enabled: false

valid providers:

puppetrun (for puppetrun/kick, deprecated in Puppet 3)

mcollective (uses mco puppet)

puppetssh (run puppet over ssh)

salt (uses salt puppet.run)

customrun (calls a custom command with args)

#:puppet_provider: puppetrun

Customrun command details

Set :customrun_cmd to the full path of the script you want to run,

instead of /bin/false
:customrun_cmd: /bin/false

Set :customrun_args to any args you want to pass to your custom

script. The hostname of the

system to run against will be appended after the custom commands.

:customrun_args: -ay -f -s

:puppet_conf: /etc/puppet/puppet.conf

whether to use sudo before the ssh command

:puppetssh_sudo: false

the command which will be sent to the host

:puppetssh_command: /usr/bin/puppet agent --onetime --no-usecacheonfailure

With which user should the proxy connect

#:puppetssh_user: root
#:puppetssh_keyfile: /etc/foreman-proxy/id_rsa

Which user to invoke sudo as to run puppet commands

#:puppet_user: root
[root@laptop.local ~]# cat /etc/foreman-proxy/settings.d/puppetca.yml

:enabled: false
#:ssldir: /var/lib/puppet/ssl
#:puppetdir: /etc/puppet
#:puppetca_use_sudo: true
#:sudo_command: /usr/bin/sudo
[root@laptop.local ~]# rpm -qa | grep puppet
puppet-3.6.2-1.el7.noarch
[root@laptop.local ~]# systemctl start foreman-proxy.service
Job for foreman-proxy.service failed. See ‘systemctl status
foreman-proxy.service’ and ‘journalctl -xn’ for details.
[root@laptop.local ~]# systemctl status foreman-proxy.service
foreman-proxy.service - Foreman Proxy
Loaded: loaded (/usr/lib/systemd/system/foreman-proxy.service; enabled)
Active: failed (Result: exit-code) since Tue 2014-07-01 09:35:08
BST; 21s ago
Process: 6068 ExecStart=/usr/share/foreman-proxy/bin/smart-proxy
(code=exited, status=1/FAILURE)

Jul 01 09:35:08 laptop.local systemd[1]: foreman-proxy.service: control
process exited, code=exited status=1
Jul 01 09:35:08 laptop.local systemd[1]: Failed to start Foreman Proxy.
Jul 01 09:35:08 laptop.local systemd[1]: Unit foreman-proxy.service
entered failed state.
[root@laptop.local ~]# journalctl -xn
– Logs begin at Mon 2014-06-30 20:13:02 BST, end at Tue 2014-07-01
09:35:21 BST. –
Jul 01 09:33:33 laptop.local systemd[1]: foreman-proxy.service: control
process exited, code=exited status=1
Jul 01 09:33:33 laptop.local systemd[1]: Failed to start Foreman Proxy.
– Subject: Unit foreman-proxy.service has failed
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

– Unit foreman-proxy.service has failed.

– The result is failed.
Jul 01 09:33:33 laptop.local systemd[1]: Unit foreman-proxy.service
entered failed state.
Jul 01 09:34:57 laptop.local dnsmasq-dhcp[3064]: DHCPREQUEST(virbr0)
192.168.122.129 52:54:00:00:00:02
Jul 01 09:34:57 laptop.local dnsmasq-dhcp[3064]: DHCPACK(virbr0)
192.168.122.129 52:54:00:00:00:02 foreman
Jul 01 09:35:07 laptop.local systemd[1]: Starting Foreman Proxy…
– Subject: Unit foreman-proxy.service has begun with start-up
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

– Unit foreman-proxy.service has begun starting up.
Jul 01 09:35:08 laptop.local systemd[1]: foreman-proxy.service: control
process exited, code=exited status=1
Jul 01 09:35:08 laptop.local systemd[1]: Failed to start Foreman Proxy.
– Subject: Unit foreman-proxy.service has failed
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

– Unit foreman-proxy.service has failed.

– The result is failed.
Jul 01 09:35:08 laptop.local systemd[1]: Unit foreman-proxy.service
entered failed state.
Jul 01 09:35:21 laptop.local puppet-agent[5842]: Could not request
certificate: getaddrinfo: Name or service not known
[root@laptop.local ~]# cat /var/log/foreman-proxy/proxy.log

Logfile created on 2014-06-30 21:05:04 +0100 by logger.rb/41954

E, [2014-07-01T09:30:17.043551 #5377] ERROR – : Both http and https are
disabled, unable to start.
E, [2014-07-01T09:33:33.282286 #5900] ERROR – : Both http and https are
disabled, unable to start.
E, [2014-07-01T09:35:08.776432 #6068] ERROR – : Both http and https are
disabled, unable to start.
[root@laptop.local ~]#
systemctl status httpd.service
httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled)
Active: active (running) since Mon 2014-06-30 20:13:31 BST; 13h ago
Main PID: 1752 (httpd)
Status: "Total requests: 0; Current requests/sec: 0; Current traffic:
0 B/sec"
CGroup: /system.slice/httpd.service
├─1752 /usr/sbin/httpd -DFOREGROUND
├─2736 /usr/sbin/httpd -DFOREGROUND
├─2737 /usr/sbin/httpd -DFOREGROUND
├─2738 /usr/sbin/httpd -DFOREGROUND
├─2739 /usr/sbin/httpd -DFOREGROUND
└─2740 /usr/sbin/httpd -DFOREGROUND

Jun 30 20:13:31 laptop.local httpd[1752]: AH00557: httpd:
apr_sockaddr_info_get() failed for laptop.local
Jun 30 20:13:31 laptop.local httpd[1752]: AH00558: httpd: Could not
reliably determine the server’s fully qualified domain name, using
127.0.0.1. Set the 'Serv…his message
Jun 30 20:13:31 laptop.local systemd[1]: Started The Apache HTTP Server.
Hint: Some lines were ellipsized, use -l to show in full.
[root@laptop.local ~]#

Is this a failure to recognise that httpd is running?

Cheers

D

On Tuesday, 1 July 2014 09:18:10 UTC+1, Dominic Cleal wrote:
On 01/07/14 09:05, Duncan Innes wrote:
> Sorry - I had seen this, but thought it was in the clip I pasted
earlier.
>
> Jul 01 08:20:05 laptop.local systemd[1]: Starting Foreman Proxy...
> Jul 01 08:20:05 laptop.local smart-proxy[31648]:
> /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:53:in
`require':
> cannot load such file -- puppet (LoadError)

Ah okay, so our foreman-proxy package doesn't depend on Puppet as
it's a
soft dependency.  I think we'll change this in the future and use
sub-packages so we can use hard dependencies as the 1.6 proxy is
modular.

You can either disable the Puppet and Puppet CA modules under
/etc/foreman-proxy/settings.d/, or install Puppet.

-- 
Dominic Cleal
Red Hat Engineering
–
You received this message because you are subscribed to the Google
Groups “foreman-dev” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-dev+unsubscribe@googlegroups.com
mailto:foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Dominic_Cleal · June 30, 2014, 8:58am

I don't understand this - port is a valid param on the type in master:

github.com

puppetlabs/puppetlabs-postgresql/blob/master/lib/puppet/type/postgresql_psql.rb#L55-L57


status = output.exitcode if status.nil?


self.fail("Error evaluating 'onlyif' clause, returned #{status}: '#{output}'") unless status == 0

You updated the whole module, not just manifests?

···

On 30/06/14 09:53, Duncan Innes wrote: > OK - managed to checkout from github properly this time. > > Have tried both master and 3.4.x branches so far and get the following > error: > > [root@foreman modules]# foreman-installer > Invalid parameter port on Postgresql_psql[Check for existence of db > 'foreman'] at > /usr/share/foreman-installer/modules/postgresql/manifests/server/database.pp:58 > on node foreman.rhel7.local > Invalid parameter port on Postgresql_psql[Check for existence of db > 'foreman'] at > /usr/share/foreman-installer/modules/postgresql/manifests/server/database.pp:58 > on node foreman.rhel7.local

–
Dominic Cleal
Red Hat Engineering

Duncan_Innes · June 30, 2014, 9:19am

I believe so. I've got the following in
/usr/share/foreman-installer/modules -

[root@foreman modules]# pwd
/usr/share/foreman-installer/modules
[root@foreman modules]# ll
total 76
drwxr-xr-x. 9 root root 4096 Jun 27 21:36 apache
drwxr-xr-x. 7 root root 4096 Jun 27 21:36 apt
drwxr-xr-x. 7 root root 4096 Jun 27 21:36 concat
drwxr-xr-x. 5 root root 4096 Jun 27 21:36 concat_native
drwxr-xr-x. 8 root root 4096 Jun 27 21:36 dhcp
drwxr-xr-x. 8 root root 4096 Jun 27 21:36 dns
drwxr-xr-x. 5 root root 4096 Jun 27 21:36 firewall
drwxr-xr-x. 7 root root 4096 Jun 27 21:36 foreman
drwxr-xr-x. 6 root root 4096 Jun 27 21:36 foreman_proxy
drwxr-xr-x. 4 root root 4096 Jun 27 21:36 git
drwxr-xr-x. 8 root root 4096 Jun 27 21:36 mysql
lrwxrwxrwx. 1 root root 21 Jun 30 09:48 postgresql ->
postgresql.git.master
drwxr-xr-x. 7 root root 4096 Jun 27 21:34 postgresql.git.3.4.x
drwxr-xr-x. 8 root root 4096 Jun 30 09:30 postgresql.git.master
drwxr-xr-x. 7 root root 4096 Jun 27 21:36 postgresql.old
drwxr-xr-x. 7 root root 4096 Jun 27 22:25 postgresql.wrong
drwxr-xr-x. 7 root root 4096 Jun 27 21:36 puppet
drwxr-xr-x. 6 root root 4096 Jun 27 21:36 stdlib
drwxr-xr-x. 6 root root 4096 Jun 27 21:36 tftp
drwxr-xr-x. 6 root root 4096 Jun 27 21:36 xinetd
[root@foreman modules]#

Dominic_Cleal · June 30, 2014, 9:20am

Having multiple versions inside the modulepath is likely causing
problems, as Puppet will load types/providers from */lib/puppet and
won't be aware that postgresql.git.master/lib/puppet is the latest.

···

On 30/06/14 10:19, Duncan Innes wrote: > I believe so. I've got the following in > /usr/share/foreman-installer/modules - > > [root@foreman modules]# pwd > /usr/share/foreman-installer/modules > [root@foreman modules]# ll > total 76 > drwxr-xr-x. 9 root root 4096 Jun 27 21:36 apache > drwxr-xr-x. 7 root root 4096 Jun 27 21:36 apt > drwxr-xr-x. 7 root root 4096 Jun 27 21:36 concat > drwxr-xr-x. 5 root root 4096 Jun 27 21:36 concat_native > drwxr-xr-x. 8 root root 4096 Jun 27 21:36 dhcp > drwxr-xr-x. 8 root root 4096 Jun 27 21:36 dns > drwxr-xr-x. 5 root root 4096 Jun 27 21:36 firewall > drwxr-xr-x. 7 root root 4096 Jun 27 21:36 foreman > drwxr-xr-x. 6 root root 4096 Jun 27 21:36 foreman_proxy > drwxr-xr-x. 4 root root 4096 Jun 27 21:36 git > drwxr-xr-x. 8 root root 4096 Jun 27 21:36 mysql > lrwxrwxrwx. 1 root root 21 Jun 30 09:48 postgresql -> > postgresql.git.master > drwxr-xr-x. 7 root root 4096 Jun 27 21:34 postgresql.git.3.4.x > drwxr-xr-x. 8 root root 4096 Jun 30 09:30 postgresql.git.master > drwxr-xr-x. 7 root root 4096 Jun 27 21:36 postgresql.old > drwxr-xr-x. 7 root root 4096 Jun 27 22:25 postgresql.wrong

–
Dominic Cleal
Red Hat Engineering

Duncan_Innes · June 30, 2014, 10:14am

OK - I kept them around for failback etc. Should really have stored them
elsewhere.

Pruned back to just having the git master folder in there, removed the link
and renamed the git master folder to postgresql.

After a hiccup to disable gpgchecks from the foreman.repo, I'm now sitting
at the Foreman-1.6.0 console.

Thanks for your assistance (and patience).

Cheers

D

Having multiple versions inside the modulepath is likely causing

···

> problems, as Puppet will load types/providers from */lib/puppet and > won't be aware that postgresql.git.master/lib/puppet is the latest. > > -- > Dominic Cleal > Red Hat Engineering >

RHEL7 installation

Customrun command details

Set :customrun_cmd to the full path of the script you want to run,

Set :customrun_args to any args you want to pass to your custom script.

system to run against will be appended after the custom commands.

whether to use sudo before the ssh command

the command which will be sent to the host

With which user should the proxy connect

Which user to invoke sudo as to run puppet commands

#:puppet_user: root [root@laptop.local ~]# cat /etc/foreman-proxy/settings.d/puppetca.yml

– Unit foreman-proxy.service has failed.

– Unit foreman-proxy.service has failed.

Logfile created on 2014-06-30 21:05:04 +0100 by logger.rb/41954

Logfile created on 2014-06-30 21:05:04 +0100 by logger.rb/41954

[root@laptop.local ~]# cat /etc/foreman-proxy/settings.d/puppet.yml

valid providers:

puppetrun (for puppetrun/kick, deprecated in Puppet 3)

mcollective (uses mco puppet)

puppetssh (run puppet over ssh)

salt (uses salt puppet.run)

customrun (calls a custom command with args)

Customrun command details

Set :customrun_cmd to the full path of the script you want to run,

Set :customrun_args to any args you want to pass to your custom

system to run against will be appended after the custom commands.

whether to use sudo before the ssh command

the command which will be sent to the host

With which user should the proxy connect

Which user to invoke sudo as to run puppet commands

#:puppet_user: root [root@laptop.local ~]# cat /etc/foreman-proxy/settings.d/puppetca.yml

– Unit foreman-proxy.service has failed.

– Unit foreman-proxy.service has failed.

Logfile created on 2014-06-30 21:05:04 +0100 by logger.rb/41954

#:puppet_user: root
[root@laptop.local ~]# cat /etc/foreman-proxy/settings.d/puppetca.yml

#:puppet_user: root
[root@laptop.local ~]# cat /etc/foreman-proxy/settings.d/puppetca.yml