| From: | Jonathan Leroy - Inikup <jonathan(at)inikup(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | Tim Cross <theophilusx(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Commands linked to pg_wrapper not working with non-root users |
| Date: | 2018-04-12 00:36:34 |
| Message-ID: | CAC88fzEpaHFdQK0qcZr=WnWY73F6jxT3JwTxOK7nrM6Ci+vmPQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
2018-04-12 1:49 GMT+02:00 Jonathan Leroy - Inikup <jonathan(at)inikup(dot)com>:
> Maybe I will try to "dissect" pg_wrapper to find where the error
> occurs, but the script is quite complex...
OK, I've found the issue : pg_wrapper is trying to get the value of
the "data_directory" setting by reading the postgresql.conf file.
However, my user can't access the postgresql.conf file.
So I've bootstrapped a fresh Debian 8 VM with just postgresql-9.6, and
compared files permissions between that VM and my production servers.
All my production postgresql.conf files have a chmod 640 vs 644 on my new VM.
After digging, I've found that the SaltStack recipe who configure all
my servers force the file chmod to 640...
I've fixed it: everything works now. :)
Thank you all for your help!
--
Jonathan Leroy
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2018-04-12 00:41:45 | Re: Commands linked to pg_wrapper not working with non-root users |
| Previous Message | Adrian Klaver | 2018-04-12 00:09:39 | Re: Commands linked to pg_wrapper not working with non-root users |