Incorrect error code/string (ENOSTR)

[ant5]

I've encountered many more than few errors which seems related to huge delay in content delivery. Lines of error looks like:

20260527.14h04m02s CONNECT: attempt fail [CONNECTION_ERROR] to 72.167.35.147:443 for host='docs.trafficserver.apache.org' connection_result=ENOSTR [60] error=ENOSTR [60] retry_attempts=0 url='https://docs.trafficserver.apache.org/en/latest/_static/css/theme.css?v=9edc463e'

I've failed to identify a place in the sources that produce the error. Moreover, ENOSTR seems related to deprecated XSI STREAMS:

ENOSTR	       Not a STREAM (POSIX.1 (XSI STREAMS option))

I've not finded any evidenvce that Traffic Server uses XSI streams (stropts.h not included).
It seems that there is something wrong with error code/error sting matching/interpretation.

So I'm stuck in exploring delay of content delivery.

P.S. Apache Traffic Server 10.1, FreeBSD 14-stable

[bryancall]

@ant5 Can you please give and example on how to reproduce this issue? Also, can you give your build settings. We would like to reproduce this ourselves.

[ant5]

TrafficServer builded on FreeBSD 14-STABLE from -current port www/trafficserver.
Port option is MIMALLOC only, which translates to those flags:

-DENABLE_MAGICK=OFF  -DENABLE_MAXMIND_ACL=OFF -DENABLE_GEOIP_ACL=OFF
-DENABLE_MIMALLOC=1

Another build related flag is: CPUTYPE=nehalem

About reproduceability.
From user point it is visible as 10-15 seconds delay before site opened in a browser while surfing Web.
It is seems to be site (origin) related. I know only one site that reproduceably gives this error in my system: https://docs.trafficserver.apache.org/en/latest/

I've tried to debug with tags: socket|iocore_net but found no anomaly around the time when the error is raised.