Hello.
Thanks for your reply.
Of cource, heartbeat is started.
Normal log shows:
heartbeat[9111]: 2009/02/14_16:28:01 WARN: Core dumps could be lost if multiple
dumps occur.
heartbeat[9111]: 2009/02/14_16:28:01 WARN: Consider setting non-default value
in /proc/sys/kernel/core_pattern (or equivalent) for maximum supportability
heartbeat[9111]: 2009/02/14_16:28:01 WARN: Consider setting
/proc/sys/kernel/core_uses_pid (or equivalent) to 1 for maximum supportability
heartbeat[9111]: 2009/02/14_16:28:01 info: Version 2 support: false
heartbeat[9111]: 2009/02/14_16:28:01 WARN: Logging daemon is disabled
--enabling logging daemon is recommended
heartbeat[9111]: 2009/02/14_16:28:01 info: **************************
heartbeat[9111]: 2009/02/14_16:28:01 info: Configuration validated. Starting
heartbeat 2.1.3
heartbeat[9112]: 2009/02/14_16:28:01 info: heartbeat: version 2.1.3
heartbeat[9112]: 2009/02/14_16:28:01 info: Heartbeat generation: 1234325819
heartbeat[9112]: 2009/02/14_16:28:01 info: glib: UDP Broadcast heartbeat
started on port 694 (694) interface eth0
heartbeat[9112]: 2009/02/14_16:28:01 info: glib: UDP Broadcast heartbeat closed
on port 694 interface eth0 - Status: 1
heartbeat[9112]: 2009/02/14_16:28:01 info: glib: UDP multicast heartbeat
started for group 225.0.0.1 port 694 interface eth0 (ttl=1 loop=0)
heartbeat[9112]: 2009/02/14_16:28:01 info: G_main_add_TriggerHandler: Added
signal manual handler
heartbeat[9112]: 2009/02/14_16:28:01 info: G_main_add_TriggerHandler: Added
signal manual handler
heartbeat[9112]: 2009/02/14_16:28:01 info: G_main_add_SignalHandler: Added
signal handler for signal 17
heartbeat[9112]: 2009/02/14_16:28:01 info: Comm_now_up(): updating status to
active
heartbeat[9112]: 2009/02/14_16:28:01 info: Local status now set to: 'active'
heartbeat[9112]: 2009/02/14_16:28:01 info: Starting child client
"/usr/lib/heartbeat/ipfail" (105,107)
heartbeat[9112]: 2009/02/14_16:28:01 info: Local status now set to: 'up'
heartbeat[9120]: 2009/02/14_16:28:01 info: Starting "/usr/lib/heartbeat/ipfail"
as uid 105 gid 107 (pid 9120)
heartbeat[9112]: 2009/02/14_16:28:02 info: Link loadb1:eth0 up.
ipfail[9120]: 2009/02/14_16:28:05 info: Link Status update: Link loadb1/eth0
now has status up
Debug log:
heartbeat[9111]: 2009/02/14_16:28:01 WARN: Core dumps could be lost if multiple
dumps occur.
heartbeat[9111]: 2009/02/14_16:28:01 WARN: Consider setting non-default value
in /proc/sys/kernel/core_pattern (or equivalent) for maximum supportability
heartbeat[9111]: 2009/02/14_16:28:01 WARN: Consider setting
/proc/sys/kernel/core_uses_pid (or equivalent) to 1 for maximum supportability
heartbeat[9111]: 2009/02/14_16:28:01 info: Version 2 support: false
heartbeat[9111]: 2009/02/14_16:28:01 WARN: Logging daemon is disabled
--enabling logging daemon is recommended
heartbeat[9111]: 2009/02/14_16:28:01 info: **************************
heartbeat[9111]: 2009/02/14_16:28:01 info: Configuration validated. Starting
heartbeat 2.1.3
heartbeat[9112]: 2009/02/14_16:28:01 info: heartbeat: version 2.1.3
heartbeat[9112]: 2009/02/14_16:28:01 info: Heartbeat generation: 1234325819
heartbeat[9112]: 2009/02/14_16:28:01 info: glib: UDP Broadcast heartbeat
started on port 694 (694) interface eth0
heartbeat[9112]: 2009/02/14_16:28:01 info: glib: UDP Broadcast heartbeat closed
on port 694 interface eth0 - Status: 1
heartbeat[9112]: 2009/02/14_16:28:01 info: glib: UDP multicast heartbeat
started for group 225.0.0.1 port 694 interface eth0 (ttl=1 loop=0)
heartbeat[9112]: 2009/02/14_16:28:01 info: G_main_add_TriggerHandler: Added
signal manual handler
heartbeat[9112]: 2009/02/14_16:28:01 info: G_main_add_TriggerHandler: Added
signal manual handler
heartbeat[9112]: 2009/02/14_16:28:01 info: G_main_add_SignalHandler: Added
signal handler for signal 17
heartbeat[9112]: 2009/02/14_16:28:01 info: Comm_now_up(): updating status to
active
heartbeat[9112]: 2009/02/14_16:28:01 info: Local status now set to: 'active'
heartbeat[9112]: 2009/02/14_16:28:01 info: Starting child client
"/usr/lib/heartbeat/ipfail" (105,107)
heartbeat[9112]: 2009/02/14_16:28:01 info: Local status now set to: 'up'
heartbeat[9120]: 2009/02/14_16:28:01 info: Starting "/usr/lib/heartbeat/ipfail"
as uid 105 gid 107 (pid 9120)
ipfail[9120]: 2009/02/14_16:28:01 debug: PID=9120
ipfail[9120]: 2009/02/14_16:28:01 debug: Signing in with heartbeat
ipfail[9120]: 2009/02/14_16:28:01 debug: [We are loadb1]
ipfail[9120]: 2009/02/14_16:28:02 debug: auto_failback -> 0 (off)
heartbeat[9112]: 2009/02/14_16:28:02 info: Link loadb1:eth0 up.
ipfail[9120]: 2009/02/14_16:28:02 debug: Setting message filter mode
ipfail[9120]: 2009/02/14_16:28:02 debug: Starting node walk
ipfail[9120]: 2009/02/14_16:28:03 debug: Cluster node: loadb1: status: up
ipfail[9120]: 2009/02/14_16:28:03 debug: Setting message signal
ipfail[9120]: 2009/02/14_16:28:04 debug: Waiting for messages...
ipfail[9120]: 2009/02/14_16:28:05 info: Link Status update: Link loadb1/eth0
now has status up
BUT, ldirector log shows:
[Sat Feb 14 16:28:01 2009|ldirectord.cf|9098] Invoking ldirectord invoked as:
/etc/ha.d/resource.d/ldirectord ldirectord.cf status
[Sat Feb 14 16:28:01 2009|ldirectord.cf|9098] Exiting with exit_status 3:
Exiting from ldirectord status
...when heartbeat is started...when I want to get it running, I must
run it from /etc/init.d/ldirectord start
Graeme, dňa 14. februára 2009 ste napísali:
GF> On Sat, 2009-02-14 at 13:58 +0100, Marek Soha wrote:
>> The problem is, that ldirectord dont add virtual IP address to
>> interface from config.
GF> ldirectord doesn't add the VIP to the interface. Heartbeat does that.
GF> Did you start heartbeat? If so, what do the log say?
GF> Graeme
GF> __________ Informacia od NOD32 3136 (20080527) __________
GF> Tato sprava bola preverena antivirusovym systemom NOD32.
GF> http://www.eset.sk
---------------=[**]=-----------------
S prianim pekneho dna
\\\\|////
\\ _ _ //
( o o )
+==========oOOo-(_)-oOOo==========+
Marek Soha
marek@xxxxxxx
snet.sk network administrator
ICQ 146-284-791
MSN spam@xxxxxxx
+==================Oooo===========+
oooO ( )
( ) ) /
\ ( (_/
\_)
_______________________________________________
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
|