Actions
Bug #26958
closedssh/session: webrick tries to use closed socket after hijacking
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Description
Webrick does not fully support socket hijacking, so we pry the socket from its hands with some trickery. However, once the session is done, webrick will try to use the hijacked socket, which is now closed. This results in errors, which are logged and then ignored.
We should prevent these errors from happening, if just to keep them out of the log. They don't seem to cause any harm, but the log should be kept clean from noise.
Updated by The Foreman Bot over 5 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/smart_proxy_remote_execution_ssh/pull/41 added
Updated by Anonymous over 5 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman_proxy_plugin|a72da5eee99b3992559303acc0f41dfe4f3bf6e7.
Updated by Adam Ruzicka almost 5 years ago
- Fixed in Releases smart_proxy_remote_execution_ssh-0.3.0 added
Actions