Jetpack Stats killing my server
-
The jetpack stats seem to take so much APache CPU that the server goes into tilt:
Masses of
“84.73.90.197 – – [03/Feb/2013:14:53:42 +0100] “POST /wp-admin/admin-ajax.php HTTP/1.1” 200 476 “https://snbchf.com/wp-admin/admin.php?page=stats” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/536.26.17 (KHTML, like Gecko) Version/6.0.2 Safari/536.26.17” “Can’t wordpress.com improve them?
________________________________________
Hello George,
Taking a look at our logs I was able to determine that the problem was indeed being caused by the requests coming from your IP address. You can see a summary of the top requesting IP addresses below:
=====================================
Sun Feb 3 15:41:14 CET 2013
—————————————————————-
/var/www/vhosts/snbchf.com/statistics/logs/access_log
# of requests IP address Domain name (if available)
2499 84.73.90.197 84-73-90-197.dclient.hispeed.ch.
623 92.60.240.211 211-240-60-90.packetexchange.net.
446 198.154.201.204
405 219.94.255.179 www3405uf.sakura.ne.jp.
384 108.161.184.116
301 108.161.180.116
289 108.161.190.116
288 66.249.73.121 crawl-66-249-73-121.googlebot.com.
221 108.161.181.116
115 184.168.27.109 p3nlhg897.shr.prod.phx3.secureserver.net.
105 69.64.56.47 s441.pingdom.com.
105 178.255.154.2 s429.pingdom.com.
104 95.211.87.85 s406.pingdom.com.
104 72.46.153.26 s451.pingdom.com.
104 64.237.55.3 s426.pingdom.com.
104 64.141.100.136 s431.pingdom.com.
104 212.84.74.156 s424.pingdom.com.
104 204.152.200.42 s410.pingdom.com.
104 188.138.118.144 s465.pingdom.com.
89 65.55.24.245 msnbot-65-55-24-245.search.msn.com.
=====================================You can see that at the time of the largest load today, the VPS was using up a very large amount of resources due to the wp-admin/admin-ajax.php script. The logs show us that this is being caused by your stats plugin, that is provided by Jetpack.
—————————————————————-
84.73.90.197 – – [03/Feb/2013:14:43:48 +0100] “POST /wp-admin/admin-ajax.php HTTP/1.1” 200 476 “https://snbchf.com/wp-admin/admin.php?page=stats” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/536.26.17 (KHTML, like Gecko) Version/6.0.2 Safari/536.26.17”
84.73.90.197 – – [03/Feb/2013:14:48:41 +0100] “POST /wp-admin/admin-ajax.php HTTP/1.1” 200 476 “https://snbchf.com/wp-admin/admin.php?page=stats” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/536.26.17 (KHTML, like Gecko) Version/6.0.2 Safari/536.26.17”
84.73.90.197 – – [03/Feb/2013:14:53:42 +0100] “POST /wp-admin/admin-ajax.php HTTP/1.1” 200 476 “https://snbchf.com/wp-admin/admin.php?page=stats” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/536.26.17 (KHTML, like Gecko) Version/6.0.2 Safari/536.26.17”
84.73.90.197 – – [03/Feb/2013:14:58:48 +0100] “POST /wp-admin/admin-ajax.php HTTP/1.1” 200 476 “https://snbchf.com/wp-admin/admin.php?page=stats” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/536.26.17 (KHTML, like Gecko) Version/6.0.2 Safari/536.26.17”
84.73.90.197 – – [03/Feb/2013:15:03:44 +0100] “POST /wp-admin/admin-ajax.php HTTP/1.1” 200 476 “https://snbchf.com/wp-admin/admin.php?page=stats” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/536.26.17 (KHTML, like Gecko) Version/6.0.2 Safari/536.26.17”
84.73.90.197 – – [03/Feb/2013:15:08:45 +0100] “POST /wp-admin/admin-ajax.php HTTP/1.1” 200 476 “https://snbchf.com/wp-admin/admin.php?page=stats” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/536.26.17 (KHTML, like Gecko) Version/6.0.2 Safari/536.26.17”
84.73.90.197 – – [03/Feb/2013:15:13:46 +0100] “POST /wp-admin/admin-ajax.php HTTP/1.1” 200 476 “https://snbchf.com/wp-admin/admin.php?page=stats” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/536.26.17 (KHTML, like Gecko) Version/6.0.2 Safari/536.26.17”
84.73.90.197 – – [03/Feb/2013:15:18:47 +0100] “POST /wp-admin/admin-ajax.php HTTP/1.1” 200 476 “https://snbchf.com/wp-admin/admin.php?page=stats” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/536.26.17 (KHTML, like Gecko) Version/6.0.2 Safari/536.26.17”
84.73.90.197 – – [03/Feb/2013:15:28:50 +0100] “POST /wp-admin/admin-ajax.php HTTP/1.1” 200 476 “https://snbchf.com/wp-admin/admin.php?page=stats” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/536.26.17 (KHTML, like Gecko) Version/6.0.2 Safari/536.26.17”
84.73.90.197 – – [03/Feb/2013:15:33:50 +0100] “POST /wp-admin/admin-ajax.php HTTP/1.1” 200 476 “https://snbchf.com/wp-admin/admin.php?page=stats” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/536.26.17 (KHTML, like Gecko) Version/6.0.2 Safari/536.26.17”
84.73.90.197 – – [03/Feb/2013:15:38:51 +0100] “POST /wp-admin/admin-ajax.php HTTP/1.1” 200 476 “https://snbchf.com/wp-admin/admin.php?page=stats” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/536.26.17 (KHTML, like Gecko) Version/6.0.2 Safari/536.26.17”
84.73.90.197 – – [03/Feb/2013:15:43:53 +0100] “POST /wp-admin/admin-ajax.php HTTP/1.1” 200 476 “https://snbchf.com/wp-admin/admin.php?page=stats” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/536.26.17 (KHTML, like Gecko) Version/6.0.2 Safari/536.26.17”
84.73.90.197 – – [03/Feb/2013:15:48:53 +0100] “POST /wp-admin/admin-ajax.php HTTP/1.1” 200 476 “https://snbchf.com/wp-admin/admin.php?page=stats” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/536.26.17 (KHTML, like Gecko) Version/6.0.2 Safari/536.26.17”
84.73.90.197 – – [03/Feb/2013:15:53:54 +0100] “POST /wp-admin/admin-ajax.php HTTP/1.1” 200 476 “https://snbchf.com/wp-admin/admin.php?page=stats” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/536.26.17 (KHTML, like Gecko) Version/6.0.2 Safari/536.26.17”
84.73.90.197 – – [03/Feb/2013:15:59:31 +0100] “POST /wp-admin/admin-ajax.php HTTP/1.1” 200 476 “https://snbchf.com/wp-admin/admin.php?page=stats” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/536.26.17 (KHTML, like Gecko) Version/6.0.2 Safari/536.26.17”
—————————————————————-I logged into your WordPress and clicked on your stats page and the VPS’s load instantly spiked to almost 1.00. Clicking on a few pages caused the load to spike much higher than 1.00. It looks as though this is the cause of your load.
- The topic ‘Jetpack Stats killing my server’ is closed to new replies.