Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TftqV-0002uZ-CZ for pgsql-admin@arkaria.postgresql.org; Tue, 04 Dec 2012 14:51:39 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1TftqU-0003H4-HC for pgsql-admin@arkaria.postgresql.org; Tue, 04 Dec 2012 14:51:38 +0000 Received: from magus.postgresql.org ([87.238.57.229]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TftqT-0003Gz-Rz for pgsql-admin@postgresql.org; Tue, 04 Dec 2012 14:51:37 +0000 Received: from smtp172.iad.emailsrvr.com ([207.97.245.172]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TftqR-0005VZ-Ey for pgsql-admin@postgresql.org; Tue, 04 Dec 2012 14:51:37 +0000 Received: from smtp37.relay.iad1a.emailsrvr.com (localhost.localdomain [127.0.0.1]) by smtp37.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id 5CD353B0259; Tue, 4 Dec 2012 09:51:33 -0500 (EST) X-SMTPDoctor-Processed: csmtpprox 2.7.4 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp37.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id 573883B022D; Tue, 4 Dec 2012 09:51:33 -0500 (EST) X-Virus-Scanned: OK Received: by smtp37.relay.iad1a.emailsrvr.com (Authenticated sender: spike-AT-ticketevolution.com) with ESMTPSA id 30AC03B01DD; Tue, 4 Dec 2012 09:51:33 -0500 (EST) Subject: Re: Cronjob to autobackup database Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Spike Grobstein In-Reply-To: <1354583597299-5734873.post@n5.nabble.com> Date: Tue, 4 Dec 2012 09:51:32 -0500 Cc: pgsql-admin@postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: <4422292F-040B-4DE8-AA2A-2A5F1C201B65@ticketevolution.com> References: <1354583597299-5734873.post@n5.nabble.com> To: teyking2003 X-Mailer: Apple Mail (2.1283) X-Pg-Spam-Score: -0.8 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org You can debug what's going wrong with the script by adding this: 30 09 * * * /autopgdump.sh &> /autopgdump.log that will write the output of the command to a logfile living at /autopgdum= p.log. If there's anything wrong with your environment (something not in th= e PATH of the user running the cron, etc) it should be written there. Cron = runs with a slightly different environment than a regular login shell, so t= his can help you figure out exactly what's going wrong. note: each time cron executes that script, it will replace the contents of = /autopgdump.log; not append to it. Also, just to double check, the above configuration would run the script at= 9:30am every day, so did you wait until 9:30 for the script to run? ...spike On Dec 3, 2012, at 8:13 PM, teyking2003 wrote: > i have a cronjob setting up as below > 1)Command crontab -e=20 > 2)Keyin 30 09 * * * /autopgdump.sh > 3) Save to new crontab file. > but nothing happen, the backup process won't start. >=20 > i manage to perform manual backup by running the following command > sudo ./autopgdump.sh( SH file store under root directory >=20 > looking for the correct ways to setting up the cronjob. >=20 > thanks >=20 >=20 >=20 > -- > View this message in context: http://postgresql.1045698.n5.nabble.com/Cro= njob-to-autobackup-database-tp5734873.html > Sent from the PostgreSQL - admin mailing list archive at Nabble.com. >=20 >=20 > --=20 > Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin --=20 Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin