New mirror

[Matthew Dillon]

:Peter Avalos wrote:
:> The box has been up all day.  I just woke up, so I'll check with the
:> NOC to see if they were having any network problems.  I'm having no
:> problems accessing it right now.  Can you let me know if you're still
:> seeing a problem?
:> 
:> Peter
:
:Looks like the FTP server works.. HTTP still times out.
:
:- Erik

    FTP works for me.

    HTTP kinda works for me, in that I can click around and I can start
    downloads, but for some reason why I hit the Reload button I sometimes
    get long periods where the arrows are cycling around and the page is
    not completing its load.  And sometimes it fails to connect entirely.

    When I ping the box it works fine... no packet loss even with big
    ping packets.  Ping works fine even when the box is ignoring my TCP
    connection attempts, so it isn't routing.

    TCP connections seem to get lost or fail or have high latencies.
    For example, at this second I can't seem to connect to port 80:

13:03:03.262341 IP 216.240.41.44.4994 > 209.200.146.2.80: S 1909518785:1909518785(0) win 57344 <mss 1460,nop,wscale 0,nop,nop,timestamp 197383946 0>
13:03:06.262235 IP 216.240.41.44.4994 > 209.200.146.2.80: S 1909518785:1909518785(0) win 57344 <mss 1460,nop,wscale 0,nop,nop,timestamp 197384246 0>
13:03:09.462244 IP 216.240.41.44.4994 > 209.200.146.2.80: S 1909518785:1909518785(0) win 57344 <mss 1460,nop,wscale 0,nop,nop,timestamp 197384566 0>
13:03:12.662257 IP 216.240.41.44.4994 > 209.200.146.2.80: S 1909518785:1909518785(0) win 57344 <mss 1460>
13:03:15.862273 IP 216.240.41.44.4994 > 209.200.146.2.80: S 1909518785:1909518785(0) win 57344 <mss 1460>
13:03:19.062285 IP 216.240.41.44.4994 > 209.200.146.2.80: S 1909518785:1909518785(0) win 57344 <mss 1460>
13:03:25.262306 IP 216.240.41.44.4994 > 209.200.146.2.80: S 1909518785:1909518785(0) win 57344 <mss 1460>
13:03:37.462347 IP 216.240.41.44.4994 > 209.200.146.2.80: S 1909518785:1909518785(0) win 57344 <mss 1460>

    Other preexisting TCP connections seem to still be good, the box
    does eventually close them down even while it continues to ignore new
    connection attempts (2446 is a new connection attempt, while
    4252 is an old one being shut down).

13:04:54.082601 IP 216.240.41.44.2446 > 209.200.146.2.80: S 3618086681:3618086681(0) win 57344 <mss 1460,nop,wscale 0,nop,nop,timestamp 197395028 0>
13:04:57.282609 IP 216.240.41.44.2446 > 209.200.146.2.80: S 3618086681:3618086681(0) win 57344 <mss 1460,nop,wscale 0,nop,nop,timestamp 197395348 0>
13:05:00.482610 IP 216.240.41.44.2446 > 209.200.146.2.80: S 3618086681:3618086681(0) win 57344 <mss 1460>
13:05:03.682620 IP 216.240.41.44.2446 > 209.200.146.2.80: S 3618086681:3618086681(0) win 57344 <mss 1460>
13:05:06.186650 IP 209.200.146.2.80 > 216.240.41.44.4252: F 2467844930:2467844930(0) ack 2952691491 win 57920 <nop,nop,timestamp 5087950 197394748>
13:05:06.186690 IP 216.240.41.44.4252 > 209.200.146.2.80: . ack 1 win 57920 <nop,nop,timestamp 197396238 5087950>
13:05:06.882638 IP 216.240.41.44.2446 > 209.200.146.2.80: S 3618086681:3618086681(0) win 57344 <mss 1460>
13:05:09.533020 IP 216.240.41.44.4252 > 209.200.146.2.80: F 1:1(0) ack 1 win 57920 <nop,nop,timestamp 197396573 5087950>
13:05:09.577324 IP 209.200.146.2.80 > 216.240.41.44.4252: . ack 2 win 57920 <nop,nop,timestamp 5088288 197396573>

    But the box appears to sometimes take an aweful long time to close 
    a connection.  Note that 15 seconds the connection was left open before
    theshell closed it.  This could simply be due to Apache negotiating 
    persistent connections (in the below trace), but the failure in the
    top trace to even make a connection seems to indicate that Apache's
    LISTEN queue is full.

13:00:09.591650 IP 216.240.41.44.3762 > 209.200.146.2.80: S 4283943384:4283943384(0) win 57344 <mss 1460>
13:00:10.192476 IP 216.240.41.44.3549 > 209.200.146.2.80: S 3852218415:3852218415(0) win 57344 <mss 1460,nop,wscale 0,nop,nop,timestamp 197366639 0>
13:00:10.237399 IP 209.200.146.2.80 > 216.240.41.44.3549: S 424100512:424100512(0) ack 3852218416 win 57344 <mss 1460,nop,wscale 0,nop,nop,timestamp 5058359 197366639>
13:00:10.237476 IP 216.240.41.44.3549 > 209.200.146.2.80: . ack 1 win 57920 <nop,nop,timestamp 197366643 5058359>
13:00:10.237649 IP 216.240.41.44.3549 > 209.200.146.2.80: P 1:511(510) ack 1 win 57920 <nop,nop,timestamp 197366643 5058359>
13:00:10.287858 IP 209.200.146.2.80 > 216.240.41.44.3549: P 1:835(834) ack 511 win 57920 <nop,nop,timestamp 5058364 197366643>
13:00:10.358558 IP 216.240.41.44.3549 > 209.200.146.2.80: P 511:1029(518) ack 835 win 57920 <nop,nop,timestamp 197366655 5058364>
13:00:10.422652 IP 209.200.146.2.80 > 216.240.41.44.3549: P 835:1018(183) ack 1029 win 57920 <nop,nop,timestamp 5058376 197366655>
13:00:10.423107 IP 216.240.41.44.3549 > 209.200.146.2.80: P 1029:1548(519) ack 1018 win 57920 <nop,nop,timestamp 197366662 5058376>
13:00:10.469654 IP 209.200.146.2.80 > 216.240.41.44.3549: P 1018:1201(183) ack 1548 win 57920 <nop,nop,timestamp 5058382 197366662>
13:00:10.561649 IP 216.240.41.44.3549 > 209.200.146.2.80: . ack 1201 win 57920 <nop,nop,timestamp 197366676 5058382>

13:00:25.481744 IP 209.200.146.2.80 > 216.240.41.44.3549: F 1201:1201(0) ack 1548 win 57920 <nop,nop,timestamp 5059884 197366676>
13:00:25.481810 IP 216.240.41.44.3549 > 209.200.146.2.80: . ack 1202 win 57920 <nop,nop,timestamp 197368168 5059884>
13:00:33.791727 IP 216.240.41.44.3762 > 209.200.146.2.80: S 4283943384:4283943384(0) win 57344 <mss 1460>
13:00:39.458366 IP 216.240.41.44.3549 > 209.200.146.2.80: F 1548:1548(0) ack 1202 win 57920 <nop,nop,timestamp 197369565 5059884>
13:00:39.500518 IP 209.200.146.2.80 > 216.240.41.44.3549: . ack 1549 win 57920 <nop,nop,timestamp 5061285 197369565>

    My guess is that the Apache server needs some configuration tweeks... it
    probably needs more forks to handle the load.

					-Matt
					Matthew Dillon 
					<dillon at xxxxxxxxxxxxx>