Re: Server crashed, now cannot start postgres [FIXED] - Mailing list pgsql-general

From Rich Shepard
Subject Re: Server crashed, now cannot start postgres [FIXED]
Date
Msg-id alpine.LNX.2.11.1609121701270.1140@localhost
Whole thread Raw
In response to Re: Server crashed, now cannot start postgres  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Server crashed, now cannot start postgres [FIXED]  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Mon, 12 Sep 2016, Tom Lane wrote:

> A look at the code suggests this is shm_open() returning EACCES. Not sure
> why that's happening. If this is a Linux box, maybe the permissions on
> /dev/shm are bollixed?

Tom,

   Yes, it's a linux box. And /dev/shm/ does have incorrect permissions
(755). Thanks to your response I remembered that chromium does not run until
I follow its advice to chmod 1777 /dev/shm. Sure enough, chromium would not
load.

   So, I changed the perms on /dev/shm/ and now both postgres and chromium
work.

Very much appreciated,

Rich


pgsql-general by date:

Previous
From: Vinicius Segalin
Date:
Subject: Re: Predicting query runtime
Next
From: Tom Lane
Date:
Subject: Re: Server crashed, now cannot start postgres [FIXED]