|
||||||||
|
|
|||||||
![]() |
|
|
Thread Tools | Display Modes |
|
#1
|
|
I have a process that goes out to a server and does a software update.
Originally it took 60 - 80 seconds to accomplish. It now takes 500 - 1000 seconds to do the same function. Several other box's that do this same script have not seen this increase. The script will sit at this function for long periods of time; Connecting to www.uabc.edu[1xx.xxx.1xx.182]:80... Then it finally gets the; Connecting to www.uabc.edu[1xx.xxx.1xx.182]:80... connected. HTTP request sent, awaiting response... 200 OK I noticed that the tw value is high on this box as seen in the /proc/net/sockstat file [tw=65 when the script is sitting waiting to connect]. A tcpdump of the transaction is full of; 12:41:13.984998 monitor.uabc.edu.33690 > 1xx.xxx.1xx.182.http: . ack 995 win 6958 <nop,nop,timestamp 1503190 884584174> (DF) Can someone tell me what is happening during this connect? And where to look next? I should add that once it makes this connect it flys through the data xfer until it hits the next connect where it sits once again whoha |
|
#2
|
|||
|
|||
|
whoha wrote:
> I have a process that goes out to a server and does a software update. > Originally it took 60 - 80 seconds to accomplish. It now takes 500 - > 1000 seconds to do the same function. Several other box's that do this > same script have not seen this increase. The script will sit at this > function for long periods of time; > > Connecting to www.uabc.edu[1xx.xxx.1xx.182]:80... > > Then it finally gets the; > > Connecting to www.uabc.edu[1xx.xxx.1xx.182]:80... connected. > HTTP request sent, awaiting response... 200 OK > > > I noticed that the tw value is high on this box as seen in the > /proc/net/sockstat file [tw=65 when the script is sitting waiting to > connect]. A tcpdump of the transaction is full of; > > 12:41:13.984998 monitor.uabc.edu.33690 > 1xx.xxx.1xx.182.http: . ack 995 > win 6958 <nop,nop,timestamp 1503190 884584174> (DF) > > Can someone tell me what is happening during this connect? And where to > look next? I should add that once it makes this connect it flys through > the data xfer until it hits the next connect where it sits once again > Ok I'v tried the following items; moved server ip/name to hosts file looked at resolv.conf and host.conf both are correct - no change not a DNS problem removed iptables checked with iptables -L to make sure table is unloaded - no change changed mtu to a smaller value [1472] - no change [ this one came from a listing in google groups] moved the nic to a different module and port in the switch - no change used a different nic - no change checked the port for errors - no errors checked netstat -a - unsure of output, looks ok to me Can someone give me some ideas what to try next? I have checked packages to see if we have the latest . |
![]() |
| Tags |
| connecting, problems, process, remote, server |
| Thread Tools | |
| Display Modes | |
|
|