Comments for Alchemist http://alchemi.st Ramblings on the eclectic and dangerous. Mon, 20 Feb 2012 22:42:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Comment on The actual graylog2 installation instructions by mklappstuhl http://alchemi.st/the-actual-graylog2-installation-instructions/#comment-214 mklappstuhl Mon, 20 Feb 2012 22:42:00 +0000 http://alchemi.st/?p=760#comment-214 Thanks! Why don't you edit the installation instructions at the Github wiki? Maybe try to stay distribution agnostic but at least add some info what else is needed... Thanks! Why don’t you edit the installation instructions at the Github wiki? Maybe try to stay distribution agnostic but at least add some info what else is needed…

]]> Comment on The actual graylog2 installation instructions by mklappstuhl http://alchemi.st/the-actual-graylog2-installation-instructions/#comment-213 mklappstuhl Mon, 20 Feb 2012 22:41:18 +0000 http://alchemi.st/?p=760#comment-213 Thanks! Why don't you edit the installation instructions at the Github wiki. Thanks! Why don’t you edit the installation instructions at the Github wiki.

]]> Comment on Nginx, WordPress Network, and Fastcgi Cache: The Ultimate Guide. by admin http://alchemi.st/nginx-wordpress-network-and-fastcgi-cache-the-ultimate-guide/#comment-186 admin Fri, 27 Jan 2012 23:54:55 +0000 http://alchemi.st/?p=361#comment-186 this upstart script is not ideal. I've added a new one above this upstart script is not ideal. I’ve added a new one above

]]> Comment on Nginx, WordPress Network, and Fastcgi Cache: The Ultimate Guide. by chris hough http://alchemi.st/nginx-wordpress-network-and-fastcgi-cache-the-ultimate-guide/#comment-183 chris hough Wed, 28 Dec 2011 21:30:15 +0000 http://alchemi.st/?p=361#comment-183 I was able to finally get my system upgraded and put together a post about it here: http://noconformity.co/2011/12/06/rackspace-cloud-ubuntu-nginx-upgrade/ Here was how I set up my server from the start: http://noconformity.co/2011/11/09/rackspace-cloud-ubuntu-11-04-lemp-server/ I was able to finally get my system upgraded and put together a post about it here: http://noconformity.co/2011/12/06/rackspace-cloud-ubuntu-nginx-upgrade/

Here was how I set up my server from the start:
http://noconformity.co/2011/11/09/rackspace-cloud-ubuntu-11-04-lemp-server/

]]> Comment on Nginx, WordPress Network, and Fastcgi Cache: The Ultimate Guide. by admin http://alchemi.st/nginx-wordpress-network-and-fastcgi-cache-the-ultimate-guide/#comment-182 admin Fri, 09 Dec 2011 18:19:08 +0000 http://alchemi.st/?p=361#comment-182 I'm currently using this upstart script: <pre escaped="true" lang="bash" line="1">description "nginx http daemon" start on runlevel [2] stop on runlevel [016] console owner exec /opt/nginx/sbin/nginx -c /opt/nginx/conf/nginx.conf -g "daemon off;" respawn </pre> I’m currently using this upstart script:

1
2
3
4
5
6
7
8
9
10

description "nginx http daemon"
 
start on runlevel [2]
stop on runlevel [016]
 
console owner
 
exec /opt/nginx/sbin/nginx -c /opt/nginx/conf/nginx.conf -g "daemon off;"
 
respawn
]]> Comment on Nginx, WordPress Network, and Fastcgi Cache: The Ultimate Guide. by chris hough http://alchemi.st/nginx-wordpress-network-and-fastcgi-cache-the-ultimate-guide/#comment-181 chris hough Mon, 05 Dec 2011 00:35:17 +0000 http://alchemi.st/?p=361#comment-181 disregard my last post, I was able to get it installed correctly. disregard my last post, I was able to get it installed correctly.

]]> Comment on Nginx, WordPress Network, and Fastcgi Cache: The Ultimate Guide. by chris hough http://alchemi.st/nginx-wordpress-network-and-fastcgi-cache-the-ultimate-guide/#comment-180 chris hough Sat, 03 Dec 2011 23:54:04 +0000 http://alchemi.st/?p=361#comment-180 after reading your post I set out to try to upgrade and configure my nginx installation to meet the specs. after make install, what are the other commands to get it to startup? http://serverfault.com/questions/337421/ubuntu-server-upgrade-nginx-to-1-1-5-from-1-0-10 the older installation had a /etc/init.d start process after reading your post I set out to try to upgrade and configure my nginx installation to meet the specs. after make install, what are the other commands to get it to startup? http://serverfault.com/questions/337421/ubuntu-server-upgrade-nginx-to-1-1-5-from-1-0-10 the older installation had a /etc/init.d start process

]]> Comment on Nginx, WordPress Network, and Fastcgi Cache: The Ultimate Guide. by admin http://alchemi.st/nginx-wordpress-network-and-fastcgi-cache-the-ultimate-guide/#comment-148 admin Sat, 10 Sep 2011 17:55:54 +0000 http://alchemi.st/?p=361#comment-148 Yeah, I would let nginx do the compression, instead of php. Glad you got it fixed! Yeah, I would let nginx do the compression, instead of php. Glad you got it fixed!

]]> Comment on Nginx, WordPress Network, and Fastcgi Cache: The Ultimate Guide. by Eleshar http://alchemi.st/nginx-wordpress-network-and-fastcgi-cache-the-ultimate-guide/#comment-147 Eleshar Sat, 10 Sep 2011 07:32:46 +0000 http://alchemi.st/?p=361#comment-147 Unfortunately that didn't make a difference, but I finally figured out why it wasn't working. I had zlib.output_compression active in php.ini, once I deactivated that it started working. Unfortunately that didn’t make a difference, but I finally figured out why it wasn’t working.

I had zlib.output_compression active in php.ini, once I deactivated that it started working.

]]> Comment on Nginx, WordPress Network, and Fastcgi Cache: The Ultimate Guide. by admin http://alchemi.st/nginx-wordpress-network-and-fastcgi-cache-the-ultimate-guide/#comment-146 admin Fri, 09 Sep 2011 19:39:12 +0000 http://alchemi.st/?p=361#comment-146 So, first and foremost, I would suggest double checking to make sure the user fmmsync and the group www-data can write to /var/cache/nginx Secondly, It looks like you are passing the connection off to php before you are executing the cache. You want to include the fastcgi params first, then execute the cache, then move on the the fastcgi param configuration, and then finally send the connection back to php. Change the order of your configuration directives to something more like this: <pre escaped="true" lang="nginx" line="1"> include fastcgi_params; fastcgi_cache_use_stale error timeout invalid_header http_500; fastcgi_cache_key $host$request_uri; fastcgi_cache WORDPRESS; fastcgi_cache_valid 200 2m; fastcgi_cache_bypass $nocache; fastcgi_no_cache $nocache; fastcgi_cache_min_uses 1; fastcgi_index index.php; fastcgi_param CONTENT-LENGTH $content_length; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; fastcgi_param PATH_INFO $fastcgi_script_name; fastcgi_pass php; </pre> Third, it looks like your cache purge key and cache key are different: <pre escaped="true" lang="nginx" line="1"> fastcgi_cache_purge WORDPRESS $host$1$request_method; fastcgi_cache_key $host$request_uri; </pre> additionally, make sure you are testing with a browser that isn't logged into your wordpress instance. I like to add a header to the response to check wether or the the request would have been cached, or called from the cache: <pre escaped="true" lang="nginx" line="1"> add_header nocache $nocache; </pre> This will return empty if the cache ought to have been used, and with "y" if the cache is bypassed. Aside from that, I would simplify your fastcgi_cache_path directive. Once you've got it caching something, try adding directives to optimize. For even more speed, try putting the cache on a <a href="http://www.ruby-forum.com/topic/203190" rel="nofollow">tmpfs</a>! Hope this helps! So, first and foremost, I would suggest double checking to make sure the user fmmsync and the group www-data can write to /var/cache/nginx
Secondly, It looks like you are passing the connection off to php before you are executing the cache. You want to include the fastcgi params first, then execute the cache, then move on the the fastcgi param configuration, and then finally send the connection back to php. Change the order of your configuration directives to something more like this:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

include fastcgi_params;
fastcgi_cache_use_stale error timeout invalid_header http_500;
fastcgi_cache_key $host$request_uri;
fastcgi_cache WORDPRESS;
fastcgi_cache_valid 200 2m;
fastcgi_cache_bypass $nocache;
fastcgi_no_cache $nocache;
fastcgi_cache_min_uses 1;
 
fastcgi_index index.php;
fastcgi_param CONTENT-LENGTH $content_length;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
fastcgi_param PATH_INFO $fastcgi_script_name;
 
fastcgi_pass php;

Third, it looks like your cache purge key and cache key are different:

1
2

fastcgi_cache_purge WORDPRESS $host$1$request_method;
fastcgi_cache_key $host$request_uri;

additionally, make sure you are testing with a browser that isn’t logged into your wordpress instance. I like to add a header to the response to check wether or the the request would have been cached, or called from the cache:

1

add_header nocache $nocache;

This will return empty if the cache ought to have been used, and with “y” if the cache is bypassed.

Aside from that, I would simplify your fastcgi_cache_path directive. Once you’ve got it caching something, try adding directives to optimize.

For even more speed, try putting the cache on a tmpfs!

Hope this helps!

]]>