Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

During database crash, RedHat can't find pg_ident.conf #309

Open
gclough opened this issue Mar 20, 2018 · 2 comments
Open

During database crash, RedHat can't find pg_ident.conf #309

gclough opened this issue Mar 20, 2018 · 2 comments
Labels
Projects

Comments

@gclough
Copy link
Collaborator

gclough commented Mar 20, 2018

If the database crashes, then during crash recovery it looks for pg_ident.conf... and fails:

2018-03-20 15:07:25 UTC [11965]: [3-1] user=,db=,app=,client= LOG:  could not open usermap file "/etc/postgresql/9.6/data/pg_ident.conf": No such file or directory
2018-03-20 15:07:25 UTC [11967]: [1-1] user=,db=,app=,client= LOG:  database system was interrupted while in recovery at 2018-03-20 15:05:24 UTC
2018-03-20 15:07:25 UTC [11967]: [2-1] user=,db=,app=,client= HINT:  This probably means that some data is corrupted and you will have to use the last backup for recovery.

By default on RedHat/CentOS this should be in $PGDATA, but because of the "Ubuntu" layout this file is expected to be in /etc/postgresql/{{ postgresql_version }}/data:

ident_file = '/etc/postgresql/9.6/data/pg_ident.conf' # ident configuration file

... but it's currently in $PGDATA/pg_ident.conf

Personally I'd prefer to see this playbook configure more of a "RedHat" layout, which means putting everything into $PGDATA, and not scattering things into /etc/postgresql...

@aoyawale
Copy link
Contributor

agreed. will have to make a change somewhere were each distro can have their default location.

@aoyawale aoyawale added the bug label Mar 30, 2018
@aoyawale aoyawale added this to In progress in Ehancements Apr 2, 2018
@gclough
Copy link
Collaborator Author

gclough commented Apr 3, 2018

This should get fixed by #288, but will likely need a lot of merging due to the recent changes. I'll see what I can sort out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Ehancements
  
In progress
Development

No branches or pull requests

2 participants