Re: Post-Reboot Issue: Postmaster Not Accessible

On Wed, 28 Feb 2007, Tom Lane wrote:

> Stop the postmaster, remove the bogus socket file by hand, start the
> postmaster.

Tom,

That did it.

> I imagine that if you check the postmaster log you will notice a bleat
> near the beginning about failing to open the socket file (because of the
> pre-existence of the root-owned file). It would come up anyway as long as
> it could establish a TCP listen socket.

I see.

> Offhand I would guess that things got this way because of some errant
> tmp-cleaning script; perhaps the socket file got chown'd to root sometime
> in the past during the previous postmaster's life.

Something certainly did the wrong thing. Now that I know I can safely
delete the socket file I'm prepared if this ever happens again.

Thank you,

Rich

--
Richard B. Shepard, Ph.D. | The Environmental Permitting
Applied Ecosystem Services, Inc. | Accelerator(TM)
<http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863