pg.ddx.io pgsql-admin@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Steve Crawford <scrawford@pinpointresearch.com>
To: Nirav Parikh <niravp@alliancerecruitment.com.au>
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_dump from crontab
Date: Thu, 10 Aug 2006 12:04:25 -0700
Message-ID: <44DB8339.4030206@pinpointresearch.com> (raw)
In-Reply-To: <221385EC3F18A44DB0925467A1D2395F568D6D@exsrv3.workskillsprofessionals.com.au>
References: <221385EC3F18A44DB0925467A1D2395F568D6D@exsrv3.workskillsprofessionals.com.au>
Nirav Parikh wrote:
> Hi,
>
> I am having problem backing up database from crontab, I got following
> lines in crontab file
>
>
> 0 20 * * 5 /usr/pgsql/bin/pg_dump -F c database >
> /usr/backup/friDATE4.pgdump
> 0 20 * * 4 pg_dump -F c database > /usr/backup/thurDATE06-3.pgdump
>
> none of them works, I have given full permission to everyone in
> /usr/backup directory
>
> it creates the dump file but with 0 size - empty!
>
> I have other commands in crontab which executes normally, also pg_dump
> command works through command line.
>
> does anyone what else I can check?
Is the cron backup process running as the same user as your command-line
version? I am, of course, assuming as well that the command-line success
is on the same machine as the crontab.
Are your startup scripts setting any environment variables that may not
be set when cron runs the job?
Is there anything interesting in the PostgreSQL server log at the time
of your backup attempt?
Does a simple command in crontab succeed in writing to the same
directory (something like * * * * * date >> /usr/backup/crondatetest)?
Try redirecting stderr (add something like 2> ~/pg_dump.err to your
crontab command) and see if any errors are being generated. (Most cron
implementations will send an email if anything is output to stderr or
stdout but this assumes that the crontab user's email is actually routed
to someplace that it will end up being seen.)
Cheers,
Steve
view thread (5+ messages) latest in thread
Message-ID: <44DB8339.4030206@pinpointresearch.com> Permalink: ../44DB8339.4030206@pinpointresearch.com/ Also on: postgresql.org/message-id/44DB8339.4030206@pinpointresearch.com ·
reply
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Reply to all the recipients from your mail client; the link fills in the headers below: reply via email Some clients, webmail especially, drop In-Reply-To and References from a link, and the reply then starts a new thread: use the mbox below. To: pgsql-admin@postgresql.org Cc: scrawford@pinpointresearch.com, niravp@alliancerecruitment.com.au Subject: Re: pg_dump from crontab In-Reply-To: <44DB8339.4030206@pinpointresearch.com> References: <221385EC3F18A44DB0925467A1D2395F568D6D@exsrv3.workskillsprofessionals.com.au> <44DB8339.4030206@pinpointresearch.com> * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox