Skip site navigation (1) Skip section navigation (2)

Re: BUG #3034: FATAL: could not open lock file "/tmp/.s.PGSQL.5432.lock": Permission denied

From: tomas(at)tuxteam(dot)de
To: Jessica <hxq7681(at)cs(dot)rit(dot)edu>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #3034: FATAL: could not open lock file "/tmp/.s.PGSQL.5432.lock": Permission denied
Date: 2007-02-23 08:52:47
Message-ID: 20070223085246.GC17053@www.trapp.net (view raw or flat)
Thread:
Lists: pgsql-bugs
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, Feb 19, 2007 at 09:53:26PM +0000, Jessica wrote:
> 
> The following bug has been logged online:
> 
> Bug reference:      3034
> Logged by:          Jessica
> Email address:      hxq7681(at)cs(dot)rit(dot)edu
> PostgreSQL version: 8.2
> Operating system:   Unix
> Description:        FATAL:  could not open lock file
> "/tmp/.s.PGSQL.5432.lock": Permission denied

It looks like the postmaster was started (at least once) with the wrong
unser ID. Typically there is a user 'postgres' especially for this.
Always create the DB and start and stop the database under this user.

The operating systems's start and stop scripts usually do this for you
(they must be called as root, obviously).

HTH
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFF3qteBcgs9XrR2kYRAs6BAJ9sLxaQ8ys+Tq3giqn/Khv/MfwTIwCdGgje
UTubw0Y2WT15mno6jhbPmwI=
=02xM
-----END PGP SIGNATURE-----


In response to

pgsql-bugs by date

Next:From: Tom LaneDate: 2007-02-23 16:06:33
Subject: Re: BUG #3052: Inconsistent results from PQexec... with rules
Previous:From: tomasDate: 2007-02-23 08:50:16
Subject: Re: BUG #3033: performance issue with self join

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group