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

Re: Trouble starting server

From: Barry Moore <barry(dot)moore(at)genetics(dot)utah(dot)edu>
To: Jeff Frost <jeff(at)frostconsultingllc(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Trouble starting server
Date: 2006-02-16 18:40:16
Message-ID: 7C295891-3DCE-4606-94D8-7EB5C451F04B@genetics.utah.edu (view raw or flat)
Thread:
Lists: pgsql-admin
Thanks.  I wasn't sure that I should do that since I didn't change  
those permissions since I hadn't done anything with it.  There is a  
new user who is taking over admin of this machine, so I'll have to  
ask if the did anything to affect this.

Barry

On Feb 16, 2006, at 11:30 AM, Jeff Frost wrote:

> On Thu, 16 Feb 2006, Barry Moore wrote:
>
>> So with my minimal system admin skills I'm guessing that '/ 
>> tmp/.s.PGSQL.5432' is lock file where the system puts a lock on  
>> port 5432 for postmaster to listen, but the pg_ctl and postmaster  
>> commands can't create that file because /tmp is writeable only by  
>> root (drwxr-xr-x   11 root root  4096 Feb 16 11:06 tmp).  Of  
>> course I can't start the postmaster as root, so I'm a bit  
>> perplexed as to what to do, and why I never had this problem before.
>
> You need to change the permissions on /tmp.  I'd be curious to know  
> how it got this way.  Has anyone done chmods on /tmp?  It should be  
> 1777/drwxrwxrwt, so a chmod 1777 /tmp should fix it for you.
>
>
> -- 
> Jeff Frost, Owner 	<jeff(at)frostconsultingllc(dot)com>
> Frost Consulting, LLC 	http://www.frostconsultingllc.com/
> Phone: 650-780-7908	FAX: 650-649-1954


In response to

pgsql-admin by date

Next:From: Scott MarloweDate: 2006-02-16 20:14:13
Subject: Re: Postgresql performance and tuning questions
Previous:From: Jeff FrostDate: 2006-02-16 18:30:58
Subject: Re: Trouble starting server

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