X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id B2E89D72AA for ; Fri, 14 Oct 2005 17:49:44 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 00999-03 for ; Fri, 14 Oct 2005 20:49:37 +0000 (GMT) Received: from window.monsterlabs.com (window.monsterlabs.com [216.183.105.176]) by svr1.postgresql.org (Postfix) with SMTP id 449E6D9EB0 for ; Fri, 14 Oct 2005 17:49:38 -0300 (ADT) Received: (qmail 26575 invoked from network); 14 Oct 2005 20:49:33 -0000 Received: from pcp0012204803pcs.blairblvd.tn.nash.comcast.net (HELO ?192.168.15.103?) (69.245.49.69) by 0 with SMTP; 14 Oct 2005 20:49:33 -0000 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> Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Cc: Tom Lane Content-Transfer-Encoding: 7bit From: "Thomas F. O'Connell" Subject: Re: postmaster blues after system restart Date: Fri, 14 Oct 2005 15:49:29 -0500 To: pgsql-admin@postgresql.org X-Mailer: Apple Mail (2.734) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.017 required=5 tests=[AWL=0.017] X-Spam-Level: X-Archive-Number: 200510/169 X-Sequence-Number: 19241 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" 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.