nginx error : cache file has too long header
omkar_jadhav_20
nginx-forum at forum.nginx.org
Wed Dec 7 07:02:32 UTC 2016
Hi ,
We are getting too many Cache file has too long header errors in nginx
error.log file. Some servers are getting such error as many as 273 times a
day.
Below is sample nginx file in our environment :
worker_processes auto;
events {
worker_connections 4096;
use epoll;
multi_accept on;
}
worker_rlimit_nofile 100001;
http {
include mime.types;
default_type video/mp4;
proxy_buffering on;
proxy_buffer_size 4096k;
proxy_buffers 5 4096k;
sendfile on;
keepalive_timeout 30;
tcp_nodelay on;
tcp_nopush on;
reset_timedout_connection on;
gzip off;
server_tokens off;
log_format access '$remote_addr $http_x_forwarded_for $host [$time_local] '
'$upstream_cache_status ' '"$request" $status $body_bytes_sent '
'"$http_referer" "$http_user_agent" $request_time' ' Patna
sptnacdnds01.cdnsrv.jio.com sptnacdnds01 DS';
proxy_cache_path /cache/11452 keys_zone=a11452:8m levels=1:2 max_size=50g
inactive=10m;
proxy_cache_path /cache/11506 keys_zone=a11506:8m levels=1:2 max_size=50g
inactive=10m;
proxy_cache_path /cache/12151 keys_zone=a12151:200m levels=1:2
max_size=100g inactive=10m;
proxy_cache_path /cache/12053 keys_zone=a12053:200m levels=1:2
max_size=50g inactive=10m;
proxy_cache_path /cache/11502 keys_zone=a11502:50m levels=1:2
max_size=200g inactive=10d;
proxy_cache_path /cache/11503 keys_zone=a11503:50m levels=1:2
max_size=200g inactive=10d;
proxy_cache_path /cache/11504 keys_zone=a11504:50m levels=1:2
max_size=200g inactive=10d;
proxy_cache_path /cache/11505 keys_zone=a11505:50m levels=1:2
max_size=200g inactive=10d;
proxy_cache_path /cache/11507 keys_zone=a11507:50m levels=1:2
max_size=200g inactive=10d;
proxy_cache_path /cache/12202 keys_zone=a12202:200m levels=1:2
max_size=200g inactive=10d;
proxy_cache_path /cache/12201 keys_zone=a12201:200m levels=1:2
max_size=200g inactive=10d;
proxy_cache_path /cache/12003 keys_zone=a12003:200m levels=1:2
max_size=700g inactive=10d;
proxy_cache_path /cache/12008 keys_zone=a12008:300m levels=1:2
max_size=20g inactive=10d;
proxy_cache_path /cache/12007 keys_zone=a12007:200m levels=1:2
max_size=200g inactive=10d;
proxy_cache_path /cache/12152 keys_zone=a12152:200m levels=1:2
max_size=700g inactive=10d;
proxy_cache_path /cache/12005 keys_zone=a12005:200m levels=1:2
max_size=100g inactive=10d;
proxy_cache_path /cache/12153 keys_zone=a12153:200m levels=1:2
max_size=100g inactive=10d;
proxy_cache_path /cache/12006 keys_zone=a12006:200m levels=1:2
max_size=100g inactive=10d;
proxy_cache_path /cache/11501 keys_zone=a11501:50m levels=1:2
max_size=200g inactive=10d;
proxy_cache_path /cache/12054 keys_zone=a12054:200m levels=1:2
max_size=500g inactive=3d;
proxy_cache_path /cache/12251 keys_zone=a12251:200m levels=1:2
max_size=200g inactive=15m;
proxy_cache_path /cache/12252 keys_zone=a12252:200m levels=1:2
max_size=200g inactive=10d;
proxy_cache_path /cache/12301 keys_zone=a12301:200m levels=1:2
max_size=200g inactive=10d;
Please suggest some solution.
Posted at Nginx Forum: https://forum.nginx.org/read.php?2,271382,271382#msg-271382
More information about the nginx
mailing list