You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On a fresh install of Ubuntu server (14.04.4), when you install the AWS CLI using pip the executable seems to end up in /usr/local/bin, so when using ec2-automate-backup.sh cron-primer.sh needs to be modified to reflect this; maybe worth adding a comment to this effect?
The text was updated successfully, but these errors were encountered:
I spent a damn load of time trying to resolve this issue. Somehow my script does not catch/execute cron-primer file, even if i specify it with -c /path/to/cron-primer.sh. In addition my command seems to redirect only STDOUT output to log file only and i saw an empty file that pissed me off.
As a final workaround-solution i just used sudo ln -s /usr/local/bin/aws /usr/bin/aws and everything went good.
On a fresh install of Ubuntu server (14.04.4), when you install the AWS CLI using pip the executable seems to end up in /usr/local/bin, so when using ec2-automate-backup.sh cron-primer.sh needs to be modified to reflect this; maybe worth adding a comment to this effect?
The text was updated successfully, but these errors were encountered: