Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[lvs\-users\]\s+real_server\s+on\s+the\s+same\s+machine\s+where\s+keepalived\s+runs\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[lvs\-users\]\s+real_server\s+on\s+the\s+same\s+machine\s+where\s+keepalived\s+runs\s*$/: 3 ]

Total 3 documents matching your query.

1. Re: [lvs-users] real_server on the same machine where keepalived runs (score: 1): Author: "SJ Stanaitis" <sj.stanaitis@xxxxxxxxxxxx>; Date: Mon, 14 Nov 2011 08:43:25 -0500; I've done that before I actually had a dedicated LVS box running. I only used a standard TCP check at the time (port open, server up, port closed, server down). We had keepalived running on 2 boxes.; /html/lvs-users/2011-11/msg00002.html (11,269 bytes)
2. Re: [lvs-users] real_server on the same machine where keepalived runs (score: 1): Author: dousti <dousti@xxxxxxxxx>; Date: Sun, 30 Oct 2011 12:44:39 -0700 (PDT); Hi, I played with it some more and this is what I'm seeing. When .157 owns the VIP, regardless of the outcome of the MISC_CHECK (even when .157 check fails) the request is being sent to .157. This of; /html/lvs-users/2011-10/msg00049.html (11,068 bytes)
3. [lvs-users] real_server on the same machine where keepalived runs (score: 1): Author: dousti <dousti@xxxxxxxxx>; Date: Fri, 28 Oct 2011 11:36:52 -0700 (PDT); Hi, I have two hosts (10.175.151.157/22 and 10.175.151.158/22) that run a udp service. In order to provide HA, I'm using keepalived (10.175.148.242/22) on these two hosts. This is the conf of one of; /html/lvs-users/2011-10/msg00048.html (9,830 bytes)

Current List: 1 - 3
Page: [1]