psql: error: could not connect to server: Connection refused

Поиск
Список
Период
Сортировка
От BeeRich Lists
Тема psql: error: could not connect to server: Connection refused
Дата
Msg-id 5C6C7AA2-88FF-4F15-B7AC-92B2C2584877@gmail.com
обсуждение исходный текст
Ответы Re: psql: error: could not connect to server: Connection refused  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-novice
Hi folks.  I cannot connect to my postgres server.  I’ve run through all the directives and I still can’t understand
whythis isn’t showing up.   

psql: error: could not connect to server: Connection refused
    Is the server running on host "server1.local" (192.168.1.23) and accepting
    TCP/IP connections on port 5432?

I cannot find an open port on that box using nmap for ports 5400-6500:

Starting Nmap 7.92 ( https://nmap.org ) at 2022-07-03 19:48 EDT
Nmap scan report for 192.168.1.23
Host is up (0.00041s latency).
All 1101 scanned ports on 192.168.1.23 are in ignored states.
Not shown: 1090 filtered tcp ports (no-response), 11 filtered tcp ports (admin-prohibited)
MAC Address: D0:50:99:87:7B:4A (ASRock Incorporation)

Nmap done: 1 IP address (1 host up) scanned in 5.94 seconds

listen_addresses = '*'

Here is my effective pg_hba.conf:

# TYPE  DATABASE        USER            ADDRESS                 METHOD
local   all             all                                                 trust
host    all             all                 127.0.0.1/32                md5
local   replication     all                                             trust
host    replication     all             127.0.0.1/32                trust
host    replication     all             ::1/128                         trust

host    all             user1            192.168.1.4                 255.255.255.0    md5
host    all             user1            192.168.1.24                255.255.255.0    md5
host    all             user1            192.168.1.0/24              md5
host    all             all                 0.0.0.0/0                        md5

Upon restart/start of the server, it spits this out:

Jul 03 18:07:51 server1.project33.ca postmaster[2321]: 2022-07-03 18:07:51.206 EDT [2321] LOG:  listening on Unix
socket"/var/run/postgresql/.s.PGSQL.5432" 
Jul 03 18:07:51 server1.project33.ca postmaster[2321]: 2022-07-03 18:07:51.213 EDT [2321] LOG:  listening on Unix
socket"/tmp/.s.PGSQL.5432" 

Those directives are the same in the server settings:

unix_socket_directories                | /var/run/postgresql, /tmp           | Sets the directories where Unix-domain
socketswill be created. 
unix_socket_group                      |                                     | Sets the owning group of the Unix-domain
socket.
unix_socket_permissions                | 0777                                | Sets the access permissions of the
Unix-domainsocket. 

tcp_keepalives_count                   | 0                                   | Maximum number of TCP keepalive
retransmits.
tcp_keepalives_idle                    | 0                                   | Time between issuing TCP keepalives.
tcp_keepalives_interval                | 0                                   | Time between TCP keepalive retransmits.
tcp_user_timeout                       | 0                                   | TCP user timeout.

How I can get this to be visible on the LAN and allow me to connect? For some reason TCP sockets aren’t showing up, yet
I’veset listen_addresses to '*'.  I can also ssh into the box, so TCP sockets are running and runctional.  


Cheers, Bee




В списке pgsql-novice по дате отправления:

Предыдущее
От: Bzzzz
Дата:
Сообщение: Re: Info on error `Connection to client lost`
Следующее
От: Tom Lane
Дата:
Сообщение: Re: psql: error: could not connect to server: Connection refused