<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>MrBrown blob &#187; nginx</title>
	<atom:link href="http://charles.lescampeurs.org/tag/nginx/feed" rel="self" type="application/rss+xml" />
	<link>http://charles.lescampeurs.org</link>
	<description>random bits.</description>
	<lastBuildDate>Sat, 10 Apr 2010 09:02:57 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Permanent redirect with nginx</title>
		<link>http://charles.lescampeurs.org/2009/03/20/permanent-redirect-with-nginx</link>
		<comments>http://charles.lescampeurs.org/2009/03/20/permanent-redirect-with-nginx#comments</comments>
		<pubDate>Fri, 20 Mar 2009 05:12:42 +0000</pubDate>
		<dc:creator>CharlyBr</dc:creator>
				<category><![CDATA[http]]></category>
		<category><![CDATA[nginx]]></category>

		<guid isPermaLink="false">http://charles.lescampeurs.org/?p=164</guid>
		<description><![CDATA[server { server_name domain.com; rewrite ^(.*)$ http://www.domain.com$1 permanent; }]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fcharles.lescampeurs.org%2F2009%2F03%2F20%2Fpermanent-redirect-with-nginx"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fcharles.lescampeurs.org%2F2009%2F03%2F20%2Fpermanent-redirect-with-nginx&amp;style=normal" height="61" width="50" /><br />
			</a>
		</div>
<pre>server {
    server_name domain.com;
    rewrite ^(.*)$ http://www.domain.com$1 permanent;
}</pre>
]]></content:encoded>
			<wfw:commentRss>http://charles.lescampeurs.org/2009/03/20/permanent-redirect-with-nginx/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Nginx and worker_connections are more than open file resource limit warning</title>
		<link>http://charles.lescampeurs.org/2009/03/09/nginx-and-worker_connections-are-more-than-open-file-resource-limit-warning</link>
		<comments>http://charles.lescampeurs.org/2009/03/09/nginx-and-worker_connections-are-more-than-open-file-resource-limit-warning#comments</comments>
		<pubDate>Mon, 09 Mar 2009 20:30:26 +0000</pubDate>
		<dc:creator>CharlyBr</dc:creator>
				<category><![CDATA[Distro]]></category>
		<category><![CDATA[http]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[nginx]]></category>
		<category><![CDATA[ulimit]]></category>

		<guid isPermaLink="false">http://charles.lescampeurs.org/?p=160</guid>
		<description><![CDATA[If you encounter this warning message under Linux: 2009/03/09 21:23:19 [warn] 26827#0: 4096 worker_connections are more than open file resource limit: 1024 A solution is to use the command ulimit in nginx start script, just before lunching nginx: [...] ulimit  -n 65536 [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fcharles.lescampeurs.org%2F2009%2F03%2F09%2Fnginx-and-worker_connections-are-more-than-open-file-resource-limit-warning"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fcharles.lescampeurs.org%2F2009%2F03%2F09%2Fnginx-and-worker_connections-are-more-than-open-file-resource-limit-warning&amp;style=normal" height="61" width="50" /><br />
			</a>
		</div>
<p>If you encounter this warning message under Linux:</p>
<pre>2009/03/09 21:23:19 [warn] 26827#0: 4096 worker_connections are more than open file resource limit: 1024</pre>
<p>A solution is to use the command ulimit in nginx start script, just before lunching nginx:</p>
<pre>[...]
ulimit  -n 65536
[...]</pre>
]]></content:encoded>
			<wfw:commentRss>http://charles.lescampeurs.org/2009/03/09/nginx-and-worker_connections-are-more-than-open-file-resource-limit-warning/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Fix nginx increase server_names_hash_bucket_size error</title>
		<link>http://charles.lescampeurs.org/2008/11/14/fix-nginx-increase-server_names_hash_bucket_size</link>
		<comments>http://charles.lescampeurs.org/2008/11/14/fix-nginx-increase-server_names_hash_bucket_size#comments</comments>
		<pubDate>Fri, 14 Nov 2008 09:28:10 +0000</pubDate>
		<dc:creator>CharlyBr</dc:creator>
				<category><![CDATA[http]]></category>
		<category><![CDATA[nginx]]></category>

		<guid isPermaLink="false">http://charles.lescampeurs.org/?p=112</guid>
		<description><![CDATA[When adding new virtual hosts in your nginx configuration file, you can experience this error message: # nginx -t 2008/11/13 09:37:03 [emerg] 12299#0: could not build the server_names_hash, you should increase server_names_hash_bucket_size: 32 2008/11/13 09:37:03 [emerg] 12299#0: the configuration file /etc/nginx/nginx.conf test failed server_names_hash_bucket_size controls the maximum length of a virtual host entry (ie the [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fcharles.lescampeurs.org%2F2008%2F11%2F14%2Ffix-nginx-increase-server_names_hash_bucket_size"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fcharles.lescampeurs.org%2F2008%2F11%2F14%2Ffix-nginx-increase-server_names_hash_bucket_size&amp;style=normal" height="61" width="50" /><br />
			</a>
		</div>
<p>When adding new virtual hosts in your nginx configuration file, you can experience this error message:</p>
<pre># nginx -t
2008/11/13 09:37:03 [emerg] 12299#0: could not build the server_names_hash, you should increase server_names_hash_bucket_size: 32
2008/11/13 09:37:03 [emerg] 12299#0: the configuration file /etc/nginx/nginx.conf test failed</pre>
<p><em><a href="http://wiki.codemongers.com/NginxHttpCoreModule#server_names_hash_bucket_size" target="_blank">server_names_hash_bucket_size</a></em> controls the maximum length of a virtual host entry (ie the length of the domain name).</p>
<p>In other words, if your domain names are long, increase this parameter.</p>
<p>You need to add this flag in the <em>http</em> context:</p>
<pre>http {
    server_names_hash_bucket_size 64;
    ...
}</pre>
<p>After increasing the value, test your configuration file and reload nginx:</p>
<pre># nginx -t
2008/11/13 09:48:06 [info] 12315#0: the configuration file /etc/nginx/nginx.conf syntax is ok
2008/11/13 09:48:06 [info] 12315#0: the configuration file /etc/nginx/nginx.conf was tested successfully
# kill -HUP `cat /var/run/nginx.pid`</pre>
]]></content:encoded>
			<wfw:commentRss>http://charles.lescampeurs.org/2008/11/14/fix-nginx-increase-server_names_hash_bucket_size/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Rotate Nginx log files under FreeBSD</title>
		<link>http://charles.lescampeurs.org/2008/07/17/rotate-nginx-log-files-under-freebsd</link>
		<comments>http://charles.lescampeurs.org/2008/07/17/rotate-nginx-log-files-under-freebsd#comments</comments>
		<pubDate>Thu, 17 Jul 2008 05:15:12 +0000</pubDate>
		<dc:creator>CharlyBr</dc:creator>
				<category><![CDATA[Logs]]></category>
		<category><![CDATA[FreeBSD]]></category>
		<category><![CDATA[newsyslog]]></category>
		<category><![CDATA[nginx]]></category>

		<guid isPermaLink="false">http://charles.lescampeurs.org/?p=27</guid>
		<description><![CDATA[To rotate your nginx log files, you can use the log file handler provided by FreeBSD: newsyslog. Configuring /etc/newsyslog.conf /var/log/nginx-access.log               644  7     1024 *     JC /var/run/nginx.pid /var/log/nginx-error.log                644  7     1024 *     JC /var/run/nginx.pid Before log rotation: -rw-r--r--  1 root  wheel    104278002 Jul 16 11:35 nginx-access.log -rw-r--r--  1 root  wheel      1509531 Jul 16 11:17 nginx-error.log After [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fcharles.lescampeurs.org%2F2008%2F07%2F17%2Frotate-nginx-log-files-under-freebsd"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fcharles.lescampeurs.org%2F2008%2F07%2F17%2Frotate-nginx-log-files-under-freebsd&amp;style=normal" height="61" width="50" /><br />
			</a>
		</div>
<p>To rotate your nginx log files, you can use the log file handler provided by FreeBSD: newsyslog.</p>
<h2>Configuring /etc/newsyslog.conf</h2>
<pre>/var/log/nginx-access.log               644  7     1024 *     JC /var/run/nginx.pid
/var/log/nginx-error.log                644  7     1024 *     JC /var/run/nginx.pid</pre>
<p>Before log rotation:</p>
<pre>-rw-r--r--  1 root  wheel    104278002 Jul 16 11:35 nginx-access.log
-rw-r--r--  1 root  wheel      1509531 Jul 16 11:17 nginx-error.log</pre>
<p>After log rotation:</p>
<pre>-rw-r--r--  1 root  wheel        967 Jul 16 12:42 nginx-access.log
-rw-r--r--  1 root  wheel    5310443 Jul 16 12:41 nginx-access.log.0.bz2
-rw-r--r--  1 root  wheel         77 Jul 16 12:41 nginx-error.log
-rw-r--r--  1 root  wheel      37552 Jul 16 12:41 nginx-error.log.0.bz2</pre>
<h2>Links</h2>
<ul>
<li><a title="FreeBSD newsyslog man page" href="http://www.freebsd.org/cgi/man.cgi?query=newsyslog&amp;sektion=8&amp;apropos=0&amp;manpath=FreeBSD+7.0-RELEASE" target="_blank">newsyslog man page</a></li>
<li><a title="FreeBSD newsyslog.conf man page" href="http://www.freebsd.org/cgi/man.cgi?query=newsyslog.conf&amp;sektion=5&amp;apropos=0&amp;manpath=FreeBSD+7.0-RELEASE" target="_blank">newsyslog.conf man page</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://charles.lescampeurs.org/2008/07/17/rotate-nginx-log-files-under-freebsd/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
