Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[BUG] No Error when S3 access key is not available / got deleted
See original GitHub issueContext In order to help us troubleshoot issues with this project, you must provide the following details:
- ElasticDump version: docker.io/elasticdump/elasticsearch-dump:v6.72.0
Describe the bug A clear and concise description of what the bug is.
During operations the access token to the S3 bucket got deleted, elasticsearch-dump only reported an error but did not exit with an error code.
Thu, 09 Sep 2021 05:40:42 GMT | Error Emitted => Access Key you provided does not exist in our records.
Current behavior
Elasticsearch-dump just continues to run, without reporting any errors.
Expected behavior
Elasticsearch-dump should immediatly exit with an error code.
Additional context
We run elasticsearch-dump on an openshift-cluster as a cronjob, so we need a reliable error handling.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Fixed by https://github.com/elasticsearch-dump/elasticsearch-dump/commit/2c5e435770fdd32361a7e71735623ae340d69581
Will be in the next release
Perfect, thank you very much 😄