Hey Cliff,<div><br></div><div>I did, same issue.  The way we ended up "fixing" it was deleting all of the vhosts and syncing them from another PoP.</div><div><br></div><div>Thanks<br clear="all"><span style="border-collapse:collapse;font-family:arial,sans-serif;font-size:13px"><div>
<span style="border-collapse:collapse;font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="border-collapse:collapse;font-family:arial,sans-serif;font-size:13px">Reg</span>ards,</div><div><br></div>
<a href="http://www.twitter.com/jdorfman" target="_blank">Justin Dorfman</a></span><br>
<br><br><div class="gmail_quote">On Thu, Mar 29, 2012 at 6:41 PM, Cliff Wells <span dir="ltr"><<a href="mailto:cliff@develix.com">cliff@develix.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Thu, 2012-03-29 at 17:11 -0700, Justin Dorfman wrote:<br>
<br>
> nginx: [emerg] could not build the referers_hash, you should increase<br>
> referers_hash_bucket_size: 64<br>
<br>
<br>
</div>I hate to ask the obvious, but did you try increasing<br>
referers_hash_bucket_size?<br>
<br>
server {<br>
    referers_hash_bucket_size 128;<br>
}<br>
<br>
This variable seems undocumented (aside from a note it appeared in<br>
1.0.5), but the error message appears helpful enough.<br>
<br>
Regards,<br>
Cliff<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
<a href="http://mailman.nginx.org/mailman/listinfo/nginx" target="_blank">http://mailman.nginx.org/mailman/listinfo/nginx</a><br>
</blockquote></div><br></div>