Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1i5s6Z-0003Yt-9z for pgsql-admin@arkaria.postgresql.org; Thu, 05 Sep 2019 13:47:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1i5s6Y-0007XQ-5M for pgsql-admin@arkaria.postgresql.org; Thu, 05 Sep 2019 13:47:18 +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_SHA1:256) (Exim 4.89) (envelope-from ) id 1i5s6X-0007XJ-SJ for pgsql-admin@lists.postgresql.org; Thu, 05 Sep 2019 13:47:17 +0000 Received: from imx6.etecsa.cu ([200.55.152.141]) by magus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1i5s6U-00014n-7f for pgsql-admin@lists.postgresql.org; Thu, 05 Sep 2019 13:47:17 +0000 Received: from mail.etecsa.cu (unknown [192.168.91.10]) by imx6.etecsa.cu (Postfix) with ESMTP id D4108101; Thu, 5 Sep 2019 09:47:08 -0400 (CDT) Received: from webmailrc.etecsa.cu (unknown [192.168.97.37]) (Authenticated sender: gilberto.castillo) by mail.etecsa.cu (Postfix) with ESMTPA id D1DF83294467; Thu, 5 Sep 2019 09:47:08 -0400 (CDT) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Thu, 05 Sep 2019 09:47:08 -0400 From: gilberto.castillo@etecsa.cu To: mallikarjun t Cc: Luca Ferrari , soumitra bhandary , Pgsql-admin Subject: Re: [MASSMAIL]Re: Streaming replication issue In-Reply-To: References: <348e59259ebb469677de80c8b4864a07@etecsa.cu> Message-ID: X-Sender: gilberto.castillo@etecsa.cu User-Agent: Roundcube Webmail/1.2.5 X-KLMS-Rule-ID: 1 X-KLMS-Message-Action: clean X-KLMS-AntiSpam-Lua-Profiles: 144635 [Sep 05 2019] X-KLMS-AntiSpam-Version: 5.8.6.0 X-KLMS-AntiSpam-Envelope-From: gilberto.castillo@etecsa.cu X-KLMS-AntiSpam-Rate: 0 X-KLMS-AntiSpam-Status: not_detected X-KLMS-AntiSpam-Method: none X-KLMS-AntiSpam-Info: LuaCore: 315 315 bf779a3ab660ae84781ee7b895e349b8788eb866, Auth:dkim=none X-KLMS-AntiSpam-Interceptor-Info: scan successful X-KLMS-AntiPhishing: Clean, 2019/07/09 11:58:30 X-KLMS-AntiVirus: Kaspersky Security 8.0 for Linux Mail Server, version 8.0.1.721, bases: 2019/09/05 06:13:00 #10407260 X-KLMS-AntiVirus-Status: Clean, skipped List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk El 2019-09-05 09:39, mallikarjun t escribió: > Dear Gilberto, > > ./psql -p 5444 -d edb -U enterprisedb this one is accessing the EDB > Advanced Server by using this command. > Iam already checked the logs role "postgres" is not a login permission > error message is there. Do you check it? /opt/edb/as9.6/bin/pg_ctl -p 5444 -D /home/postgres/data_96 start > > Regards, > Malli. > > On Thu, Sep 5, 2019 at 6:35 PM wrote: > >> Hello, >> >> Please, you could check postgresql.log >> or What is this : ./psql -p 5444 -d edb -U enterprisedb.? >> >> El 2019-09-05 08:45, mallikarjun t escribió: >>> Dear All, >>> >>> Before streaming replication I will access EDB Advanced Server >> below >>> command by using psql >>> >>> ./psql -p 5444 -d edb -U enterprisedb. >>> >>> I am happily working. >>> >>> When I am starting replication process stop the server and take >> the >>> basebackup of PostgreSQL Community version and start the new >> cluster. >>> >>> for example >>> >>> /opt/edb/as9.6/bin/pg_basebackup -D /home/postgres/data_96 -h >>> -p 5432 -X stream -R >>> >>> I am taking basebackup then after recovery.conf file I include >>> trigger_file ='/tmp/primary_down', >>> >>> If my master is down unexpectedly, I will promote my Slave to >> Master. >>> >>> the after I start the server by using following commnad >>> >>> /opt/edb/as9.6/bin/pg_ctl -D /home/postgres/data_96 start >>> >>> server started and wal receiver is working properly, but real >> problem >>> is happens here only, >>> >>> I want connect to sever by using following command >>> /opt/edb/as9.6/bin/psql >>> >>> role "postgres" not a log in permission error message I am >> getting , >>> I am try to put port number along with that >>> error: could not connect to the server, locally running this port >>> number 5432. >>> >>> this is the error message I am getting. >>> >>> Regards, >>> Malli. >>> >>> On Thu, Sep 5, 2019 at 5:58 PM Luca Ferrari >>> wrote: >>> >>>> On Thu, Sep 5, 2019 at 1:54 PM mallikarjun t >> >>>> wrote: >>>>> I tried these two compatibilities I will get the same issue. >>>> >>>> According to the installation guide available at >>>> >>> >> > >>>> the database to connect to is 'edb' with user 'enterprisedb'. >>>> So does >>>> psql -U enterprisedb edb >>>> allow you to connect to your cluster? >>>> >>>> Luca