Foreman-installer fails with postgresql-9.4

Support
1

I'm trying to setup puppet/foreman.

puppetdb-4.4.0
puppetserver-2.7.2
puppet-agent-1.10.1
postgresql94-server

Systemd start for postgresql failed!
journalctl log for postgresql:
– Logs begin at Sun 2017-05-28 21:56:15 BST, end at Tue 2017-05-30
12:59:33 BST. –
May 30 12:59:33 systemd[1]: postgresql.service lacks both ExecStart= and
ExecStop= setting. Refusing.
May 30 12:59:33 systemd[1]: postgresql.service lacks both ExecStart= and
ExecStop= setting. Refusing.

/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/service/systemd.rb:166:in
rescue in start' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/service/systemd.rb:163:instart'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/service.rb:103:in
block (3 levels) in <module:Puppet>' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/property.rb:487:inset'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/property.rb:561:in sync' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/service.rb:114:insync'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:236:in
sync' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:134:insync_if_needed'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:80:in
perform_changes' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:21:inevaluate'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:230:in
apply' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:246:ineval_resource'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:163:in
call' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:163:inblock (2 levels) in evaluate'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:387:in block in thinmark' /opt/puppetlabs/puppet/lib/ruby/2.1.0/benchmark.rb:294:inrealtime'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:386:in thinmark' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:163:inblock in evaluate'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:118:in
traverse' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:154:inevaluate'
/usr/share/gems/gems/kafo-2.0.0/modules/kafo_configure/lib/puppet/parser/functions/add_progress.rb:30:in
evaluate_with_trigger' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:222:inblock in apply'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/log.rb:155:in
with_destination' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/report.rb:142:inas_logging_destination'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:221:in
apply' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:171:inblock in apply_catalog'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:224:in block in benchmark' /opt/puppetlabs/puppet/lib/ruby/2.1.0/benchmark.rb:294:inrealtime'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:223:in
benchmark' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:170:inapply_catalog'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:343:in
run_internal' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:221:inblock in run'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:in
override' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:294:inoverride'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:195:in
run' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:350:inapply_catalog'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:274:in
block in main' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:inoverride'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:294:in override' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:225:inmain'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:170:in
run_command' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:358:inblock in run'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:542:in
exit_on_fail' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:358:inrun'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:132:in
run' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:inexecute'
/opt/puppetlabs/puppet/bin/puppet:5:in `<main>'
/Stage[main]/Postgresql::Server::Service/Service[postgresqld]/ensure:
change from stopped to running failed: Systemd start for postgresql failed!
journalctl log for postgresql:
– Logs begin at Sun 2017-05-28 21:56:15 BST, end at Tue 2017-05-30
12:59:33 BST. –
May 30 12:59:33 systemd[1]: postgresql.service lacks both ExecStart= and
ExecStop= setting. Refusing.
May 30 12:59:33 systemd[1]: postgresql.service lacks both ExecStart= and
ExecStop= setting. Refusing.

Has anyone else encountered this issue? Any help would be appreciated.

2

Hi,

> I'm trying to setup puppet/foreman.
>
> postgresql94-server

Do I guess right this is from yum.postgresql.org?

> May 30 12:59:33 systemd[1]: postgresql.service lacks both ExecStart= and
> ExecStop= setting. Refusing.
> May 30 12:59:33 systemd[1]: postgresql.service lacks both ExecStart= and
> ExecStop= setting. Refusing.

If your packages are from yum.postgresql.org, then the service you need
is called postgresql-9.4, not postgresql. Not sure where
postgresql.service is comming from in your case then.

That said, I have no idea if we can tell the installer to use an
alternative PostgreSQL service name.

Regards
Evgeni

··· On Tue, May 30, 2017 at 05:10:27AM -0700, mc14983@bristol.ac.uk wrote:

–
Beste Grüße/Kind regards,

Evgeni Golov
Software Engineer

Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham, Michael O’Neill, Eric Shander

3

Hi,

··· On Tue, May 30, 2017 at 05:10:27AM -0700, mc14983@bristol.ac.uk wrote: > postgresql94-server

Try to set the following in /etc/foreman-installer/custom-hiera.yaml:

postgresql::globals::manage_package_repo: true
postgresql::globals::version: ‘9.4’

Regards

Michael Moll

4

That worked! Now I've different errors. Thanks.

··· -- Kind regards

mc
​ michelle.crouch@bristol.ac.uk
On 30 May 2017 at 15:23, Michael Moll kvedulv@kvedulv.de wrote:

Hi,

On Tue, May 30, 2017 at 05:10:27AM -0700, mc14983@bristol.ac.uk wrote:

postgresql94-server

Try to set the following in /etc/foreman-installer/custom-hiera.yaml:

postgresql::globals::manage_package_repo: true
postgresql::globals::version: ‘9.4’

Regards

Michael Moll

5

That did it for me, thank you you kind person!

···

On Tuesday, May 30, 2017 at 7:23:42 AM UTC-7, Michael Moll wrote:

Hi,

On Tue, May 30, 2017 at 05:10:27AM -0700, mc1...@bristol.ac.uk > <javascript:> wrote:
> postgresql94-server

Try to set the following in /etc/foreman-installer/custom-hiera.yaml:

postgresql::globals::manage_package_repo: true
postgresql::globals::version: '9.4'

Regards
--
Michael Moll