-
Notifications
You must be signed in to change notification settings - Fork 10
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
ssl.SSLEOFError when using HTTPS #439
Comments
Investigation shows that these exceptions are printed in the request handler threads run by the WSGIServer, at https://github.com/python/cpython/blob/main/Lib/wsgiref/handlers.py#L382:
This means it is just a somewhat crude way of logging the error, and otherwise an error response is sent back to the web client (i.e. Prometheus, or web browser), who can retry (?). Specifically, neither the WSGIServer thread inside of the zhmc exporter process, nor the zhmc exporter process are terminated. In fact, it seems to me that at some level within the WSGIServer, a retry happens, because when I inject the raising of an When I inject the exception as close as possible to where it is originally raised, the WSGIServer retries. This is when adding the following code:
at the begin of @Charles1000Chen |
With some debug code added, the output with the injected SSLEOFError looks like this:
and the web browser properly displays the metrics page. |
Another occurrence using the exporter code of the upcoming version 2.0.0 (as of PR #605) on Python 3.12 with stomp-py 8.1.2, and the config file for M12:
The exporter was still functional after this. Logging was off when this happened. |
Occasionally, the exporter fails with this traceback:
This happened in the L&M team when using version 1.5.0b3, which already had the exception handling around
start_http_server()
so we know now that it is not raised in that function, but in the HTTP server thread.See also issue #397 for the earlier occurrence of this error.
The text was updated successfully, but these errors were encountered: