wthttp/async: remote_endpoint() threw: remote_endpoint: Socket not connected
Added by Emeric Poupon 6 days ago
Hello,
A user is reporting logs filled with lines like this every 5 seconds, regardless of the site's activity:
[2025-Feb-14 11:29:05.906] 1 - [error] "wthttp/async: remote_endpoint() threw: remote_endpoint: Socket not connected [system:107 at /usr/include/boost/asio/detail/reactive_socket_service.hpp:218 in function 'remote_endpoint']"
[2025-Feb-14 11:29:10.910] 1 - [error] "wthttp/async: remote_endpoint() threw: remote_endpoint: Socket not connected [system:107 at /usr/include/boost/asio/detail/reactive_socket_service.hpp:218 in function 'remote_endpoint']"
[2025-Feb-14 11:29:15.914] 1 - [error] "wthttp/async: remote_endpoint() threw: remote_endpoint: Socket not connected [system:107 at /usr/include/boost/asio/detail/reactive_socket_service.hpp:218 in function 'remote_endpoint']"
[2025-Feb-14 11:29:20.917] 1 - [error] "wthttp/async: remote_endpoint() threw: remote_endpoint: Socket not connected [system:107 at /usr/include/boost/asio/detail/reactive_socket_service.hpp:218 in function 'remote_endpoint']"
[2025-Feb-14 11:29:25.921] 1 - [error] "wthttp/async: remote_endpoint() threw: remote_endpoint: Socket not connected [system:107 at /usr/include/boost/asio/detail/reactive_socket_service.hpp:218 in function 'remote_endpoint']"
[2025-Feb-14 11:29:30.923] 1 - [error] "wthttp/async: remote_endpoint() threw: remote_endpoint: Socket not connected [system:107 at /usr/include/boost/asio/detail/reactive_socket_service.hpp:218 in function 'remote_endpoint']"
Strangely, this doesn't seem to affect their use of the site...
I can't find anything in the code that matches this—does anyone have any leads?
Replies (2)
RE: wthttp/async: remote_endpoint() threw: remote_endpoint: Socket not connected - Added by Matthias Van Ceulebroeck 5 days ago
Hello Emeric,
I don't think that there is anything specifically on a 5 seconds interval that ought to show this behavior. Nor have I seen it before.
Might I inquire a little about their set-up?
Do they run with SSL or not?
Do they have a session timeout configured?
Do they have dedicated sessions enabled?
Does this occur immediately after they restart their application, or does this only start after a while?
RE: wthttp/async: remote_endpoint() threw: remote_endpoint: Socket not connected - Added by Emeric Poupon 4 days ago
Actually you can have some more details there: https://github.com/epoupon/lms/issues/613 (with logs in debug mode)
It seems to appear right after the beginning of the server spawn.
My application is actually using the default vanilla wt_config.xml file.
It is running wt 4.11.1 in an alpine container, manually compiled, see https://github.com/epoupon/lms/blob/dd1a080b7a6dffcd623d19c20518b730a390cc27/Dockerfile-release#L82
And the problem seems to appear only when running this image in an unraid server