[torqueusers] Hanging TIME_WAIT

Tim Freeman tfreeman at mcs.anl.gov
Tue Feb 17 14:07:06 MST 2009

With Torque 2.3.6, we are seeing many connections settle in to the TIME_WAIT
state and clog up the cluster because of privileged port socket exhaustion.

Jason Williams reported what looks to be the exact thing last month:


We're seeing the same netstat output too, the foreign socket is printed as the
local address.

Is there anything we can do?  Does this imply some misconfiguration?


More information about the torqueusers mailing list