Conversation

Notices

1. musicman (musicman@nu.federati.net)'s status on Monday, 08-Feb-2021 17:37:10 EST musicman
   #postgres folks, any out-of-the-box thoughts about this error:
   
   psql: error: could not connect to server: could not connect to server: Connection refused
   Is the server running on host "10.14.202.76" and accepting
   TCP/IP connections on port 9999?
   
   Obviously, the firewall has been checked.
   1. lnxw48a1 (lnxw48a1@nu.federati.net)'s status on Monday, 08-Feb-2021 17:53:48 EST lnxw48a1

      in reply to
      If you run `netstat` on the machine with the database, does this port show up as a listening port? Also, #postgresql normally uses port 5432 ... did you change the config to make it use 9999 instead?
      
      Most DBMSs listen only for local connections unless manually configured differently. (No one wants to find out accidentally that their database is accessible to places they didn't intend.) So check your database config.
      
      What happens when you try `telnet 10.14.202.76 9999` (or `telnet 10.14.202.76 5432` as appropriate)?
      1. musicman (musicman@nu.federati.net)'s status on Tuesday, 09-Feb-2021 09:29:59 EST musicman

         in reply to
         the issue is with pgpool, not postgres directly: https://www.pgpool.net/docs/latest/en/html/index.html
         1. musicman (musicman@nu.federati.net)'s status on Tuesday, 09-Feb-2021 11:13:41 EST musicman

            in reply to
            not SELinux on this one machine:
            
            SELinux status: enabled
            SELinuxfs mount: /sys/fs/selinux
            SELinux root directory: /etc/selinux
            Loaded policy name: targeted
            Current mode: permissive
            Mode from config file: permissive
            Policy MLS status: enabled
            Policy deny_unknown status: allowed
            Memory protection checking: actual (secure)
            Max kernel policy version: 31
         2. lnxw48a1 (lnxw48a1@nu.federati.net)'s status on Tuesday, 09-Feb-2021 12:45:18 EST lnxw48a1

            in reply to
            @musicman Ah, hopefully you've tracked it down and proposed a fix.
   2. lnxw48a1 (lnxw48a1@nu.federati.net)'s status on Monday, 08-Feb-2021 17:59:50 EST lnxw48a1

      in reply to
      @musicman https://bigbinary.com/blog/configure-postgresql-to-allow-remote-connection [bigbinary com] Might have some help for you.