Runbook

Nginx Pod Crash due to Server Names Hash Bucket Size Error.

Back to Runbooks

Overview

This incident type refers to a situation where an nginx pod crashes after deployment due to the error message "[emerg] could not build the server_names_hash, you should increase server_names_hash_bucket_size: 64". This error occurs when the server_names_hash_bucket_size parameter in the nginx configuration file is set to a value that is too small to accommodate all the server names. As a result, nginx is unable to build the server names hash table, leading to a crash of the nginx pod. This incident can be resolved by increasing the server_names_hash_bucket_size parameter in the nginx configuration file to a power of two value that is sufficient to hold the longest server name.

Parameters

Debug

List all pods in the namespace where the incident occurred

Describe the nginx pod to see its current status and events

Check the logs of the pod to see if there are any errors or warnings

Check the nginx configuration file configmap to verify the server_names_hash_bucket_size value

Repair

Increase the server_names_hash_bucket_size in the nginx configuration. This can be done by modifying the nginx.conf file or the configuration file for the specific pod that is crashing.

Learn more

Related Runbooks

Check out these related runbooks to help you debug and resolve similar issues.