Just wanted to follow up that re-installing Postgres worked (well almost—I did
have to reset the permissions and ownership on the key and pem file).
Thanks so much for all the help.
-Shawn
> On Feb 15, 2017, at 9:49 AM, Adrian Klaver wrote:
>
> On 02/15/2017 09:45 AM, Shawn Tho
Yes, definitely.
> On Feb 15, 2017, at 9:49 AM, Adrian Klaver wrote:
>
> On 02/15/2017 09:45 AM, Shawn Thomas wrote:
>> Which would you recommend? Leave the data directory in place and
>> re-install PG or copy it to somewhere else, delete it and then
>> re-instal
Yes, sadly it does explain things. Your insight has been super helpful though.
-Shawn
> On Feb 15, 2017, at 9:38 AM, Adrian Klaver wrote:
>
> On 02/15/2017 09:28 AM, Shawn Thomas wrote:
>> Well that would make more sense of things. I had removed and
>> re-installed
Which would you recommend? Leave the data directory in place and re-install PG
or copy it to somewhere else, delete it and then re-install PG?
-Shawn
> On Feb 15, 2017, at 9:36 AM, Magnus Hagander wrote:
>
> On Wed, Feb 15, 2017 at 6:28 PM, Shawn Thomas <mailto:thoma...@u.wa
get the database back in place.
-Shawn
> On Feb 15, 2017, at 9:01 AM, Adrian Klaver wrote:
>
> On 02/15/2017 08:35 AM, Shawn Thomas wrote:
>> Yes, that’s the correct sequence of scripts. And no there’s not anything
>> really helpful in the system logs.
>>
>>
directory into the newly installed one, will there
be an xlog issue?
-Shawn
> On Feb 15, 2017, at 9:09 AM, Magnus Hagander wrote:
>
> On Wed, Feb 15, 2017 at 6:03 PM, Shawn Thomas <mailto:thoma...@u.washington.edu>> wrote:
> /usr/lib/postgresql/9.4/bin/pg_ctl: No such file or di
AM, Joshua D. Drake wrote:
>
> On 02/15/2017 08:35 AM, Shawn Thomas wrote:
>> Yes, that’s the correct sequence of scripts. And no there’s not anything
>> really helpful in the system logs.
>>
>> I’m thinking that at this point I need to approach this problem a
15, 2017, at 6:35 AM, Adrian Klaver wrote:
>
> On 02/14/2017 08:47 PM, Shawn Thomas 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 mak
r wrote:
>
> On 02/14/2017 05:00 PM, Adrian Klaver wrote:
>> On 02/14/2017 12:00 PM, Shawn Thomas wrote:
>>> Yes that would be the standard approach. But the Debian package removes
>>> pg_ctl from it normal place and wraps it with a perl script in a way
>>> t
-o -c
config_file="/etc/postgresql/9.4/main/postgresql.conf”
-Shawn
> On Feb 14, 2017, at 11:52 AM, Magnus Hagander wrote:
>
> On Tue, Feb 14, 2017 at 8:47 PM, Joshua D. Drake <mailto:j...@commandprompt.com>> wrote:
> On 02/14/2017 11:43 AM, Shawn Thomas wrote:
> pangaea:/v
)
Main PID: 28668 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/postgresql.service
-Shawn
> On Feb 14, 2017, at 11:31 AM, Joshua D. Drake wrote:
>
> On 02/14/2017 11:17 AM, Shawn Thomas wrote:
>> I inadvertently deleted the ssl-cert-snakeoil.pem out from under a runni
I inadvertently deleted the ssl-cert-snakeoil.pem out from under a running
Postgres instance (9.4) which caused it to shut down. The last line of main.log:
FATAL: could not load server certificate file
"/etc/ssl/certs/ssl-cert-snakeoil.pem": No such file or directory
I've since restored the ce
12 matches
Mail list logo
