hours, status changed; resolution, totalhours set

chris — Mon, 27 Mar 2017 12:32:41 GMT

hours changed from 0 to 0.5
status changed from new to closed
resolution set to fixed
totalhours set to 0.5

A lot of requests were coming form a Russian IP address which appears to be crawling the site but getting a lote of 301's due to the Nginx rate limiting:

 grep "95.213.191.13" /var/log/nginx/crin.org.access.log | wc -l
1451

grep "95.213.191.13" /var/log/nginx/crin.org.access.log | awk '{ print $9 }' | grep 200 | wc -l
491
grep "95.213.191.13" /var/log/nginx/crin.org.access.log | awk '{ print $9 }' | grep 301 | wc -l
943

I have blocked that IP address.

Another one causing problems:

grep 163.172.71.23  /var/log/nginx/crin.org.access.log | wc -l
1961

Again this bot is getting more 301 responses than 200 responses:

grep 163.172.71.23  /var/log/nginx/crin.org.access.log | awk '{ print $9 }' | grep 200 | wc -l
807
grep 163.172.71.23  /var/log/nginx/crin.org.access.log | awk '{ print $9 }' | grep 301 | wc -l
1149

This French IP address has also been blocked.

The load spike now appears to have passed.

CRIN Trac: Ticket #105: High load and slow responses from Crin2

hours, status changed; resolution, totalhours set