Non blocking socket connect() get errno ETIMEDOUT-Connection timed out
Question
I have a non-blocking IPv4 TCP socket, when I try to connect(), I get the errno ETIMEDOUT. It confused me a lot, since I have not set timeout on socket. What is some possible reasons of this case?
1 answers
solution1
0 2020-04-04 11:47:42
From man page:
ETIMEDOUT:
Timeout while attempting connection. The server may be too busy to accept new connections. Note that for IP sockets the timeout may be very long when syncookies are enabled on the server.
You can also see ETIMEDOUT in this quesiton How to handle ETIMEDOUT error
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.
Related Question
non blocking socket select returns 1 after connect
Non-blocking Socket connect always succeeds?
In a non blocking socket connect, select() always returns 1
Detect idle connection in non-blocking socket
using a non-blocking socket connection in C
Non-blocking pasv sock and blocking connection (active) socket
unix sockets - can't connect to server (connection timed out)
Unexpected revents value in poll for non blocking socket connect
Why is non-blocking socket connect so slow?
How to terminate non-blocking socket connection attempt?
Related Tags