Re: Yet Another Socket .s.PGSQL.5432 Problem

From: "Hilton Perantunes" <hperantunes(at)gmail(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: Yet Another Socket .s.PGSQL.5432 Problem
Date: 2007-08-15 20:48:57
Message-ID: b24a8cca0708151348o5ef92415tc42177aa3c843359@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Thanks for answering, Julio.

When I stop the database, the socket file is automatically removed. That's
the way it happened before... but now, oddly enough, I restarted the
database at will several times, my app is still running, pgadmin too... and
no socket file is created. o.0

(and I still can't connect via bash)

Hilton

On 8/15/07, Julio Cesar Sánchez González <
knowhow(at)sistemasyconectividad(dot)com(dot)mx> wrote:
>
> El mié, 15-08-2007 a las 17:13 -0300, Hilton Perantunes escribió:
> > Hi folks!
> >
> > That's another "sob sob.. I can't connect to socket blah
> > blah .. .s.PGSQL.5432" asking for help. But this is somewhat bizarre,
> > and i'm not used to the 8.2's postgresql.conf file.
> >
> > I'm running a PostgreSQL 8.4.2 powered by Debian Sarge (very)Unstable.
> > My PHP application successfully connects to the appropriated database.
> > Even PgAdmin3 connects to the database. But my 'postgres' user cannot
> > connect to the database via command line:
> >
> > ----------
> > psql: could not connect to server:
> > Is the server running locally and accepting
> > connections on Unix domain socket
> > "/var/run/postgresql/.s.PGSQL.5432"?
> > ----------
> >
> > Well, the socket file actually IS there (zero bytes of size) and it's
> > given the correct permissions. Now, I have this in my pg_hba.conf
> > (replace XXX by my network, and I just added the second line recently,
> > in despair):
> >
>
> Try stoping the postgresql process and delete the socket unix file,
> restart the postgresql daemon and we to mean.
>
> > ----------
> > # "local" is for Unix domain socket connections only
> > local all all trust
> > # IPv4 local connections:
> > host all all XXX.XXX.XXX.1 /24 trust
> > host all postgres 127.0.0.1/32 trust
> > # IPv6 local connections:
> > host all all ::1/128 trust
> > ----------
> >
> > Finally, that's the hot section in my postgresql.conf:
> >
> > ----------
> > listen_addresses = '*' # what IP address(es) to
> > listen on;
> > port = 5432 # (change requires restart)
> > ----------
> >
> > So, I just can't connect in the database through command line. Someone
> > can waste some time helping me?
> >
> > Thanks in advance =)
> >
> > --
> > Hilton William Ganzo Perantunes
> > Sistemas de Informação - Universidade Federal de Santa Catarina
> > --
> > Dinheiro não traz felicidade, mas dá uma sensação tão parecida... -_-
>
>
>
> --
> Regards,
>
> Julio Cesar Sánchez González
> www.sistemasyconectividad.com.mx
> blog: http://darkavngr.blogspot.com
>
> ---
> Ahora me he convertido en la muerte, destructora de mundos.
> Soy la Muerte que se lleva todo, la fuente de las cosas que vendran.
>
>

--
Hilton William Ganzo Perantunes
Sistemas de Informação - Universidade Federal de Santa Catarina
--
Dinheiro não traz felicidade, mas dá uma sensação tão parecida... -_-

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2007-08-15 22:01:17 Re: Yet Another Socket .s.PGSQL.5432 Problem
Previous Message Julio Cesar Sánchez González 2007-08-15 20:34:44 Re: Yet Another Socket .s.PGSQL.5432 Problem