pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Thomas F. O'Connell <tfo@sitening.com>
To: pgsql-admin@postgresql.org
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: postmaster blues after system restart
Date: Fri, 14 Oct 2005 15:49:29 -0500
Message-ID: <D32FD2AB-1299-4D34-ACCF-20E3D653B8F0@sitening.com> (raw)
In-Reply-To: <06FA92B9-81CA-493D-BB05-6A0F85B9220D@sitening.com>
References: <52873FF7-8AEE-4257-9CDC-BB6D402E87F0@sitening.com>
	<4889.1129257347@sss.pgh.pa.us>
	<06FA92B9-81CA-493D-BB05-6A0F85B9220D@sitening.com>

The culprit that ended up leading to my original post was an NFS  
script that cleans out /tmp. It was running as the last thing in a  
given boot level, so it blew away the socket file in /tmp.

Restarting postgres after boot recreated the file, so that explained  
the behavior discrepancy I was seeing.

--
Thomas F. O'Connell
Co-Founder, Information Architect
Sitening, LLC

Open Source Solutions. Optimized Web Development.

http://www.sitening.com/
110 30th Avenue North, Suite 6
Nashville, TN 37203-6320
615-469-5150
615-469-5151 (fax)

On Oct 13, 2005, at 9:40 PM, Thomas F. O'Connell wrote:

> On Oct 13, 2005, at 9:35 PM, Tom Lane wrote:
>
>> "Thomas F. O'Connell" <tfo@sitening.com> writes:
>>
>>> When I restart, everything seems to come up fine with the exception
>>> that postmaster starts in a state such that it doesn't seem to be
>>> accepting connections (either over UNIX or TCP/IP). As best I can
>>> tell, it is using the init script to start postgres because
>>> pg_autovacuum tries to start, too, and dies shortly after the box
>>> comes up because it, too, cannot connect to postgres.
>>
>> hmmm ... maybe you need to start your DNS server first?
>
> I'll check the order in which services are started. But would the  
> DNS server prevent UNIX socket connections?
>
>>> Also, is there any way to get more status out of a postmaster if one
>>> cannot connect to it?
>>
>> One thing I'd look into is exactly what ports it's listening to ---
>> try lsof and/or netstat for this.  Also, have you looked at the
>> postmaster log?
>
> I'll take a look at the ports. I was wondering about the best way  
> to do that.
>
> The postmaster log gives no evidence of anything out of the ordinary.



view thread (12+ messages)  latest in thread

Message-ID: <D32FD2AB-1299-4D34-ACCF-20E3D653B8F0@sitening.com>
Permalink:  ../D32FD2AB-1299-4D34-ACCF-20E3D653B8F0@sitening.com/
Also on:    postgresql.org/message-id/D32FD2AB-1299-4D34-ACCF-20E3D653B8F0@sitening.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: tfo@sitening.com, tgl@sss.pgh.pa.us
  Subject: Re: postmaster blues after system restart
  In-Reply-To: <D32FD2AB-1299-4D34-ACCF-20E3D653B8F0@sitening.com>
  References: <52873FF7-8AEE-4257-9CDC-BB6D402E87F0@sitening.com> <4889.1129257347@sss.pgh.pa.us> <06FA92B9-81CA-493D-BB05-6A0F85B9220D@sitening.com> <D32FD2AB-1299-4D34-ACCF-20E3D653B8F0@sitening.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox