[PLUG] Identifying Why One Web Site Will Not Load [UPDATE]

[Rich Shepard]

On Wed, 17 Sep 2014, Robert Citek wrote:

> Here are some commands from my system for comparison:
> I'm curious to know what your results are with the same commands.

> $ 2>&1 curl -v -s http://grass.osgeo.org/ > /dev/null | cat -n

$ 2>&1 curl -v -s http://grass.osgeo.org/ > /dev/null | cat -n
      1	* Hostname was NOT found in DNS cache
      2	*   Trying 140.211.15.75...
      3	* Connected to grass.osgeo.org (140.211.15.75) port 80 (#0)
      4	> GET / HTTP/1.1
      5	> User-Agent: curl/7.36.0
      6	> Host: grass.osgeo.org
      7	> Accept: */*
      8	>
      9	< HTTP/1.1 200 OK
     10	< Date: Wed, 17 Sep 2014 16:05:41 GMT
     11	* Server Apache/2.2.16 (Debian) is not blacklisted
     12	< Server: Apache/2.2.16 (Debian)
     13	< X-Powered-By: PHP/5.3.3-7+squeeze19
     14	< Set-Cookie: CMSSESSID34ee0599=a8h24n5mbtg2vs6f01ds9kq9i6; path=/
     15	< Expires: Mon, 26 Jul 1997 05:00:00 GMT
     16	< Cache-Control: no-store, no-cache, must-revalidate
     17	< Last-Modified: Wed, 17 Sep 2014 16:05:41 GMT
     18	< Cache-Control: post-check=0, pre-check=0
     19	< Pragma: no-cache
     20	< Vary: Accept-Encoding
     21	< Connection: close
     22	< Transfer-Encoding: chunked
     23	< Content-Type: text/html; charset=utf-8
     24	<
     25	{ [data not shown]
     26	* Closing connection 0

   There was a _long_ pause at step 8; about 2 minutes ... and that is the
source of the apparent problem. I tried http://grass.osgeo.org/ then went
off to do something else. When I returned about 4 minutes later the page was
displayed.

   Ergo, it will load, but there's time to make coffee before it does. This
changes the focus to where the delay for this one site might be.

Thanks, Robert and everyone else,

Rich