Public bug reported:
For example if DNS lookup fails, s3cmd 1.1.0 version will erroneusly
exit with exit code 0 after series of backoffs. This is very serious as
s3cmd is often used for taking automated backups to s3; there are
countless blog articles and even the book "Resilience and Reliability on
AWS" recommending that it be used for archiving the WAL logs of
PostgreSQL; now a transient DNS failure for one reason or another would
mean that the rolling backups are completely unusable. (Yes, this
happened to us).
For example, open resolv.conf, comment out all dns server lines, save
the file, execute
s3cmd put y s3://foo/bar ; echo $?
After series of backoffs, the s3cmd exits with success exit code (see
the attachment)
Funnily enough, for example s3cmd ls correctly exits with exit code = 1
on such errors.
** Affects: s3cmd (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "the behaviour on DNS failure"
https://bugs.launchpad.net/bugs/1449530/+attachment/4386592/+files/output.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1449530
Title:
s3cmd 1.1.0 fails a put operation with zero exit code on DNS resolve
errors
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/s3cmd/+bug/1449530/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
