|
This is only clue related to this problem I found in log:
Mon Feb 9 15:10:07 2009|ldirectord|12816] Invoking ldirectord invoked
as: /etc/ha.d/resource.d//ldirectord start
[Mon Feb 9 15:10:07 2009|ldirectord|12816] Starting Linux Director
v1.186-ha-2.1.3 as daemon
[Mon Feb 9 15:10:07 2009|ldirectord|12827] Added virtual server:
192.168.21.150:80
[Mon Feb 9 15:10:07 2009|ldirectord|12827] Added real server:
192.168.20.1:80 (192.168.21.150:80) (Weight set to 3)
[Mon Feb 9 15:10:07 2009|ldirectord|12827] Added real server:
192.168.20.2:80 (192.168.21.150:80) (Weight set to 3)
[Mon Feb 9 15:10:07 2009|ldirectord|12827] Added real server:
192.168.20.3:80 (192.168.21.150:80) (Weight set to 3)
[Mon Feb 9 15:10:08 2009|ldirectord|12905] Invoking ldirectord
invoked as: /etc/ha.d/resource.d//ldirectord status
[Mon Feb 9 15:10:08 2009|ldirectord|12905] ldirectord for
/etc/ha.d/conf/ldirectord.cf is running with pid: 12827
[Mon Feb 9 15:10:08 2009|ldirectord|12905] Exiting from ldirectord status
[Mon Feb 9 15:10:10 2009|ldirectord|12906] Invoking ldirectord
invoked as: /etc/ha.d/resource.d//ldirectord stop
[Mon Feb 9 15:10:10 2009|ldirectord|12827] Purged real server (stop):
192.168.20.1:80 (192.168.21.150:80)
[Mon Feb 9 15:10:10 2009|ldirectord|12827] Purged real server (stop):
192.168.20.2:80 (192.168.21.150:80)
[Mon Feb 9 15:10:10 2009|ldirectord|12827] Purged real server (stop):
192.168.20.3:80 (192.168.21.150:80)
[Mon Feb 9 15:10:10 2009|ldirectord|12827] Purged virtual server
(stop): 192.168.21.150:80
[Mon Feb 9 15:10:10 2009|ldirectord|12827] Linux Director Daemon
terminated on signal: TERM
As fas as I understand, it starts and stops immediately. crm_mon tool
from heartbeat says:
esource Group: group_1
IPaddr_192_168_21_150 (heartbeat::ocf:IPaddr): Started ucplb
IPaddr_192_168_20_25 (heartbeat::ocf:IPaddr): Started ucplb
ldirectord_3 (heartbeat:ldirectord): Stopped
So IP addresses are running properly, ldirector is not.
On Mon, Feb 9, 2009 at 2:33 PM, Dusan Djordjevic
<dusan.djordjevic@xxxxxxxxx> wrote:
> Hi all,
>
> After solving my previous problem today on this list (regarding NAT
> and default gateway) I decided to have following setup:
>
> -2 LVS servers
> -Heartbeat for high availability
> -One floating public IP for service
> -One floating GW IP, to be used by real servers as default gateway.
>
> I set up heartbeat with 2 ip addresses and it works fine. Now I am
> trying to setup ldirectord. This is my configuration file:
>
> checktimeout=3
> checkinterval=1
> quiescent=no
>
> virtual=192.168.21.150:80
> real=192.168.20.1:80 masq 3
> real=192.168.20.2:80 masq 3
> real=192.168.20.3:80 masq 3
> service=http
> request="/shared/info.php"
> receive="192.168.20."
> scheduler=wlc
> persistent=900
> netmask=255.255.255.0
> protocol=tcp
>
> When I start Heartbeat with 2 IP addresses and ldirector manually,
> outside of heartbeat, everything works fine. But when I add ldirectord
> to heartbeat as resource, it fails on startup. Any idea why same setup
> won't work when started from heartbeat, but works standalone ?
>
> TIA
>
_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://lists.graemef.net/mailman/listinfo/lvs-users
|
