Nginx pod in CrashLoopBackoff because of server_names_hash_bucket_size #408

Closed
opened 2026-04-05 16:19:36 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @jose-yougov on 8/1/2025

Hello!

We have OneUptime deployed to EKS using Helm, we are moving to a new EKS cluster and there the nginx pod is in CrashLoopBackOff because of the following error:

envsubst-on-templates.sh: Running auto_envsubst
envsubst-on-templates.sh: Running envsubst on /etc/nginx/templates/default.conf.template to /etc/nginx/conf.d/default.conf
2025/08/01 09:53:00 [emerg] 18#18: could not build server_names_hash, you should increase server_names_hash_bucket_size: 64
nginx: [emerg] could not build server_names_hash, you should increase server_names_hash_bucket_size: 64

We have tried to figure out how to increase server_names_hash_bucket_size but it seems it's not possible neither in the chart values nor in any configmap since OneUptime's Nginx is a custom container.

According to Nginx documentation: https://nginx.org/en/docs/http/server_names.html

The default value of the server_names_hash_bucket_size directive may be equal to 32, or 64, or another value, depending on CPU cache line size.

Is there any way to set server_names_hash_bucket_size for OneUptime's Nginx (maybe we can pass an environment variable to the container?) so we don't need to use bigger instances for our EKS cluster? We are using r5.large for this cluster just if you found this issue in the past.

Thank you!

*Originally created by @jose-yougov on 8/1/2025* Hello! We have OneUptime deployed to EKS using Helm, we are moving to a new EKS cluster and there the nginx pod is in CrashLoopBackOff because of the following error: ``` envsubst-on-templates.sh: Running auto_envsubst envsubst-on-templates.sh: Running envsubst on /etc/nginx/templates/default.conf.template to /etc/nginx/conf.d/default.conf 2025/08/01 09:53:00 [emerg] 18#18: could not build server_names_hash, you should increase server_names_hash_bucket_size: 64 nginx: [emerg] could not build server_names_hash, you should increase server_names_hash_bucket_size: 64 ``` We have tried to figure out how to increase server_names_hash_bucket_size but it seems it's not possible neither in the chart values nor in any configmap since OneUptime's Nginx is a custom container. According to Nginx documentation: https://nginx.org/en/docs/http/server_names.html The default value of the [server_names_hash_bucket_size](https://nginx.org/en/docs/http/ngx_http_core_module.html#server_names_hash_bucket_size) directive may be equal to 32, or 64, or another value, depending on CPU cache line size. Is there any way to set server_names_hash_bucket_size for OneUptime's Nginx (maybe we can pass an environment variable to the container?) so we don't need to use bigger instances for our EKS cluster? We are using r5.large for this cluster just if you found this issue in the past. Thank you!
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#408