Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Unable to download RDS log files that contain binary data #2400

Closed
andybeak opened this issue Jan 20, 2017 · 4 comments
Closed

Unable to download RDS log files that contain binary data #2400

andybeak opened this issue Jan 20, 2017 · 4 comments
Labels
closing-soon This issue will automatically close in 4 days unless further comments are made. guidance Question that needs advice or information. service-api This issue is due to a problem in a service API, not the SDK implementation.

Comments

@andybeak
Copy link

When using aws rds download-db-log-file-portion if the log file contains binary data you get the error message "An error occurred (InvalidParameterValue) when calling the DownloadDBLogFilePortion operation: This file contains binary data and should be downloaded instead of viewed."

@kyleknap
Copy link
Contributor

This looks like an error coming from the service. The CLI is just a wrapper over the API. So it is just creating an HTTP request based on parameters provided and parsing/displaying the resulting HTTP response. The CLI in this case is just propagating the error from the service.

So unfortunately, there is not much that can be done from the CLI codebase. I did a quick search of other people who ran into this issue and found this thread: https://forums.aws.amazon.com/thread.jspa?threadID=144248. So that may be of some use. If it is not, I would recommend reaching out on the AWS Developer Forums to see if there are any workarounds.

@kyleknap kyleknap added closing-soon This issue will automatically close in 4 days unless further comments are made. move-to-forums labels Jan 23, 2017
@andybeak
Copy link
Author

Hi,

Yeah I also came to that conclusion. I decided on using mysqlbinlog to download them (here's a gist I made).

The problem with this workaround is that the user/pass is in the script. Even having them in an environment variable is not great.

@andybeak andybeak reopened this Jan 25, 2017
@bdobberteen
Copy link

+1

@JordonPhillips
Copy link
Member

Support is probably the best avenue for getting help here, but since there's nothing we can do about the issue I'm closing it out.

@diehlaws diehlaws added guidance Question that needs advice or information. service-api This issue is due to a problem in a service API, not the SDK implementation. and removed api-question labels Jan 4, 2019
thoward-godaddy pushed a commit to thoward-godaddy/aws-cli that referenced this issue Feb 12, 2022
…#2400)

* Revert "chore: Enable pylint compare to zero/empty string"

This reverts commit 1e3b282d1c83536c68dc0b754e74832f3af6dd49.

* Revert "chore: Enable pylint Else If Used checker"

This reverts commit 5819dedf38800522e587987345866c8ceb4d3aca.

* Revert "chore: Remove unnecessary pylint disable"

This reverts commit d4a5c46f159bd690375a01526e74b73497723ddc.

* Revert "chore: Enable pylint line too long"

This reverts commit fb54504124cf04f163189ed8d02be4fc9663dd16.

* Revert "chore: Enable pylint multi-processes"

This reverts commit b02c8d94c942395fb1b7d27c00d0328c373956d6.

* Revert "chore: Enable pylint rule Unused import"

This reverts commit a6eda1d68cd627b73eba3f558b30f74a3863ab84.

* Revert "chore: Remove pylint rules that do not apply for python 3"

This reverts commit 62120054ea79b5aa25f03a1924640c8ecc77ce68.

* Revert "chore: Make pylintrc ignore rule more readable"

This reverts commit fe503854829fe316b76a6123aeff98298174e1c2.
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
closing-soon This issue will automatically close in 4 days unless further comments are made. guidance Question that needs advice or information. service-api This issue is due to a problem in a service API, not the SDK implementation.
Projects
None yet
Development

No branches or pull requests

5 participants