cache file has too long header error

[turquaze]

hello, I have a problem.

2016/06/07 12:42:06 [crit] 2235#0: *72867 cache file "/var/cache/nginx/22/b42e51079b94f043787c9a1b2bfa7ssd2" has too long header, client: 213.52.129.80, server: sitename.com, request: "GET /page/45 HTTP/1.1", host: "sitename.com", referrer: "http://sitename.com/page/44"

errorlog

help me.

nginx.conf

Code: Select all

user                    nginx;
worker_processes auto;
worker_rlimit_nofile 16384;
error_log               /var/log/nginx/error.log;
pid                     /var/run/nginx.pid;

# Worker config
events {
        worker_connections  4096;
        use                 epoll;
}


http {
    # Main settings
    sendfile                        on;
    tcp_nopush                      on;
    tcp_nodelay                     on;
    client_header_timeout           1m;
    client_body_timeout             1m;
    client_header_buffer_size       2k;
    client_body_buffer_size         256k;
    client_max_body_size            100m;
    large_client_header_buffers     4   8k;
    send_timeout                    30;
    keepalive_timeout               60 60;
    reset_timedout_connection       on;
    server_tokens                   off;
	server_name_in_redirect         off;
    server_names_hash_max_size      512;
    server_names_hash_bucket_size   512;


    # Log format
    log_format  main    '$remote_addr - $remote_user [$time_local] $request '
                        '"$status" $body_bytes_sent "$http_referer" '
                        '"$http_user_agent" "$http_x_forwarded_for"';
    log_format  bytes   '$body_bytes_sent';
    #access_log          /var/log/nginx/access.log  main;
    access_log off;


    # Mime settings
    include             /etc/nginx/mime.types;
    default_type        application/octet-stream;


    # Compression
    gzip                on;
    gzip_comp_level     9;
    gzip_min_length     512;
    gzip_buffers        8 64k;
    gzip_types          text/plain text/css text/javascript
                        application/x-javascript;
    gzip_proxied        any;


    # Proxy settings
    proxy_redirect      off;
    proxy_set_header    Host            $host;
    proxy_set_header    X-Real-IP       $remote_addr;
    proxy_set_header    X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_pass_header   Set-Cookie;
    proxy_connect_timeout   90;
    proxy_send_timeout  90;
    proxy_read_timeout  300;
	proxy_buffers       32 4k;

[tjebbeke]

https://forum.nginx.org/read.php?2,2615 ... msg-261568

The message is logged when nginx detects the problem, ignores the
cached file and starts loading another response from an upstream
server. So, unfortunately, as long as the message appeared, it's
probably too late to look into the file as it's likely already
reloaded from a backend.

The message itself is expected to appear if a response header
stored in the cache file is too big for configured
proxy_buffer_size. It may also appear due to a small race
condition in nginx cache logic if two different responses are
loaded into cache simultaneously, see here:

http://hg.nginx.org/nginx/rev/6f97afc238de
http://mailman.nginx.org/pipermail/ngin ... 01287.html

The message may also indicates that the cache file was corrupted
somehow.

If you see the message on a regular basis, we may want to
investigate further. If it's just a single case in couple of
months, it is probably due to the race condition in question and
likely can be ignored safely.

[turquaze]

https://forum.nginx.org/read.php?2,2615 ... msg-261568

The message is logged when nginx detects the problem, ignores the
cached file and starts loading another response from an upstream
server. So, unfortunately, as long as the message appeared, it's
probably too late to look into the file as it's likely already
reloaded from a backend.

The message itself is expected to appear if a response header
stored in the cache file is too big for configured
proxy_buffer_size. It may also appear due to a small race
condition in nginx cache logic if two different responses are
loaded into cache simultaneously, see here:

http://hg.nginx.org/nginx/rev/6f97afc238de
http://mailman.nginx.org/pipermail/ngin ... 01287.html

The message may also indicates that the cache file was corrupted
somehow.

If you see the message on a regular basis, we may want to
investigate further. If it's just a single case in couple of
months, it is probably due to the race condition in question and
likely can be ignored safely.

proxy_buffer_size value what should I do?

[tjebbeke]

How many times do you have this error? Do you have this always or every time?
If you had this error just one time, you can ignore it. If you have this error many times, you can add or change the proxy_buffer_size parameter in you nginx config.

[turquaze]

thank you bro.

daily 5-10 piece :/