On 31/01/17 13:04, klmueller80 via Foreman users wrote:
> 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".

-- 
Dominic Cleal
[email protected]

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to