Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fkvQI-0007Uj-M5 for pgsql-admin@arkaria.postgresql.org; Wed, 01 Aug 2018 18:00:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fkvQG-0007Er-BO for pgsql-admin@arkaria.postgresql.org; Wed, 01 Aug 2018 18:00:32 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fkvQG-0007Ek-2P for pgsql-admin@lists.postgresql.org; Wed, 01 Aug 2018 18:00:32 +0000 Received: from mail-oi0-x242.google.com ([2607:f8b0:4003:c06::242]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fkvQC-0004JG-J6 for pgsql-admin@lists.postgresql.org; Wed, 01 Aug 2018 18:00:31 +0000 Received: by mail-oi0-x242.google.com with SMTP id 13-v6so36231055ois.1 for ; Wed, 01 Aug 2018 11:00:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=yOX2bj592TDapVRebcOUoyQabpw3FhXVD9v7YPBhVnc=; b=RPl1c9nmUpvbO7IBH7L2hmYMvRUTTttnL4qk4hJe15e06OJUcofj3ZFZ7x6/Gyum/k mNIjmo1CvUs/HJZbO1qHTJzY48MO54WdIrNuQ92eLPJLzsP8kbnVfnxXSq3XChmiDGQL FhCt+lIKhlFfH+XAn8rWSeODEil9QRMsQxZ9S+CkRlwttymh2SJBKBhu6Y8uK0jUF+fz R5NZJJVBeCoPEHvDho5Hq3VskyQ7RFetGML0pqU0luLpI0+kQfPQwD1DPcQsd9E3BWAA c/YXW+yURgQX4AEzMImFmJYtQ0S/8P6xpPdcNzOkZbmx+TJx/WrwGpexb/byEkMcUmGh 1N4w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=yOX2bj592TDapVRebcOUoyQabpw3FhXVD9v7YPBhVnc=; b=NSd2BOukwfVx/NMMYOiE/dm/WPlq0UMKmS7oMO2Zt68699jObcrNS0LkvPBJtYWDrJ oITl9mav6oCpiZCeY2PiOjojPNlFQ4jimZR55/VFK4CN5yX5u5/NSv7m+ZFsL1I7t6Vp 1PkQ5H9PWW/02fobNth14V+u7R5YEWQV3Bjtk+/N/ZGLe6mv6c8l4erMdbtoyF9jTTyC JmDK2jccU5mns7w/kBQAs7jBwNPvYEAGbBZFCjd6P8mavi6DxVHZcZIdp5VbamaDejmz bZ0pk99VPOyKU2cDnRK5xPPRQeQmMm3fV5IKUf9TrlrfmlOARjIVSwEGU7PdiaqmCBd4 nU7Q== X-Gm-Message-State: AOUpUlG+xJHWP6bYuxXL1APNwNvcbze3CVtpugCbJsnXjn3z3PSOF3cF IoHmqHo5j74vXzImzUNRm9WfA8tq X-Google-Smtp-Source: AAOMgpcisAox2/lLzdj8AOW74gAT0RNV3YRjI0/r+WAXml9CroqoYFfO9O+97cGZ4f0h8wy8oF5HAw== X-Received: by 2002:aca:100f:: with SMTP id 15-v6mr4872083oiq.110.1533146426381; Wed, 01 Aug 2018 11:00:26 -0700 (PDT) Received: from [192.168.1.10] (ip70-171-116-89.no.no.cox.net. [70.171.116.89]) by smtp.googlemail.com with ESMTPSA id j193-v6sm11650414oih.55.2018.08.01.11.00.25 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Aug 2018 11:00:25 -0700 (PDT) Subject: Re: postgres port 5434 not being allowed when remote server is accessing To: pgsql-admin@lists.postgresql.org References: From: Ron Message-ID: Date: Wed, 1 Aug 2018 13:00:24 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------9E1CDCAFD92E45B34D9AFFBD" Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --------------9E1CDCAFD92E45B34D9AFFBD Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit nmap to the rescue!!! It's a go-to tool in cases like this. On 08/01/2018 12:17 PM, Mark Steben wrote: > No error - the connection attempt just spins until the attempt times out. > I now suspect a firewall issue and have reached out to our IT team to > investigate. > > Thank you, > > On Wed, Aug 1, 2018 at 1:10 PM, Mariel Cherkassky > > wrote: > > Hi, what error do you get? > > > On Wed, Aug 1, 2018, 8:05 PM Mark Steben > > > wrote: > > Hi Arlindo - yes hot_standby is turned on for that server.  Thanks > for quick response. > > On Wed, Aug 1, 2018 at 12:26 PM, Arlindo Neto > wrote: > > Hello Mark, > > Have you checked the hot_standby parameter? It must be ON so > you can run queries on a standby. > > Regards, >     Arlindo Neto. > > Em qua, 1 de ago de 2018 às 13:22, Mark Steben > > escreveu: > > Good morning, > > We run postgres 9.4.8 on our GNU linux standby server. We > run 3 instances receiving data there: >    1. a slony instance - port 5432 >    2. standby instance 1 - port 5433 >    3.  standby instance 2 - port 5434 > > We run connection strings in another GNU linux server to > access the data on our standby server. > >   We can access  the postgres instances on port 5432 and > port 5433 but not port 5434. > > All the instances are up and running on the standby > server.  Any insights as to why 5434 does not work? > > -- Angular momentum makes the world go 'round. --------------9E1CDCAFD92E45B34D9AFFBD Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit nmap to the rescue!!!

It's a go-to tool in cases like this.

On 08/01/2018 12:17 PM, Mark Steben wrote:
No error - the connection attempt just spins until the attempt times out.
I now suspect a firewall issue and have reached out to our IT team to investigate.

Thank you,

On Wed, Aug 1, 2018 at 1:10 PM, Mariel Cherkassky <mariel.cherkassky@gmail.com> wrote:
Hi, what error do you get?


On Wed, Aug 1, 2018, 8:05 PM Mark Steben <mark.steben@drivedominion.com> wrote:
Hi Arlindo - yes hot_standby is turned on for that server.  Thanks for quick response.

On Wed, Aug 1, 2018 at 12:26 PM, Arlindo Neto <neto.acs@gmail.com> wrote:
Hello Mark,

Have you checked the hot_standby parameter? It must be ON so you can run queries on a standby.

Regards,
    Arlindo Neto.

Em qua, 1 de ago de 2018 às 13:22, Mark Steben <mark.steben@drivedominion.com> escreveu:
Good morning,

We run postgres 9.4.8 on our GNU linux standby server.  We run 3 instances receiving data there:
   1. a slony instance - port 5432
   2. standby instance 1 - port 5433
   3.  standby instance 2 - port 5434

We run connection strings in another GNU linux server to access the data on our standby server.

  We can access  the postgres instances on port 5432 and port 5433 but not port 5434.

All the instances are up and running on the standby server.  Any insights as to why 5434 does not work?



--
Angular momentum makes the world go 'round.
--------------9E1CDCAFD92E45B34D9AFFBD--