From: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
---|---|
To: | Stefan Schwarzer <stefan(dot)schwarzer(at)unep(dot)org> |
Cc: | pgsql-general(at)postgresql(dot)org, Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
Subject: | Re: Error message "psql: could not connect to server: No such file or directory" |
Date: | 2012-06-24 06:49:40 |
Message-ID: | 4FE6B884.4060508@ringerc.id.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 06/22/2012 03:19 PM, Stefan Schwarzer wrote:
>> sudo su - _postgres /usr/local/pgsql-9.1/bin/initdb -U postgres -D /usr/local/pgsql-9.1/data --encoding=UTF8 --locale=en_US
>> sudo su - _postgres /usr/local/pgsql-9.1/bin/pg_ctl start -D /usr/local/pgsql-9.1/data
>>
>> Although I don't get an error message, I don't have the feeling that it started the server. There is still nothing in the process list, and a normal "psql" results in the same message as before "psql: could not connect…"
>>
>> So sorry for bothering you guys… just being really frustrated now…
>>
>> If you have any ideas, please let me know… :-)
> I just went back to the postgres documentation [1] (actually reading all google results on the error message one after the other) and tried out what was said there (adapted to my conditions):
>
> sudo -u _postgres /usr/local/pgsql-9.1/bin/postgres -D /usr/local/pgsql-9.1/data
>
> and suddenly postgres runs….
>
You really should be able to use pg_ctl though.
I'm puzzled about why you don't appear to be looking at the server error
logs (/usr/local/pgsql-9.1/data/pg_log) during troubleshooting. They're
your main source of info.
--
Craig Ringer
From | Date | Subject | |
---|---|---|---|
Next Message | Tim Uckun | 2012-06-24 06:57:27 | Hot standby streaming replication doesn't work |
Previous Message | Raghavendra | 2012-06-24 02:44:13 | Re: row_to_json question |