Diagnose co-location networking problem

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: <freebsd-net@...>
Date: Tuesday, December 26, 2006 - 10:45 pm

I just got a server and put it in a co-location.

It runs RELEASE FreeBSD 6.1-RELEASE #0, pound, lighttpd and ruby on rails.

Most of the times I find the server responds nicely. But periodically
it doesn't respond properly when accessing its webpages: Type URL in
browser, hit return, no page appears. Try again and again and after a
few times it appears.

Other sites are accessible during these problematic times. Also, in
parallel I am connected to the server through ssh, and there are not
problems with that. Even during those times when the web pages don't
appear, I can type and see the result.

Before installing it at the datacentre, the server was working without
problems on the local network.

So I am thinking the problem may be with the co-location operation.

How can I make sure? How can I diagnose this? The only idea I had was
to run tcpdump on my Linux client (tcpdump host stbgo.org), and indeed
I can see entries lines this:

18:32:24.970139 sucrose.sugarmotor.net.34503 >
vps-18-138.virtualprivateservers.ca.http: S 2468438613:2468438613(0)
win 5840 <mss 1460,sackOK,timestamp 96924995 0,nop,wscale 0> (DF)
18:32:25.670135 sucrose.sugarmotor.net.34508 >
vps-18-138.virtualprivateservers.ca.http: S 2493895298:2493895298(0)
win 5840 <mss 1460,sackOK,timestamp 96925065 0,nop,wscale 0> (DF)
18:32:49.670152 sucrose.sugarmotor.net.34508 >
vps-18-138.virtualprivateservers.ca.http: S 2493895298:2493895298(0)
win 5840 <mss 1460,sackOK,timestamp 96927465 0,nop,wscale 0> (DF)
[note next is almost half a minute later]
18:33:12.970162 sucrose.sugarmotor.net.34503 >
vps-18-138.virtualprivateservers.ca.http: S 2468438613:2468438613(0)
win 5840 <mss 1460,sackOK,timestamp 96929795 0,nop,wscale 0> (DF)
18:33:12.985071 vps-18-138.virtualprivateservers.ca.http >
sucrose.sugarmotor.net.34503: S 2788301288:2788301288(0) ack
2468438614 win 65535 <mss 1460,nop,wscale 1,nop,nop,timestamp
708478538 96929795,sackOK,eol> (DF)


But I am not sure what these lines are telling me; other than
"sucrose" tried a few times, and then got a response (last line).

Any hints?

Thanks

Stephan


-- 
Stephan Wehner
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Diagnose co-location networking problem, Stephan Wehner, (Tue Dec 26, 10:45 pm)
Re: Diagnose co-location networking problem, Matthew Hudson, (Wed Dec 27, 6:18 pm)
Re: Diagnose co-location networking problem, Stephan Wehner, (Thu Dec 28, 2:08 am)
Re: Diagnose co-location networking problem, Matthew Hudson, (Thu Dec 28, 4:31 pm)
Re: Diagnose co-location networking problem, Stephan Wehner, (Tue Jan 2, 12:07 am)
Re: Diagnose co-location networking problem, Matthew Hudson, (Thu Jan 4, 3:34 pm)
Re: Diagnose co-location networking problem, Stephan Wehner, (Fri Jan 5, 2:33 am)
Re: Diagnose co-location networking problem, Gary Palmer, (Thu Dec 28, 1:31 pm)
Re: Diagnose co-location networking problem, Bill Vermillion, (Thu Dec 28, 8:07 am)
Re: Diagnose co-location networking problem, Stephan Wehner, (Thu Dec 28, 12:31 pm)
Re: Diagnose co-location networking problem, Bill Vermillion, (Thu Dec 28, 5:46 pm)
Re: Diagnose co-location networking problem, Bill Vermillion, (Wed Dec 27, 9:45 am)
Re: Diagnose co-location networking problem, Stephan Wehner, (Wed Dec 27, 1:55 am)