| From: | Steve Atkins <steve(at)blighty(dot)com> |
|---|---|
| To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Can't restart Postgres |
| Date: | 2017-02-15 17:11:27 |
| Message-ID: | 501D8220-7F09-4AD3-BF8E-C456E1EB24E2@blighty.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On Feb 14, 2017, at 8:47 PM, Shawn Thomas <thomassd(at)u(dot)washington(dot)edu> wrote:
>
> No it doesn’t matter if run with sudo, postgres or even root. Debian actually wraps the command and executes some some initial scripts with different privileges but ends up making sure that Postgres ends up running under the postgres user. I get the same output if run with sudo:
>
> sudo systemctl status postgresql(at)9(dot)4-main(dot)service -l
> Error: could not exec start -D /var/lib/postgresql/9.4/main -l /var/log/postgresql/postgresql-9.4-main.log -s -o -c config_file="/etc/postgresql/9.4/main/postgresql.conf”
There's a suspicious hole between "exec" and "start" where I'd expect to see the full path to the pg_ctl binary. As though a variable were unset in a script or config file.
Cheers,
Steve
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2017-02-15 17:15:10 | Re: Can't restart Postgres |
| Previous Message | Magnus Hagander | 2017-02-15 17:09:18 | Re: Can't restart Postgres |