Fatal error by chef-compliance-ctl reconfigure


#1

Hi

I’m getting a fatal error by configuring chef-compliance

[2016-04-26T21:54:02+02:00] ERROR: Running exception handlers
Running handlers complete
[2016-04-26T21:54:02+02:00] ERROR: Exception handlers complete
Chef Client failed. 9 resources updated in 01 minutes 19 seconds
[2016-04-26T21:54:02+02:00] FATAL: Stacktrace dumped to /opt/chef-compliance/embedded/cookbooks/cache/chef-stacktrace.out
[2016-04-26T21:54:02+02:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
[2016-04-26T21:54:02+02:00] FATAL: Mixlib::ShellOut::ShellCommandFailed: enterprise_pg_database[chef_compliance] (chef-compliance::_postgresql-enable line 47) had an error: Mixlib::ShellOut::ShellCommandFailed: execute[create_database_chef_compliance] (/opt/chef-compliance/embedded/cookbooks/cache/cookbooks/enterprise/providers/pg_database.rb line 19) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received ‘1’
---- Begin output of createdb --template template0 --encoding UTF-8 chef_compliance ----
STDOUT:
STDERR: createdb: could not connect to database template1: FATAL: no pg_hba.conf entry for host “[local]”, user “chef-pgsql”, database “template1”, SSL off
---- End output of createdb --template template0 --encoding UTF-8 chef_compliance ----
Ran createdb --template template0 --encoding UTF-8 chef_compliance returned 1

It seems that the user does not exist in the pg_hba.conf file.
cat /var/opt/opscode/postgresql/9.2/data/pg_hba.conf
local all opscode-pgsql peer

host all opscode-pgsql samehost md5

host all all 127.0.0.1/32 md5
host all all ::1/128 md5

How to change this user?


#2

Michael,

Did you figure this out ? Seem to be hitting same problem…

P


#3

No, We did use a separate server for Chef Compliance now and not on the same server as Chef Server