Hi Community!
I run puppet with foreman at CentOS7 latest. Puppet 4.5.2 and foreman 1.12.
Everything is default, i installed with foreman-installer. Everything works
fine, but i need to run the foreman-installer every time i reboot the
machine. otherwise the frontend is not started and puppetmaster as well…
i`m confused about that. Smartproxy to puppet is configured. I´m just in a
hussle right now. What to do?
Thanks for your time guys!
Hi Dominic,
it seems that foremanitself won`t start. puppetdb, puppetserver and puppet
agent are up and runnig. i added a verbose output of foreman-installer,
perhaps you can see what went wrong.
foreman-installer_verbose.log (18.3 KB)
What does "not started" mean precisely? A service isn't running?
What change does the installer make each time you run it? Read the log
or run with -v.
···
On 31/01/17 11:07, klmueller80 via Foreman users wrote:
> Hi Community!
>
> I run puppet with foreman at CentOS7 latest. Puppet 4.5.2 and foreman
> 1.12. Everything is default, i installed with foreman-installer.
> Everything works fine, but i need to run the foreman-installer every
> time i reboot the machine. otherwise the frontend is not started and
> puppetmaster as well..
–
Dominic Cleal
dominic@cleal.org
shame on me - only the psql-service was the problem, you are right! thanks
a lot!
···
Am Dienstag, 31. Januar 2017 12:20:51 UTC+1 schrieb klmue...@googlemail.com:
>
> Hi Community!
>
> I run puppet with foreman at CentOS7 latest. Puppet 4.5.2 and foreman
> 1.12. Everything is default, i installed with foreman-installer. Everything
> works fine, but i need to run the foreman-installer every time i reboot the
> machine. otherwise the frontend is not started and puppetmaster as well..
> i`m confused about that. Smartproxy to puppet is configured. I´m just in a
> hussle right now. What to do?
>
>
> Thanks for your time guys!
>
>
>
>
> Hi Dominic,
>
> it seems that foremanitself won`t start.
The log only shows that PostgreSQL isn't started, which would prevent
Foreman connecting to the database. Foreman itself (under Apache) should
be running according to the log.
> puppetdb, puppetserver and
> puppet agent are up and runnig. i added a verbose output of
> foreman-installer, perhaps you can see what went wrong.
The two log lines in the installer log show that PostgreSQL is not
started. This would affect Foreman's connection to the database.
[ WARN 2017-01-31 13:54:33 verbose]
/Stage[main]/Postgresql::Server::Config/File[systemd-override]: Ensure
set to :present but file type is link so no content will be synced
This suggests that /etc/systemd/system/postgresql.service is a symlink,
you should probably remove that and re-run the installer so the module
can install the file as designed.
This might have prevented Puppet from configuring systemd to start
postgresql.service at boot.
[ WARN 2017-01-31 13:54:35 verbose]
/Stage[main]/Postgresql::Server::Service/Service[postgresqld]/ensure:
ensure changed 'stopped' to 'running'
This is the module starting postgresql.service manually. After fixing
the above, this might not be necessary. Else try running "systemctl
enable postgresql.service".
···
On 31/01/17 13:04, klmueller80 via Foreman users wrote:
–
Dominic Cleal
dominic@cleal.org