Обсуждение: Re: Error when starting postgres database!!
Hi,
I'm facing an error in starting my postgresql database. The error is as
shown below:
bash-4.1$ psql
psql: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket
"/var/run/postgresql/.s.PGSQL.5432"?
But surprisingly the port was open at 5432, I got it confirmed as below:
top -u postgres
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
6180 postgres 20 0 164m 2296 1824 S 0.9 0.0 0:00.36
/usr/pgsql-9.1/bin/pg_statsinfod 6171
6861 postgres 20 0 17176 1324 952 R 0.9 0.0 0:00.01 top -u postgres
6171 postgres 20 0 234m 20m 19m S 0.0 0.3 0:00.47
/usr/pgsql-9.1/bin/postmaster -p 5432 -D /home/new_data/9.1/data
6173 postgres 20 0 179m 1444 636 S 0.0 0.0 0:00.24 postgres:
pg_statsinfo launcher process
6174 postgres 20 0 181m 1368 520 S 0.0 0.0 0:00.03 postgres:
logger process
6176 postgres 20 0 234m 1792 920 S 0.0 0.0 0:00.17 postgres:
writer process
6177 postgres 20 0 234m 1520 648 S 0.0 0.0 0:00.14 postgres: wal
writer process
6178 postgres 20 0 235m 3300 1344 S 0.0 0.0 0:00.14 postgres:
autovacuum launcher process
6179 postgres 20 0 184m 1936 604 S 0.0 0.0 0:00.26 postgres: stats
collector process
6826 postgres 20 0 107m 1740 1304 S 0.0 0.0 0:00.00 bash
Is there any issue with my configuration?? Kindly suggest!
Regards,
Pavan
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html
On 09/10/18 17:22, pavan95 wrote: > Hi, > > I'm facing an error in starting my postgresql database. The error is as > shown below: > > bash-4.1$ psql > psql: could not connect to server: No such file or directory > Is the server running locally and accepting > connections on Unix domain socket > "/var/run/postgresql/.s.PGSQL.5432"? The default client config expects the server's socket in /var/run/postgresql. Yours is not there. Try this: $ psql -h localhost > > But surprisingly the port was open at 5432, I got it confirmed as below: > > top -u postgres > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 6180 postgres 20 0 164m 2296 1824 S 0.9 0.0 0:00.36 > /usr/pgsql-9.1/bin/pg_statsinfod 6171 > 6861 postgres 20 0 17176 1324 952 R 0.9 0.0 0:00.01 top -u postgres > 6171 postgres 20 0 234m 20m 19m S 0.0 0.3 0:00.47 > /usr/pgsql-9.1/bin/postmaster -p 5432 -D /home/new_data/9.1/data > 6173 postgres 20 0 179m 1444 636 S 0.0 0.0 0:00.24 postgres: > pg_statsinfo launcher process > 6174 postgres 20 0 181m 1368 520 S 0.0 0.0 0:00.03 postgres: > logger process > 6176 postgres 20 0 234m 1792 920 S 0.0 0.0 0:00.17 postgres: > writer process > 6177 postgres 20 0 234m 1520 648 S 0.0 0.0 0:00.14 postgres: wal > writer process > 6178 postgres 20 0 235m 3300 1344 S 0.0 0.0 0:00.14 postgres: > autovacuum launcher process > 6179 postgres 20 0 184m 1936 604 S 0.0 0.0 0:00.26 postgres: stats > collector process > 6826 postgres 20 0 107m 1740 1304 S 0.0 0.0 0:00.00 bash > > Is there any issue with my configuration?? Kindly suggest! > > > Looks like a non standard setup (data directory /home/new_data/9.1/data). What is unix_socket_directories set to in your postgresql.conf? (If not set then it is probably using /tmp) regards Mark
On 09/10/18 17:22, pavan95 wrote: > Hi, > > I'm facing an error in starting my postgresql database. The error is as > shown below: > > bash-4.1$ psql > psql: could not connect to server: No such file or directory > Is the server running locally and accepting > connections on Unix domain socket > "/var/run/postgresql/.s.PGSQL.5432"? The default client config expects the server's socket in /var/run/postgresql. Yours is not there. Try this: $ psql -h localhost > > But surprisingly the port was open at 5432, I got it confirmed as below: > > top -u postgres > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 6180 postgres 20 0 164m 2296 1824 S 0.9 0.0 0:00.36 > /usr/pgsql-9.1/bin/pg_statsinfod 6171 > 6861 postgres 20 0 17176 1324 952 R 0.9 0.0 0:00.01 top -u postgres > 6171 postgres 20 0 234m 20m 19m S 0.0 0.3 0:00.47 > /usr/pgsql-9.1/bin/postmaster -p 5432 -D /home/new_data/9.1/data > 6173 postgres 20 0 179m 1444 636 S 0.0 0.0 0:00.24 postgres: > pg_statsinfo launcher process > 6174 postgres 20 0 181m 1368 520 S 0.0 0.0 0:00.03 postgres: > logger process > 6176 postgres 20 0 234m 1792 920 S 0.0 0.0 0:00.17 postgres: > writer process > 6177 postgres 20 0 234m 1520 648 S 0.0 0.0 0:00.14 postgres: wal > writer process > 6178 postgres 20 0 235m 3300 1344 S 0.0 0.0 0:00.14 postgres: > autovacuum launcher process > 6179 postgres 20 0 184m 1936 604 S 0.0 0.0 0:00.26 postgres: stats > collector process > 6826 postgres 20 0 107m 1740 1304 S 0.0 0.0 0:00.00 bash > > Is there any issue with my configuration?? Kindly suggest! > > > Looks like a non standard setup (data directory /home/new_data/9.1/data). What is unix_socket_directories set to in your postgresql.conf? (If not set then it is probably using /tmp) regards Mark
pavan95 <pavan.postgresdba@gmail.com> writes:
> I'm facing an error in starting my postgresql database. The error is as
> shown below:
> bash-4.1$ psql
> psql: could not connect to server: No such file or directory
> Is the server running locally and accepting
> connections on Unix domain socket
> "/var/run/postgresql/.s.PGSQL.5432"?
Note the error message: it mentions the Unix socket location
"/var/run/postgresql/.s.PGSQL.5432". This means the psql (or
more precisely, libpq.so) that you're using thinks that PG
socket files live in /var/run/postgresql. That is *not* standard;
as shipped by the community, PG puts its socket files in "/tmp".
However, various distros think that is bad style and override
the build option to put the socket files elsewhere, most often
/var/run/postgresql.
In short, you are probably using a vendor-supplied libpq to
try to talk to a PG server that was built from unmodified
community code. You could confirm the latter by looking to see
if there's a /tmp/.s.PGSQL.5432 socket file.
You could use "psql -h /tmp" to override libpq's idea of the
socket location, or use "psql -h localhost" to forget about
socket files and connect via TCP, or change the server's
unix_socket_directories parameter to make it create a socket
(or additional socket) in /var/run/postgresql, or replace
either your libpq or your server with something that's got
the same built-in default location as the other end.
regards, tom lane
pavan95 <pavan.postgresdba@gmail.com> writes:
> I'm facing an error in starting my postgresql database. The error is as
> shown below:
> bash-4.1$ psql
> psql: could not connect to server: No such file or directory
> Is the server running locally and accepting
> connections on Unix domain socket
> "/var/run/postgresql/.s.PGSQL.5432"?
Note the error message: it mentions the Unix socket location
"/var/run/postgresql/.s.PGSQL.5432". This means the psql (or
more precisely, libpq.so) that you're using thinks that PG
socket files live in /var/run/postgresql. That is *not* standard;
as shipped by the community, PG puts its socket files in "/tmp".
However, various distros think that is bad style and override
the build option to put the socket files elsewhere, most often
/var/run/postgresql.
In short, you are probably using a vendor-supplied libpq to
try to talk to a PG server that was built from unmodified
community code. You could confirm the latter by looking to see
if there's a /tmp/.s.PGSQL.5432 socket file.
You could use "psql -h /tmp" to override libpq's idea of the
socket location, or use "psql -h localhost" to forget about
socket files and connect via TCP, or change the server's
unix_socket_directories parameter to make it create a socket
(or additional socket) in /var/run/postgresql, or replace
either your libpq or your server with something that's got
the same built-in default location as the other end.
regards, tom lane
Thank You mark. I was able to connect now!!! -- Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html
Thank You mark. I was able to connect now!!! -- Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html
Thank you soo much, for your valuable explanation. Regards, Pavan -- Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html