Welcome! Log In Create A New Profile

Advanced

Re: Debugging 504 Gateway Timeout and its actual cause and solution

January 04, 2016 08:53AM
Here are some of the timeouts already defined :

Under server wide nginx.conf :

keepalive_timeout 5;
send_timeout 150;

under specific vhost.conf :

proxy_send_timeout 100;
proxy_read_timeout 100;
proxy_connect_timeout 100;
fastcgi_connect_timeout 120;
fastcgi_send_timeout 300;
fastcgi_read_timeout 300;

Different values for timeouts are used so I can figured out which timeout was exactly triggered.

Below are some of the settings from sysctl.conf :

net.ipv4.ip_local_port_range = 1024 65500
net.ipv4.tcp_fin_timeout = 10
net.ipv4.tcp_tw_reuse = 1
net.ipv4.tcp_syn_retries = 6
net.core.netdev_max_backlog = 8192
net.ipv4.tcp_max_tw_buckets = 2000000
net.core.somaxconn = 4096
net.ipv4.tcp_no_metrics_save = 1
vm.max_map_count = 256000


Thanks!
Subject Author Posted

Debugging 504 Gateway Timeout and its actual cause and solution

Keyur January 04, 2016 08:34AM

Re: Debugging 504 Gateway Timeout and its actual cause and solution

Keyur January 04, 2016 08:53AM

Re: Debugging 504 Gateway Timeout and its actual cause and solution

Richard Stanway January 04, 2016 09:12AM

Re: Debugging 504 Gateway Timeout and its actual cause and solution

Keyur January 06, 2016 02:56AM

Re: Debugging 504 Gateway Timeout and its actual cause and solution

Maxim Dounin January 08, 2016 11:36AM

Re: Debugging 504 Gateway Timeout and its actual cause and solution

Keyur January 11, 2016 12:51AM

Re: Debugging 504 Gateway Timeout and its actual cause and solution

itpp2012 January 04, 2016 09:34AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 196
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready