-
Notifications
You must be signed in to change notification settings - Fork 405
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Instruction for ec2-automate-backup on Ubuntu 14 server #129
Comments
same problem |
Hi @insiderq I resolved this issue by issues the following command. It is not picking up role permissions assigned to ec2.
You can further debug the issue by outputting them to log file and see what's going on. |
I think the problem is in something different. The output shows me nothing. Program works but does nothing. |
Did you tagged ebs volumes? |
This command works perfectly in shell and really outputs to the log, but when i add it to the crontab it with even * * * * * it seem's to be work, since it empties the log file. |
Same problem here. @insiderq you need to output the error to log file, attach 2>&1 at the end of your cron job. My error output: @jgardezi solution doens't work for me. |
This is my solution, looks like there are a conflict with awscli installed from pip and apt-get, so i removed awscli with apt-get and reinstall with pip.
After this you need to create a link to aws executable:
|
Hi,
I am having issues running ec2-automate-backup.sh as cron Job on Ubuntu 14 server. When I run a command
/home/backup-agent/scripts/ec2-automate-backup.sh -s tag -t Backup,Values=true -k 31 -r ap-southeast-2
on terminal it works fine and I can see it also creates snapshots.The issue is when I try run this as a cron job it does not work. This is my cron command and I am trying to run it on 11pm every day. I have used crontab -e to schedule the cron job.
00 23 * * * /home/backup-agent/scripts/ec2-automate-backup.sh -s tag -t Backup,Values=true -k 31 -r ap-southeast-2
Please let me know what is going on or any steps I am missing i.e. cron-primer.sh?
Kind regards,
Javed Gardezi
The text was updated successfully, but these errors were encountered: