Looks like some JS is being loaded by the akisment plugin, however it's path is producing a 500 error. https://blog.mozilla.org/openstandard-en/wp-content/plugins/akismet/_inc/form.js?ver=3.0.2 Also attaching a screenshot. Chris - this is one of those networked plugins that we dont configure at all on the open standard site. Can you check why this may be occuring.
this appears to be happening on all mutli-site instances on the prod blog platform. is this blocking using the plugin? i don't really have the cycles right now to dig into this. there are no errors in the apache error log, just logs like the following in the access log: "<IPS_REMOVED>" - - [09/Oct/2014:12:58:30 -0700] "GET /openstandard-en/wp-content/plugins/akismet/_inc/akismet.js?ver=3.0.2 HTTP/1.1" 500 541 "https://openstandard.mozilla.org/wp-admin/post.php?post=70&action=edit" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:33.0) Gecko/20100101 Firefox/33.0" $ curl -I https://blog.mozilla.org/wp-content/plugins/akismet/_inc/form.js\?ver\=3.0.2 HTTP/1.1 500 Internal Server Error Server: Apache X-Backend-Server: generic4.webapp.phx1.mozilla.com Vary: Accept-Encoding Content-Type: text/html; charset=iso-8859-1 Date: Thu, 09 Oct 2014 19:59:44 GMT Connection: close X-Cache-Info: not cacheable; response code not cacheable
Should be fixed shortly, pending a puppet run. Problem is that akismet ships a .htaccess file that includes Order, Allow, and Deny statements. The apache config has to specify "AllowOverride Limit" for this to be allowed... otherwise it throws that 500 ISE.
thnx :jakem. great catch.
No idea if this is related but the site in the past few minutes (10 or so) has slowed to crawl. Both the admin and site.
Verified fixed. Slowness was unrelated.. gravatar was having issues.
FWIW, If you're running Apache 2.5 or later you also need this entry in your httpd.conf otherwise the legacy access directives used by the Akismet .htaccess file will result in a 500 error: LoadModule access_compat_module libexec/apache2/mod_access_compat.so I noticed this after updating my Wordpress server and deliberately chose not to enable support for the legacy access directives (by leaving that line commented out) since I thought only my top-level .htaccess file existed in my document tree.