Linode Forum
Linode Community Forums
 FAQFAQ    SearchSearch    MembersMembers      Register Register 
 LoginLogin [ Anonymous ] 
Post new topic  Reply to topic
Author Message
 Post subject: Rdiff backup problems
PostPosted: Mon Aug 01, 2005 7:17 pm 
Offline
Junior Member

Joined: Fri Dec 24, 2004 7:57 pm
Posts: 25
Website: http://www.rrijkse.com
WLM: robbert@rrijkse.com
AOL: robbertrijkse
Location: Toronto, Canada
I used the rdiff backup solution described on the Linode Wiki

http://www.linode.com/wiki/index.php/AutomatedRdiffBackup

It all works fine except for the daily cron run. I get this output from cron, however when I run the script from the command line, it works just fine.
Can anyone tell me what's going on.

Output from cron:
/etc/cron.daily/backup-rdiff:
run-parts: failed to exec /etc/cron.daily/backup-rdiff: Exec format error
run-parts: /etc/cron.daily/backup-rdiff exited with return code 1

The script I used is the exact same script that is on the wiki.

Thanks for any help

- Robbert


Top
   
 Post subject:
PostPosted: Mon Aug 01, 2005 7:32 pm 
Offline
Linode Staff
User avatar

Joined: Fri Oct 17, 2003 12:38 am
Posts: 287
Location: Dr Wierd's Lab, South Jersey Shore
Try adding "set -x" as the first line after "#!/bin/sh" in the shell script. This will output tracing information.

Michael


Top
   
 Post subject: Nothing changed.
PostPosted: Tue Aug 02, 2005 9:52 am 
Offline
Junior Member

Joined: Fri Dec 24, 2004 7:57 pm
Posts: 25
Website: http://www.rrijkse.com
WLM: robbert@rrijkse.com
AOL: robbertrijkse
Location: Toronto, Canada
I put in the line, and it still outputs the exact same error message

- Robbert


Top
   
 Post subject: Re: Nothing changed.
PostPosted: Tue Aug 02, 2005 1:21 pm 
Offline
Senior Member

Joined: Thu Aug 28, 2003 12:57 am
Posts: 273
rrijkse wrote:
I put in the line, and it still outputs the exact same error message

- Robbert


Did you ensure that they script is executable, using "chmod +x <thescript>"?

Are you sure that the first line of your script is #!/bin/sh or whatever it is supposed to be (I haven't even read the script in question), and with no extra characters at all (aside from the -x that you may have added for diagnostic purposes)?

Have you tried running the script by hand, not from cron, just running it using the same exact command as you have in your crontab file? If so, what happens?


Top
   
 Post subject: My mistake
PostPosted: Tue Aug 02, 2005 2:15 pm 
Offline
Junior Member

Joined: Fri Dec 24, 2004 7:57 pm
Posts: 25
Website: http://www.rrijkse.com
WLM: robbert@rrijkse.com
AOL: robbertrijkse
Location: Toronto, Canada
I had a space on the line that had: #!/bin/sh

I tested it and it worked, and the weird part was that when I ran in manually it worked.

Anyway, thanks a lot,

Robbert


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  
RSS

Powered by phpBB® Forum Software © phpBB Group