Re: trouble with pg_dumpall - Mailing list pgsql-admin
From | Tena Sakai |
---|---|
Subject | Re: trouble with pg_dumpall |
Date | |
Msg-id | FE44E0D7EAD2ED4BB2165071DB8E328C0378F0E5@egcrc-ex01.egcrc.org Whole thread Raw |
In response to | Re: trouble with pg_dumpall ("Phillip Smith" <phillip.smith@weatherbeeta.com.au>) |
List | pgsql-admin |
Yeeeeha!
That did, Jeff! Fantastic!
*:5432:canon:postgres:winkwink <- no good
*:5432:*:postgres:winkwink <- works!
Many thanks to Jeff and everybody else who
stayed with me to see the end of this saga.
I appreciate it wholeheartedly.
Regards,
Tena Sakai
tsakai@gallo.ucsf.edu
-----Original Message-----
From: Jeff Frost [mailto:jeff@frostconsultingllc.com]
Sent: Wed 2/27/2008 8:45 PM
To: Tena Sakai
Cc: pgsql-admin@postgresql.org
Subject: RE: [ADMIN] trouble with pg_dumpall
On Wed, 27 Feb 2008, Tena Sakai wrote:
> Hi Jeff,
>
>> What does your .pgpass look like?
> *:5432:canon:postgres:winkwink
There's the problem. That says, any host, port 5432, canon database, postgres
user, password. But pg_dumpall needs to connect to all the databases
including template1 and postgres DBs. Change the 'canon' to '*' and I bet it
will be fine.
>
>> What OS user are you running the cron job as?
> User postgres.
>
>> Do you have SELINUX enabled?
> I have no idea what SELINUX is.
cat /etc/selinux/config
>
>> Can you run the script with the strace command
>> I sent in a previous email so that we can see
>> what's really going on?
> Yes, it is running and I expect it to go for another
> 10 to 15 minutes. I will get your the result asap.
>
> Thank you for your invariable assistance.
> I am getting excited.
>
> Regards,
>
> Tena Sakai
> tsakai@gallo.ucsf.edu
>
>
> -----Original Message-----
> From: Jeff Frost [mailto:jeff@frostconsultingllc.com]
> Sent: Wed 2/27/2008 8:32 PM
> To: Tena Sakai
> Cc: pgsql-admin@postgresql.org
> Subject: RE: [ADMIN] trouble with pg_dumpall
>
> On Wed, 27 Feb 2008, Tena Sakai wrote:
>
>> Hi Jeff,
>>
>> You cuaght me with a fine point.
>>
>>> but I didn't see HOME being exported.
>>
>> I have changed the script accordingly:
>>
>> And the result/my claim remains the same as before:
>>
>> pg_dumpall: could not connect to database "template1": fe_sendauth: no password supplied
>>
>> I see just one more option. Namely, to change the
>> postgres user entry for pg_hba.conf to "trust" for
>> a short period as pg_dumpall starts and then put it
>> back to the way normally is (md5). I would rather
>> not do that and get .pgpass or PGPASSFILE to work
>> for me.
>
> I didn't really expect that to make a difference. What does your .pgpass look
> like? What OS user are you running the cron job as? Do you have SELINUX
> enabled? Can you run the script with the strace command I sent in a previous
> email so that we can see what's really going on?
>
>
--
Jeff Frost, Owner <jeff@frostconsultingllc.com>
Frost Consulting, LLC http://www.frostconsultingllc.com/
Phone: 650-780-7908 FAX: 650-649-1954
pgsql-admin by date: