Stephan,
I haven't yet looked at the new data you've reported because of the
last point that you mention, the point that I brought up in my
previous email, is of critical importance. There is currently
evidence that suggests the possibility that this problem is not
reproduceable from anywhere bu
On Mon, Jan 01, 2007 at 08:07:59PM -0800, Stephan Wehner wrote:
> Hello again,
>
> to give a short summary; I contacted this list to ask for help with
> diagnosing a problem with a co-located server (accessible at
> http://stbgo.org) running FreeBSD 6.1. When I swamp it with requests
> (simply, ly
Hello again,
to give a short summary; I contacted this list to ask for help with
diagnosing a problem with a co-located server (accessible at
http://stbgo.org) running FreeBSD 6.1. When I swamp it with requests
(simply, lynx -dump http://stbgo.org > /dev/null in a loop)
some responses take 90 sec
> On Wed, Dec 27, 2006 at 10:08:25PM -0800, Stephan Wehner wrote:
...
> Oh, also, going back to the 198.168 address seen in the client dumps,
> it's clear that you're going through a NAT firewall or VPN or something
> on the way to your server. Thus are you able to reproduce this problem
> from a
Wise men talk because they have something to say, however
on Thu, Dec 28, 2006 at 08:31 , Stephan Wehner just had
to say something so we heard:
> >So login to the FreeBSD machine and trace back to your client IP -
> >or as close as you can get. That may mean just to the edge of your
> >current p
On Wed, Dec 27, 2006 at 10:08:25PM -0800, Stephan Wehner wrote:
> The server FreeBSD kernel doesn't support tcpdump. I should recompile it
> then, but not now.
Ok, that explains the private 192.168 IP address I saw in your earlier
dumps, it was from the client (a detail mentioned but that I overl
On Wed, Dec 27, 2006 at 10:08:25PM -0800, Stephan Wehner wrote:
> Ok, this is a little unfortunate: I can't run traceroute from the client PC
> (the service provider doesn't seem to like it). (Nor can I use ping)
/usr/ports/net/tcptraceroute
You should normally be able to use tcptraceroute to ge
So login to the FreeBSD machine and trace back to your client IP -
or as close as you can get. That may mean just to the edge of your
current provider but that may give you some idea.
Ok, here is the result.
$ traceroute 64.114.83.92
traceroute to 64.114.83.92 (64.114.83.92), 64 hops max, 40 b
On or about Wed, Dec 27, 2006 at 22:08 , while attempting a
Zarathustra emulation Stephan Wehner thus spake:
> Ok, this is a little unfortunate: I can't run traceroute from
> the client PC (the service provider doesn't seem to like it).
> (Nor can I use ping)
So login to the FreeBSD machine and
Ok, this is a little unfortunate: I can't run traceroute from the client PC
(the service provider doesn't seem to like it). (Nor can I use ping)
The server FreeBSD kernel doesn't support tcpdump. I should recompile it then,
but not now.
So I ran the netstat tests, seeing no other suggestion. B
On Tue, Dec 26, 2006 at 06:45:39PM -0800, Stephan Wehner wrote:
> 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 entri
Earlier in the linear time track, on approximately Tue, Dec 26, 2006 at 18:45 ,
Stephan Wehner divulged this public information:
> 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
On Tue, 26 Dec 2006, Stephan Wehner wrote:
> Ok, thanks, I now ran tcpdump with -n.
>
> Here I am testing with a little script that continuously accesses one of
> the pages. Right at the beginning it doesn't get very far: first
> response after 90 seconds.
>
> What kind of DNS problem did you ha
Ok, thanks, I now ran tcpdump with -n.
Here I am testing with a little script that continuously accesses one
of the pages.
Right at the beginning it doesn't get very far: first response after 90 seconds.
What kind of DNS problem did you have in mind?
Stephan
$ sudo /usr/sbin/tcpdump -n host st
On Tue, 26 Dec 2006, Stephan Wehner wrote:
> 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.
DNS.
try tcpdum
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 appe
16 matches
Mail list logo
