Armin Wolfermann wrote:
If you need a quick workaround duplicate your global timeout in every
forward statement.
That is indeed a working workaround.
However, it seems that nothing is actually loaded.
pfctl -a relayd -s Tables
returns nothing for example.
So maybe there are more things
* Ben Lovett [EMAIL PROTECTED] [23.02.2008 01:22]:
could someone perhaps shed some light on what i'm doing wrong, if
anything? perhaps a bug in the http check/tcp check code?
Looks like a bug in the parser. Table options are not copied to derived
tables. Suggested fix:
Index: parse.y
Brad Arrington [EMAIL PROTECTED] wrote:
Hi,
I ran into the same problem you did, I thought it was something I
was doing wrong until I read your email...
Here is the fix I came up with.
--- check_tcp.c-current Mon Feb 25 15:11:40 2008
+++ check_tcp.c Mon Feb 25 23:48:45 2008
@@ -82,6
: relayd http check connection failures; hoststated operates
correctly
Brad Arrington [EMAIL PROTECTED] wrote:
Hi,
I ran into the same problem you did, I thought it was something I
was doing wrong until I read your email...
Here is the fix I came up with.
--- check_tcp.c-current Mon Feb 25 15
Brad Arrington [EMAIL PROTECTED] wrote:
Hi Pierre-Yves,
I guess we are both wrong...
I used a few different timeout values including 1000 before
changing any code. I just checked relayd(the unpatched version) again
and I get the same results.
These web servers just serve the default
On Wed, Feb 27, 2008 at 11:53:03AM +0100, Pierre-Yves Ritschard wrote:
Your fix is wrong, you run in a timeout which happens because the
default relayd configuration supposes you are in the same broadcast
domain than your relayed host and has a 200ms timeout.
While my relay server isn't in the
On Wed, Feb 27, 2008 at 06:28:40PM +0100, Pierre-Yves Ritschard wrote:
Please try with an insanely high value (10seconds) and see if you still
get a connection timeout message.
To make logging more meaningful you can try with this diff and send me
the relayd -dv output:
I can't set timeout
Hi Ben,
Try changing the interval value to a higher value.
I tested it the results are the same. (with timeout set to 10 seconds)
-Brad
-Original Message-
From: [EMAIL PROTECTED]
Sent: Wed, 27 Feb 2008 11:27:19 -0800
To: [EMAIL PROTECTED]
Subject: Re: relayd http check connection
on gettimeofday but here it is anyway...
I submited a bug report too.
-Brad
-Original Message-
From: [EMAIL PROTECTED]
Sent: Fri, 22 Feb 2008 16:16:29 -0800
To: misc@openbsd.org
Subject: relayd http check connection failures; hoststated operates
correctly
hello,
perhaps it's something
Brad Arrington [EMAIL PROTECTED] wrote:
Hi,
I ran into the same problem you did, I thought it was something I
was doing wrong until I read your email...
Here is the fix I came up with.
--- check_tcp.c-current Mon Feb 25 15:11:40 2008
+++ check_tcp.c Mon Feb 25 23:48:45 2008
@@ -82,6
hello,
perhaps it's something that i'm doing wrong here, or a difference
in the way that relayd works compared to hoststated. but here
goes.. i'm attempting to get relayd configured to replace my existing
hoststated setup, doing layer 7 load balancing of web servers.
what's happening is with
forgot to include system details..
this is:
kern.version=OpenBSD 4.3-beta (GENERIC) #661: Thu Feb 21 15:39:36 MST 2008
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
-ben
12 matches
Mail list logo
