On 2010/10/17 10:19, Kevin Chadwick wrote:
> On Mon, 18 Oct 2010 02:09:14 -0600 (MDT)
> [email protected] wrote:
>
> > Synopsis: relayd check https - ssl read timeout
> >
> > State-Changed-From-To: open->closed
> > State-Changed-By: pyr
> > State-Changed-When: Mon Oct 18 02:08:14 MDT 2010
> > State-Changed-Why:
> > This is not a bug, the default timeout is 200ms which is
> > a bit short for https sessions, the timeout should be
> > set when checking https sessions.
> >
>
> The bug reporter may want to increase it further than tested
> successfully locally for clients from the other side of the world, too.
>
Incoming connections (relays/redirections) have a different timeout
defaulting to 600 seconds:
session timeout seconds
Specify the inactivity timeout in seconds for established
redirections. The default timeout is 600 seconds (10 minutes).
The one defaulting to 200ms is for checks not for incoming connections:
timeout number
Set the global timeout in milliseconds for checks. This can be
overridden by the timeout value in the table definitions. The
default interval is 200 milliseconds and it must not exceed the
global interval. Please note that the default value is optimized
for checks within the same collision domain - use a higher
timeout, such as 1000 milliseconds, for checks of hosts in other
subnets. If this option is to be set, it should be placed before
overrides in tables.
...
check script path
Execute an external program to check the host state. The program
will be executed for each host by specifying the hostname on the
command line:
/usr/local/bin/checkload.pl front-www1.private.example.com
relayd(8) expects a positive return value on success and zero on
failure. Note that the script will be executed with the
privileges of the "_relayd" user and terminated after timeout
milliseconds.
...
timeout number
Set the timeout in milliseconds for each host that is checked
using TCP as the transport. This will override the global
timeout, which is 200 milliseconds by default.
...
