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 1gyk48-0004Y3-8P for pgsql-admin@arkaria.postgresql.org; Tue, 26 Feb 2019 21:15:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gyk46-0007Om-Ol for pgsql-admin@arkaria.postgresql.org; Tue, 26 Feb 2019 21:15:02 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gyk46-0007OQ-Du for pgsql-admin@lists.postgresql.org; Tue, 26 Feb 2019 21:15:02 +0000 Received: from imx6.etecsa.cu ([200.55.152.141]) by makus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gyk43-00071J-9O for pgsql-admin@lists.postgresql.org; Tue, 26 Feb 2019 21:15:01 +0000 Received: from mail.etecsa.cu (unknown [192.168.91.10]) by imx6.etecsa.cu (Postfix) with ESMTP id D41BEBC; Tue, 26 Feb 2019 16:14:55 -0500 (CST) Received: from webmailrc.etecsa.cu (unknown [192.168.97.37]) (Authenticated sender: gilberto.castillo) by mail.etecsa.cu (Postfix) with ESMTPA id CD2203294450; Tue, 26 Feb 2019 16:14:55 -0500 (CST) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Tue, 26 Feb 2019 16:14:55 -0500 From: gilberto.castillo@etecsa.cu To: Pepe TD Vo Cc: Steve Crawford , Shreeyansh Dba , Pgsql-admin Subject: Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL In-Reply-To: <1259407684.5772133.1551215389418@mail.yahoo.com> References: <1766891885.5546566.1551195368839.ref@mail.yahoo.com> <1766891885.5546566.1551195368839@mail.yahoo.com> <1161831433.5624889.1551203198375@mail.yahoo.com> <713147705.5704638.1551207564863@mail.yahoo.com> <1259407684.5772133.1551215389418@mail.yahoo.com> 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: 136248 [Feb 26 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: 236 236 6084fb9491110ca2901942eb14874f7e6341a62a, Auth:dkim=none X-KLMS-AntiSpam-Interceptor-Info: scan successful X-KLMS-AntiPhishing: Clean, 2019/02/22 13:40:30 X-KLMS-AntiVirus: Kaspersky Security 8.0 for Linux Mail Server, version 8.0.1.721, bases: 2019/02/26 11:04:00 #9315798 X-KLMS-AntiVirus-Status: Clean, skipped List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Is possible that postgres it is running for other port? Check!! El 2019-02-26 16:09, Pepe TD Vo escribió: > I typo PORT without = > > yes, I did reload postgres after make a configuration change. > > v/r, > > Bach-Nga > > No one in this world is pure and perfect. If you avoid people for > their mistakes you will be alone. So judge less, love and forgive > more. > To call him a dog hardly seems to do him justice though in as much as > he had four legs, a tail, and barked, I admit he was, to all outward > appearances. But to those who knew him well, he was a perfect > gentleman (Hermione Gingold) > **Live simply **Love generously **Care deeply **Speak kindly. > *** Genuinely rich *** Faithful talent *** Sharing success > > On Tuesday, February 26, 2019 3:55 PM, Steve Crawford > wrote: > > Some random observations that may or may not be of use. > > Are you making sure to reload PostgreSQL whenever you make a config > change? > >> I also found pg_hba.conf on both folders >> /var/lib/pgsql/11/data/pg_hba.conf & >> /var/lib/pgsql/data/pg_hba.conf). I modified it as above and the >> script is not working even run from the command prompt. > > To find out which pg_hba.conf file your running database is using run: > > show all; > > Then search for hba_file or view directly by: > > select setting from pg_settings where name = 'hba_file'; > > You can verify your pg_hba.conf settings with (as user postgres): > > select * from pg_hba_file_rules ; > >> # export HOSTNAME=hostname >> >> # export USERNAME=postgres >> # export DATABASE=postgres >> # export PORT 5432 >> # pg_dump -v -p $PORT -U $USERNAME -d $DATABASE -f >> /tmp/postgresbakup.sql > > Looks like you are missing the "=" between PORT and 5432 > > Cheers, > Steve