You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you use a public EC2 name e.g. ec2-52-36-198-136.us-west-2.compute.amazonaws.com for the fqdn_api in chef-server.rb and the fqdn in manage.rb then nginx won't start and shows in the logs:
2016-02-17_13:29:17.97029 nginx: [emerg] could not build the server_names_hash, you should increase server_names_hash_bucket_size: 64
If you use a public EC2 name e.g.
ec2-52-36-198-136.us-west-2.compute.amazonaws.com
for thefqdn_api
inchef-server.rb
and thefqdn
inmanage.rb
then nginx won't start and shows in the logs:2016-02-17_13:29:17.97029 nginx: [emerg] could not build the server_names_hash, you should increase server_names_hash_bucket_size: 64
This already was patched in chef-analytics with an insightful comment added at https://github.com/chef/chef-analytics/blob/master/omnibus/files/cookbooks/opscode-analytics/templates/default/nginx/analytics.conf.erb#L24-L27.
We should do the needful.
The text was updated successfully, but these errors were encountered: