Archives

It may be due to a coding change I made last night to add the hybridfest banner, or it could be a dos attack causing load on our server. I wil look into it when I get home in a few hours.

Tom,

I don't think it's a DoS attack (well, not a network-based DoS attack... it could be an application-level attack, though) as my ping times to www.cleanmpg.com show:

PING www.cleanmpg.com (69.41.173.98) 56(84) bytes of data.
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=1 ttl=49 time=62.6 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=2 ttl=49 time=63.8 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=3 ttl=49 time=63.7 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=4 ttl=49 time=65.4 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=5 ttl=49 time=64.7 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=6 ttl=49 time=63.1 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=7 ttl=49 time=62.6 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=8 ttl=49 time=65.0 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=9 ttl=49 time=68.9 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=10 ttl=49 time=62.7 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=11 ttl=49 time=66.5 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=12 ttl=49 time=64.9 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=13 ttl=49 time=63.4 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=14 ttl=49 time=71.4 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=15 ttl=49 time=68.0 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=16 ttl=49 time=64.6 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=17 ttl=49 time=63.0 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=18 ttl=49 time=62.6 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=19 ttl=49 time=64.7 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=20 ttl=49 time=63.7 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=21 ttl=49 time=65.4 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=22 ttl=49 time=66.6 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=23 ttl=49 time=69.0 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=24 ttl=49 time=64.9 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=25 ttl=49 time=63.2 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=26 ttl=49 time=63.0 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=27 ttl=49 time=69.1 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=28 ttl=49 time=64.5 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=29 ttl=49 time=68.9 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=30 ttl=49 time=67.5 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=31 ttl=49 time=67.0 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=32 ttl=49 time=65.8 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=33 ttl=49 time=62.7 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=34 ttl=49 time=74.0 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=35 ttl=49 time=112 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=36 ttl=49 time=62.5 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=37 ttl=49 time=63.8 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=38 ttl=49 time=66.0 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=39 ttl=49 time=73.1 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=40 ttl=49 time=66.4 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=41 ttl=49 time=64.1 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=42 ttl=49 time=69.7 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=43 ttl=49 time=63.2 ms
64 bytes from mail.cleanmpg.com (69.41.173.98): icmp_seq=44 ttl=49 time=63.5 ms


On a side note I just realized the reverse DNS record is a bit screwy...

~$ dig www.cleanmpg.com

; <<>> DiG 9.3.2 <<>> www.cleanmpg.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31534
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 2

;; QUESTION SECTION:
;www.cleanmpg.com. IN A

;; ANSWER SECTION:
www.cleanmpg.com. 146 IN A 69.41.173.98

~$ dig -x 69.41.173.98

; <<>> DiG 9.3.2 <<>> -x 69.41.173.98
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30541
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4

;; QUESTION SECTION:
;98.173.41.69.in-addr.arpa. IN PTR

;; ANSWER SECTION:
98.173.41.69.in-addr.arpa. 409 IN PTR mail.cleanmpg.com.

Well, looks like it was something hogging resources. I'll have to keep an eye on the server to see if I can find out what. I'm leaning toward maybe a memory leak in something I worked on last night.

Things should be better now.

Hi Tom:

___Thank goodness the gallery is back :)

___Good Luck

___Wayne

Yes - was slow, is definitely better now.

Also it looks like the graphs in the Mileage Log now update immediately after adding a tank. Formerly I think the graph only updated later that evening? Nice work!

It may be due to a coding change I made last night to add the hybridfest banner, or it could be a dos attack causing load on our server. I wil look into it when I get home in a few hours.

Oh sure... first Hybridfest is blamed for the giant "smug" cloud over Madison, and now you try blaming your site problems on our banner. Geesh. What next? :)