Hi,
Trying to run foreman-installer and its fails early on as it can’t start HTTPD as we seem to be missing a few SSL related files like a hostname.pem file and crl.pem I thought foreman would install and initially setup ssl? Assuming we are missing something here?
Any help would be much appreciated…
Many thanks,
Tim
Could you provide some more information about how you’re installing? It sounds like you’re installing without Puppet which means you must supply custom certificates. CRL is optional, but you must set it to an empty string when you’re not using it.
Hi,
We are using the following options:
first run
–foreman-initial-admin-password
–foreman-db-adapter
–foreman-db-database
–foreman-db-host
–foreman-db-manage
–foreman-db-username
–foreman-db-password
–foreman-db-port
–foreman-configure-scl-repo
–foreman-configure-epel-repo
then do some PostgreSQL stuff
second run
foreman-installer
–enable-foreman-plugin-puppetdb
–puppet-server-puppetdb-host
–puppet-server-reports
–puppet-server-storeconfigs-backend
–foreman-plugin-puppetdb-address
–foreman-plugin-puppetdb-dashboard-address
But obviously failing on the first section of the installer
Thanks,
Tim
Are you sure you’re not passing --enable-puppet false or --puppet-server false? By default we rely on Puppet certificates. The installer will attempt to make sure the Puppet CA is set up before using them, but if you disable that, the server must be provisioned with certificates before running the installer or providing custom paths.
Very sure we are not passing those values… Assume the default is to use puppet…
Have moved on abit….
Now the foreman-installer states it can’t start puppetserver
Once the installer finishes, its states the enable-foreman-plugin-puppetdb - command not found
This however seems a valid option for version 1.22
the value we are trying to use is for that option:
https://hostname:8081/v2/commands - Is this correct?
Firewall is open for 8081
It’s much easier if you give the exact error messages and exact commands (with passwords obfuscated). Right now I don’t know I have to guess what you mean and since my time is limited, responding ends up very low on my todo list.
Using the following options:
–foreman-initial-admin-password=######
–foreman-db-adapter=postgresql
–foreman-db-database=foreman
–foreman-db-host=localhost
–foreman-db-manage=false
–foreman-db-username=foreman
–foreman-db-password=#######
–foreman-db-port=5432
–foreman-configure-scl-repo=false
–foreman-configure-epel-repo=false
–enable-foreman-plugin-puppetdb
–puppet-server-puppetdb-host=for01.playpen.local
–puppet-server-reports=foreman,puppetdb
–puppet-server-storeconfigs-backend=puppetdb
–foreman-plugin-puppetdb-address=https://for01.playpen.local:8081/v2/commands
Red text is dsiplayed - failed to start puppetserver
Once installer finished, summary info is given and at the bottom of that states
–enable-foreman-plugin-puppetdb - command not found
Errors from /var/log/foreman-installer
[ERROR 2019-09-24T15:33:50 main] Systemd start for puppetserver failed!
[ERROR 2019-09-24T15:33:50 main] journalctl log for puppetserver:
[ERROR 2019-09-24T15:33:50 main] – Logs begin at Tue 2019-09-24 15:31:47 BST, end at Tue 2019-09-24 15:33:50 BST. –
[ERROR 2019-09-24T15:33:50 main] Sep 24 15:33:21 for01.playpen.local systemd[1]: Starting puppetserver Service…
[ERROR 2019-09-24T15:33:50 main] Sep 24 15:33:49 for01.playpen.local puppetserver[9231]: Failed to load feature test for posix: can’t find user for 0
[ERROR 2019-09-24T15:33:50 main] Sep 24 15:33:49 for01.playpen.local puppetserver[9231]: Puppet::Error: Cannot determine basic system flavour
[ERROR 2019-09-24T15:33:50 main] Sep 24 15:33:49 for01.playpen.local puppetserver[9231]: at /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/feature/base.rb:19
[ERROR 2019-09-24T15:33:50 main] Sep 24 15:33:49 for01.playpen.local puppetserver[9231]: require at org/jruby/RubyKernel.java:970
[ERROR 2019-09-24T15:33:50 main] Sep 24 15:33:49 for01.playpen.local puppetserver[9231]: require at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:59
so I set /tmp to exec instead of noexec and get the following now:
Preparing installation Done
Success!
So just the command not found issue now 