Skip to content
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

added --no-progress to aws s3 commands to create sane log files.... #97

Merged
merged 1 commit into from
Mar 1, 2022

Conversation

TheLastCicada
Copy link
Contributor

added the date to the script output. Couldn't find the --no-progress documented anywhere official, but found it in Github aws/aws-cli#2747 and it works. Instead of 25 MB for one backup job, the log file is now a handful of bytes and we have just as much usable info. Also added some "echo" statements to log what point of the cleanup we are in for when one of those things fails (had some trouble with it in manual testing). This worked for a test run on testnet.

@cmmarslender cmmarslender merged commit b65d834 into main Mar 1, 2022
@cmmarslender cmmarslender deleted the logrotate-backup-logs-debugging branch March 1, 2022 14:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants