[gentoo-user] {OT} Firefox's "Connecting"

[gentoo-user] {OT} Firefox's "Connecting"

[Grant]

Can anyone tell me what Firefox is doing when it says it is
"Connecting" to a particular website?  My site is periodically hanging
at that point, and I'd like to track down the problem.  Is it just
waiting for apache2's first response to the HTTP request?

- Grant
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] {OT} Firefox's "Connecting"

[Markus Schönhaber]

Grant wrote:
> Can anyone tell me what Firefox is doing when it says it is
> "Connecting" to a particular website?  My site is periodically hanging
> at that point, and I'd like to track down the problem.  Is it just
> waiting for apache2's first response to the HTTP request?

No, Firefox is propably waiting for the TCP connection to be
established. Use something like wireshark or tcpdump to find out for sure.

Regards
  mks

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] {OT} Firefox's "Connecting"

[Mick]

[-- Attachment #1: Type: text/plain, Size: 821 bytes --]

On Friday 08 June 2007 19:24, Markus Schönhaber wrote:
> Grant wrote:
> > Can anyone tell me what Firefox is doing when it says it is
> > "Connecting" to a particular website?  My site is periodically hanging
> > at that point, and I'd like to track down the problem.  Is it just
> > waiting for apache2's first response to the HTTP request?
>
> No, Firefox is propably waiting for the TCP connection to be
> established. Use something like wireshark or tcpdump to find out for sure.

I was trying to login (via ssh) to a virtual server and it was taking ages (19 
secs or so).  Apparently there was something wrong with the way the sysadmin 
had set up DNS.  Once fixed I would be asked for a passwd with 1-2 seconds.  
It could be that something like this is wrong with your server?
-- 
Regards,
Mick

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] {OT} Firefox's "Connecting"

[Grant]

> > > Can anyone tell me what Firefox is doing when it says it is
> > > "Connecting" to a particular website?  My site is periodically hanging
> > > at that point, and I'd like to track down the problem.  Is it just
> > > waiting for apache2's first response to the HTTP request?
> >
> > No, Firefox is propably waiting for the TCP connection to be
> > established. Use something like wireshark or tcpdump to find out for sure.
>
> I was trying to login (via ssh) to a virtual server and it was taking ages (19
> secs or so).  Apparently there was something wrong with the way the sysadmin
> had set up DNS.  Once fixed I would be asked for a passwd with 1-2 seconds.
> It could be that something like this is wrong with your server?

I'll check that out.  Thanks guys.

- Grant
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] {OT} Firefox's "Connecting"

[Kent Fredric]

On 6/10/07, Grant <emailgrant@gmail.com> wrote:
> > > > Can anyone tell me what Firefox is doing when it says it is
> > > > "Connecting" to a particular website?  My site is periodically hanging
> > > > at that point, and I'd like to track down the problem.  Is it just
> > > > waiting for apache2's first response to the HTTP request?
> > >
> > > No, Firefox is propably waiting for the TCP connection to be
> > > established. Use something like wireshark or tcpdump to find out for sure.
> >
> > I was trying to login (via ssh) to a virtual server and it was taking ages (19
> > secs or so).  Apparently there was something wrong with the way the sysadmin
> > had set up DNS.  Once fixed I would be asked for a passwd with 1-2 seconds.
> > It could be that something like this is wrong with your server?
>
> I'll check that out.  Thanks guys.
>

Try it with 'curl'
ie:
curl -v www.google.com

If it doesnt find an IP, its a DNS problem, if it finds an IP but
doesn't connect, it may be a routing problem, if it works for all
sites, but not a particular site, that site might be broken, and
'curl' might be able to help you see where.

:)



-- 
Kent
ruby -e '[1, 2, 4, 7, 0, 9, 5, 8, 3, 10, 11, 6, 12, 13].each{|x|
print "enNOSPicAMreil kdrtf@gma.com"[(2*x)..(2*x+1)]}'
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] {OT} Firefox's "Connecting"

