If you run the cron job under the root account it works fine. I guess when running it under the cPanel account, it doesn’t have enough access to run curl (hey - I told you I was a noob).

This solution rocks!

It works fine from the command line via SSH running as root, but not via cron when it is presumably running under my cpanel account (iotaco in this case). This is the error I get emailed to me when the cron job runs:

…
/home/iotaco/backup/sql/20081107-iotaco_wceet.sql
which: no curl in (/usr/bin:/bin)
s3-put: Environment Error: curl not found on the path or not executable
…

So it works normally until it has to run curl in s3-put. I can confirm that curl is in the /usr/bin so not sure what is going wrong here.

I am a complete Linux noob so hoping somebody can give me some ideas to get this working!!

Here is my cron command:

0 0 * * * sh /home/iotaco/backup/de-website-backup-public.sh

BTW, I found I had to tweak the backup script to get this far, i.e. remove blank lines and modify the code to get multiple databases working, i.e.

$mysqldumpcmd $userpassword $dumpoptions ${database} > ${backupdir}/sql/${DOW}-${database}.sql

Before I changed the above line it wouldn’t work for multiple databases, now it does

Please help!

rm -rf /tmp/s3-*

If your environment uses a TMP folder located in your user home folder (ie: ~/tmp) the .sh file does not need to modified.

If you don’t confirm this you will leave sensitive files in your TMP folder which may be compromised.

Another side effect is the script will not run successfully on the same host because the folders already exist.

Lastly, for multiple sites on a single host you should cron them sufficiently far apart to avoid concurrency problems with the TMP files.

@themandril: look under “Download Here” which has a non-hyperlinked URL to the download; it begins with https://.

You’ll need the s3-bash scripts which can be found by clicking the “s3-bash” link next to “References” at the bottom of the post.

Lastly, the s3.key file cannot contain any trailing characters such as newline. If so, the s3-bash scripts will die (with an appropriate error displayed at the console).

As suggested by the author test via SSH to ensure the script is working properly.