atom feed10 messages in ru.sysoev.nginxRe: could not build the referers_hash
FromSent OnAttachments
Justin DorfmanMar 29, 2012 5:11 pm 
Cliff WellsMar 29, 2012 6:41 pm 
Justin DorfmanMar 29, 2012 7:03 pm 
Cliff WellsMar 30, 2012 8:16 am 
Justin DorfmanMar 30, 2012 9:08 am 
Cliff WellsMar 30, 2012 2:49 pm 
Justin DorfmanApr 9, 2012 12:49 pm 
Maxim DouninApr 10, 2012 4:15 am 
Ryan BrownApr 10, 2012 6:52 am 
Maxim DouninApr 10, 2012 7:43 am 
Subject:Re: could not build the referers_hash
From:Cliff Wells (cli@develix.com)
Date:Mar 30, 2012 8:16:41 am
List:ru.sysoev.nginx

On Thu, 2012-03-29 at 19:04 -0700, Justin Dorfman wrote:

Hey Cliff,

I did, same issue. The way we ended up "fixing" it was deleting all of the vhosts and syncing them from another PoP.

How large did you make the value? With a large number of vhosts the value might need to be significantly higher. Also, I'm not sure of the context for this value, it might need to be at the http level.

There's also a related value, referers_hash_bucket_size that might need to be increased.

The only information I found was from this thread (translated from Russian via google):

2011/7/19 Igor Sysoev <igor@xxxxxxxxx>:

Changes in nginx 1.0.5 19.07.2011

*) Feature: the referer_hash_max_size and Referer_hash_bucket_size. Thank you Witold Filipczyk.

With these guidelines, there are some problems: - In the error messages as they are called, and referers_hash_max_size referers_hash_bucket_size - The default value for referer_hash_max_size in the error message described as a 128 (actually - 2048) - It is not clear how to find exactly where the problem that is, such as the diagnosis is nginx: [emerg] could not build the referers_hash, you should increase referers_hash_bucket_size: 64 But that's not enough, as the context for referer_hash_max_size server and location

Regards, Cliff

_______________________________________________ nginx mailing list ngi@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx