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
AWS lib is verbose when using S3 #21898
Comments
Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks. |
Updated. |
Yeah we disabled the logs completely because it was logging way too much and so we are loosing all the logging purpose now because "good" logs are being lost in false positive. thank you. |
Any update on this? |
I am getting this : 😢
Actually, more than 500 of these. 🤕 Can anybody let me know how do I disable this log (Only this, if possible)? or a possible workaround for this? Thanks. |
This issue seems to be quite stale by now, but the problem still persists, at least for me. Has there been any kind of fix yet? |
@prameshbajra As a workaround, I just filter these messages with python train.py 2>&1 | grep -v "Connection has been released. Continuing." |
See also tensorflow/serving#789 |
Closing this issue since the PR has been merged. Thanks! |
The solution here is to set the logging level for AWS, taken from the PR which has been merged, this worked in 1.14 for me:
|
I use TF_CPP_MIN_LOG_LEVEL=3 and it works too but the above solution seems a better way to do. |
Hi, |
I'm using latest version of Tensorflow with AWS S3 as a backend for models and I have those annoying logs:
[tensorflow-server-pr-14-585f869b5f-2wln8] 2018-08-27 13:51:41.183378: I external/org_tensorflow/tensorflow/core/platform/s3/aws_logging.cc:54] Found secret key
[tensorflow-server-pr-14-585f869b5f-2wln8] 2018-08-27 13:51:41.183471: I external/org_tensorflow/tensorflow/core/platform/s3/aws_logging.cc:54] Connection has been released. Continuing.
[tensorflow-server-pr-14-585f869b5f-2wln8] 2018-08-27 13:51:41.194855: I external/org_tensorflow/tensorflow/core/platform/s3/aws_logging.cc:54] Found secret key
[tensorflow-server-pr-14-585f869b5f-2wln8] 2018-08-27 13:51:41.194963: I external/org_tensorflow/tensorflow/core/platform/s3/aws_logging.cc:54] Connection has been released. Continuing.
[tensorflow-server-pr-14-585f869b5f-2wln8] 2018-08-27 13:51:41.206484: I external/org_tensorflow/tensorflow/core/platform/s3/aws_logging.cc:54] Found secret key
[tensorflow-server-pr-14-585f869b5f-2wln8] 2018-08-27 13:51:41.206714: I external/org_tensorflow/tensorflow/core/platform/s3/aws_logging.cc:54] Connection has been released. Continuing.
[tensorflow-server-pr-14-585f869b5f-2wln8] 2018-08-27 13:51:41.212817: E external/org_tensorflow/tensorflow/core/platform/s3/aws_logging.cc:60] No response body. Response code: 404
[tensorflow-server-pr-14-585f869b5f-2wln8] 2018-08-27 13:51:41.212852: W external/org_tensorflow/tensorflow/core/platform/s3/aws_logging.cc:57] If the signature check failed. This could be because of a time skew. Attempting to adjust the signer.
The server is working as expected though. I set the log level to ERROR only but still the 404 error is happening more than every second.
I saw that there is an issue open in
tensorflow/serving
but this seems to be core/3rd party issue.tensorflow/serving#615
Have I written custom code: No
OS Platform and Distribution: Kubernetes 1.8 running on CENTOS
TensorFlow installed from: Docker image tensorflow/serving:1.10.1
TensorFlow version: 1.10.1
Bazel version: ??
CUDA/cuDNN version: N/A
GPU model and memory: N/A
Exact command to reproduce:
Example of model_config_file:
Mobile device: None
Thank you
The text was updated successfully, but these errors were encountered: