Hi Willy,
sorry it was my mistake, i checked this morning and saw i made a mistake
in the listen backend, since there are over 50.
kind regards,
Robbie
On 13/08/09 22:41, Willy Tarreau wrote:
On Thu, Aug 13, 2009 at 01:13:24PM +0200, Robbie Aelter wrote:
Hi,
we seem to get 504 errors. I have found the solution, we just increase
the timeout server variable to a higher value.
But the problem seems to be that I can't seem to do it per listen
instance and have a general timeout server configured in the defaults
section.
defaults ...
timeout server 60s
...
listen ...
timeout server 1200s
...
The defaults seems to get the upperhand. Did I do something wrong or
does the default overwrite the one in the listen section?
No, you're proceeding the right way. Are you really sure about
your observations ? What do you see in the logs for timeouted
connections ?
Willy
--
Robbie Aelter
System/Network Engineer
NETLOG NV
Emile Braunplein 18
B-9000 Gent
http://corporate.netlog.com/
Tel +32 2 400 43 21
Fax +32 2 400 43 20
[email protected]
http://netlog.com/robbieaelter