[Grant]

> > > > > Can anyone tell me what Firefox is doing when it says it is
> > > > > "Connecting" to a particular website?  My site is periodically hanging
> > > > > at that point, and I'd like to track down the problem.  Is it just
> > > > > waiting for apache2's first response to the HTTP request?
> > > >
> > > > No, Firefox is propably waiting for the TCP connection to be
> > > > established. Use something like wireshark or tcpdump to find out for sure.
> > >
> > > I was trying to login (via ssh) to a virtual server and it was taking ages (19
> > > secs or so).  Apparently there was something wrong with the way the sysadmin
> > > had set up DNS.  Once fixed I would be asked for a passwd with 1-2 seconds.
> > > It could be that something like this is wrong with your server?
> >
> > I'll check that out.  Thanks guys.
> >
>
> Try it with 'curl'
> ie:
> curl -v www.google.com
>
> If it doesnt find an IP, its a DNS problem, if it finds an IP but
> doesn't connect, it may be a routing problem, if it works for all
> sites, but not a particular site, that site might be broken, and
> 'curl' might be able to help you see where.

Thanks Kent.  When I'm browsing my site and it hangs, I ping the
domain and the times are normal even though I'm having trouble
connecting at the exact same time.  The pings are really slow in
coming back, but the reported times are normal.  Does that sound like
a problem with apache2 then?

- Grant
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] {OT} Firefox's "Connecting"

[Kent Fredric]

On 6/10/07, Grant <emailgrant@gmail.com> wrote:
> > > > > > Can anyone tell me what Firefox is doing when it says it is
> > > > > > "Connecting" to a particular website?  My site is periodically hanging
> > > > > > at that point, and I'd like to track down the problem.  Is it just
> > > > > > waiting for apache2's first response to the HTTP request?
> > > > >
> > > > > No, Firefox is propably waiting for the TCP connection to be
> > > > > established. Use something like wireshark or tcpdump to find out for sure.
> > > >
> > > > I was trying to login (via ssh) to a virtual server and it was taking ages (19
> > > > secs or so).  Apparently there was something wrong with the way the sysadmin
> > > > had set up DNS.  Once fixed I would be asked for a passwd with 1-2 seconds.
> > > > It could be that something like this is wrong with your server?
> > >
> > > I'll check that out.  Thanks guys.
> > >
> >
> > Try it with 'curl'
> > ie:
> > curl -v www.google.com
> >
> > If it doesnt find an IP, its a DNS problem, if it finds an IP but
> > doesn't connect, it may be a routing problem, if it works for all
> > sites, but not a particular site, that site might be broken, and
> > 'curl' might be able to help you see where.
>
> Thanks Kent.  When I'm browsing my site and it hangs, I ping the
> domain and the times are normal even though I'm having trouble
> connecting at the exact same time.  The pings are really slow in
> coming back, but the reported times are normal.  Does that sound like
> a problem with apache2 then?
>

Sounds like a routing problem of sorts to me, apache  ( afaik ) has no
impact on /ping/ times. My favourite tool for finding traffic problems
is "mtr" , see packet loss and route and where packet loss is occuring
all at once :)   Sometimes it will report 100% packet loss on a middle
step if that server ignores pings tho, .. .so...

does curl respond properly? , or does it just sit there waiting for  response?



-- 
Kent
ruby -e '[1, 2, 4, 7, 0, 9, 5, 8, 3, 10, 11, 6, 12, 13].each{|x|
print "enNOSPicAMreil kdrtf@gma.com"[(2*x)..(2*x+1)]}'
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] {OT} Firefox's "Connecting"

[Grant]

> > > > > > > Can anyone tell me what Firefox is doing when it says it is
> > > > > > > "Connecting" to a particular website?  My site is periodically hanging
> > > > > > > at that point, and I'd like to track down the problem.  Is it just
> > > > > > > waiting for apache2's first response to the HTTP request?
> > > > > >
> > > > > > No, Firefox is propably waiting for the TCP connection to be
> > > > > > established. Use something like wireshark or tcpdump to find out for sure.
> > > > >
> > > > > I was trying to login (via ssh) to a virtual server and it was taking ages (19
> > > > > secs or so).  Apparently there was something wrong with the way the sysadmin
> > > > > had set up DNS.  Once fixed I would be asked for a passwd with 1-2 seconds.
> > > > > It could be that something like this is wrong with your server?
> > > >
> > > > I'll check that out.  Thanks guys.
> > > >
> > >
> > > Try it with 'curl'
> > > ie:
> > > curl -v www.google.com
> > >
> > > If it doesnt find an IP, its a DNS problem, if it finds an IP but
> > > doesn't connect, it may be a routing problem, if it works for all
> > > sites, but not a particular site, that site might be broken, and
> > > 'curl' might be able to help you see where.
> >
> > Thanks Kent.  When I'm browsing my site and it hangs, I ping the
> > domain and the times are normal even though I'm having trouble
> > connecting at the exact same time.  The pings are really slow in
> > coming back, but the reported times are normal.  Does that sound like
> > a problem with apache2 then?
> >
>
> Sounds like a routing problem of sorts to me, apache  ( afaik ) has no
> impact on /ping/ times. My favourite tool for finding traffic problems
> is "mtr" , see packet loss and route and where packet loss is occuring
> all at once :)   Sometimes it will report 100% packet loss on a middle
> step if that server ignores pings tho, .. .so...

But the ping times are normal.  I'm having problems with the site
intermittently hanging while I'm browsing, even as ping times are
coming back normal.  That's what makes me think it should be a problem
with the software on the server.  Does that sound right?

- Grant

> does curl respond properly? , or does it just sit there waiting for  response?

curl sits there waiting for the IP to respond.

- Grant
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] {OT} Firefox's "Connecting"

[Hans-Werner Hilse]

Hi,

On Sat, 9 Jun 2007 13:21:13 -0700
Grant <emailgrant@gmail.com> wrote:

> But the ping times are normal.  I'm having problems with the site
> intermittently hanging while I'm browsing, even as ping times are
> coming back normal.  That's what makes me think it should be a problem
> with the software on the server.  Does that sound right?
> 
> [...]
> > does curl respond properly? , or does it just sit there waiting for  response?
> 
> curl sits there waiting for the IP to respond.

- might be syncookies, if you have activated that
- any chance that it's the client you're using for access? Bad MTU/MSS
  settings?
- use tcpdump to inspect what's going on on the wire (best would be on
  server and client side and then compare timestamps). You get aware of
  retransmission tries and such...
- is server side name resolution working properly? Maybe something
  tries to reverse-resolve the IP address of connecting clients (though
  I don't know what should do such a thing on web server access...)

-hwh
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] {OT} Firefox's "Connecting"

[Grant]

> > > Sounds like a routing problem of sorts to me, apache  ( afaik ) has no
> > > impact on /ping/ times. My favourite tool for finding traffic problems
> > > is "mtr" , see packet loss and route and where packet loss is occuring
> > > all at once :)   Sometimes it will report 100% packet loss on a middle
> > > step if that server ignores pings tho, .. .so...
> >
> > But the ping times are normal.  I'm having problems with the site
> > intermittently hanging while I'm browsing, even as ping times are
> > coming back normal.  That's what makes me think it should be a problem
> > with the software on the server.  Does that sound right?
>
> no, not to me.  Ping only starts counting time once it's resolved the
> name (I think), so if your ping times are normal, but the delay between
> pings takes a long time, then there's possibly a name resolution
> problem... or at least that's what I've seen in the past...

That makes sense.  My host has fixed some kind of a problem on their
end, so hopefully that was the cause of this.  Thanks a lot for
everyone's help.

- Grant
-- 
gentoo-user@gentoo.org mailing list