Re: BUG #5423: problems installing postgresql-8.4 deleted folder / .s.PGSQL.lock not initiate the connecti - Mailing list pgsql-bugs

From Scott Mead
Subject Re: BUG #5423: problems installing postgresql-8.4 deleted folder / .s.PGSQL.lock not initiate the connecti
Date
Msg-id n2td3ab2ec81004150551nb3248c03vdd0e674e7924644d@mail.gmail.com
Whole thread Raw
In response to BUG #5423: problems installing postgresql-8.4 deleted folder / .s.PGSQL.lock not initiate the connecti  ("Alex Soto Paez" <ALEJANDRO.SOTO666@GMAIL.COM>)
List pgsql-bugs
On Wed, Apr 14, 2010 at 8:15 PM, Alex Soto Paez <ALEJANDRO.SOTO666@gmail.com
> wrote:

>
> The following bug has been logged online:
>
> Bug reference:      5423
> Logged by:          Alex Soto Paez
> Email address:      ALEJANDRO.SOTO666@GMAIL.COM
> PostgreSQL version: 8.4
> Operating system:   linux 9.10
> Description:        problems installing postgresql-8.4 deleted folder /
> .s.PGSQL.lock not initiate the connecti
> Details:
>
> problems installing postgresql-8.4 deleted folder / var / run / postgresql
> /
> .s.PGSQL.lock not initiate the connection to port 5432
>
> when installing postgresql-8.4 is installed correctly while running the
> command:
>
> $ Service postgresql-8.4 status
>
> Published online defautl port 5432, but at reboot the machine no longer
> seems in line appears down and restart the server payable are parachute
> with
> the error:
>
>
> $sudo /ect/init.d/postgresql-8.4 restart
>
> The PostgreSQL server failed to start. Please check the log output:
> 2010-04-14 18:48:24 CDT FATAL: could not lock file </ var / run /
> postgresql
> / .s.PGSQL.lock>>: no such file? directory
>
>
>                                          [Fail]
>
> run and hand it to guide the pid file and everything goes well but when you
> see another restart the computer I get the same error described above. not
> save the folder with the Pid and does not connect to port 5432
>
> Someone can help me
>
> In advance thank you very much.
>
>
Does the '/var/run/postgresql' directory exist and is it writeable by the
postgres user?  If it is not, I would say it's a bug for the packager of
this install of postgres.  Typically, postgres puts its lock / sockets in
'/tmp'.  You say linux, but don't say which linux, by your version string
(9.10) I'm guessing that this is ubuntu?

--Scott




> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
>

pgsql-bugs by date:

Previous
From: Martin von Gagern
Date:
Subject: Re: build error: strlcat/strlcpy used from heimdal libroken.so
Next
From: Tom Lane
Date:
Subject: Re: BUG #5418: psql exits after using tab-completion with error message