246 reputation
14
bio website DataExpedition.com
location
age
visits member for 2 years, 11 months
seen 13 hours ago

Sep
24
awarded  Autobiographer
Jan
16
awarded  Yearling
May
16
awarded  Analytical
May
14
answered How often does asymmetric latency actually happen?
Apr
30
comment connection hanging
If possible, try hard-coding the known-good IP address in the script and see if that helps. If that fixes the problem, then its a DNS issue. Most likely either a bad name server in /etc/resolv.conf or improper caching somewhere.
Apr
30
answered connection hanging
Apr
30
answered Site extremely slow - unresponsive - on Linode
Mar
20
answered I have a mail server that hosts several client emails but 1 in particular is being blocked because of its SBRS score
Mar
20
answered windows firewall - how much delay introduce, how safe to turn off?
Mar
20
answered How to measure UDP socket buffer loss on Windows Server 2008 R2?
Feb
24
answered PING: timed out, host unreachable and succes all at once
Feb
24
answered WSAECONNRESET curiousity
Feb
24
answered Debugging network slowness
Feb
21
comment How long does it take to fsck a volume?
That is certainly a possibility, although I would think relocation on that scale would produce some I/O errors. Based on the very slow baseline of 80 megabits per second, I was assuming the test was run on an active system. So... are there I/O errors in the system log, how were the hdparm tests performed, and were the results in "megabits" or "megabytes" per second?
Feb
21
answered How long does it take to fsck a volume?
Jan
25
comment Exhausting Linux machine TCP socket limit (~70k)?
TIME_WAIT is a factor simply because any port in that state is unavailable. If there is a spike in traffic, the number of TIME_WAITs could become so high that there are not enough free ports available for new connections. That would cause a burst of already in use errors. But because your connection times are short, samples with netstat may not capture that moment. Given all the circumstances, spreading across more nodes/addresses may be the most practical solution.
Jan
19
comment Exhausting Linux machine TCP socket limit (~70k)?
Wow, that's a lot of TIME_WAITs for a 4 second timeout. I see you have net.ipv4.tcp_tw_reuse set. You could also try net.ipv4.tcp_tw_recycle. serverfault.com/questions/342741/… stackoverflow.com/questions/6426253/… However, if you have access to the source code I suggest examining how the TCP sessions are being closed. A TIME_WAIT state usually occurs when a connection is closed while data is still in transit or not cleanly closed.
Jan
18
comment Exhausting Linux machine TCP socket limit (~70k)?
Another possibility is that the connections are not dropping cleanly, causing ports to be left in a TIME_WAIT state. How quickly are these connections cycling? In other words, how long does a typical TCP session last?
Jan
17
awarded  Teacher
Jan
17
answered Exhausting Linux machine TCP socket limit (~70k)?