Heartbeat--為什麼起動不了haresources裡面的資源?-<已解決>
軟體:heartbeat-2.0.5.tar.gz---------安裝過程沒有問題
我的haresources的主要內容:
Loadbalance IPaddr:192.168.0.20/32/192.168.0.20 lvs mon
說明
Loadbalance----主director的主機名字
192.168.0.20---virtual IP
lvs---/etc/init.d/lvs---一個啟動IPVS規則的腳本文件
mon--/etc/init.d/mon---監視realserver的腳本
特殊說明mon一定要這樣運行才生效:
#/etc/init.d/mon &
而不能
#/etc/init.d/mon start
本人水平非常菜,不能使mon以#/etc/init.d/mon start的方式運行,鬱悶一
lvs可以這樣運行
#/etc/init.d/lvs start
問題:
當我
#/etc/init.d/heartbeat start的時候
root@Loadbalance:/etc/ha.d# /etc/init.d/heartbeat start
Starting High-Availability services:
Done.
但是lvs和mon都沒有運行起來,不知道是什麼原因?
[ 本帖最後由 Linuxcn.com 於 2006-6-27 10:05 編輯 ]
《解決方案》
最好能把你的 ha.cf 還 ha-log 帖上來看看. 不然不知道為什麼.
友性提示 32 位的 netmask 用來做什麼呀?
《解決方案》
Loadbalance的ha.cf:
logfile /var/log/ha-log
logfacility local0
keepalive 2
deadtime 30
initdead 120
udpport 694
ucast eth0 192.168.0.11
auto_failback on
node Loadbalance
node Loadbalance1
而Loadbalance1的ha.cf就只有這句不同,其他都一樣:
ucast eth0 192.168.0.10
haresource現在都改為:
Loadbalance 192.168.0.20 lvs moon
其中,lvs,moon2個服務都在/etc/init.d/目錄下面
我單獨這樣運行:
/etc/init.d/lvs start
/etc/init.d/moon start
ipvsadm的規則,虛擬IP,mon監視程序都可以正常服務的
請老大們幫我看看是那裡出了問題
哦,最後要交代的是,我是在VM上做的實驗,很多帖子上說要用心跳信號,但是我一直不是很理解他們這麼說:
2台director機器都是雙網卡:
192.168.0.10 Loadbalance-----LAN
10.0.0.10 Loadbalance-----心跳信號線
192.168.0.11 Loadbalance1----LAN
10.0.0.11 Loadbalance1----心跳信號線
一個串口線-----也是用來做心跳的.........後面省略若干
既然已經有了心跳線,為什麼還要1個串口線做心跳線呢
而且在ha.cf里他們把
baud 19200
serial /dev/ttyS0 # Linux
bcast eth1 # Linux
mcast eth1 225.0.0.1 694 1 0
都選上了
小弟新手,實在搞的有點糊塗了
[ 本帖最後由 Linuxcn.com 於 2006-6-23 09:32 編輯 ]
《解決方案》
原帖由 q1208c 於 2006-6-22 22:10 發表
最好能把你的 ha.cf 還 ha-log 帖上來看看. 不然不知道為什麼.
友性提示 32 位的 netmask 用來做什麼呀?
不得不承認,小弟是純粹照"本"抄來的,32位的netmask好象是用來做廣播的,我把虛擬IP這樣配置:
ifconfig eth0:0 192.168.0.20 netmask 255.255.255.255 broadcast 192.168.0.20
客戶機是可以正常通過訪問虛擬IP192.168.0.20,得到真實伺服器提供的web服務的,而且LVS的功能也正常
詳情可看小弟的另一個帖子
http://bbs.chinaunix.net/viewthread.php?tid=770597&highlight=Linuxcn.com
原理是什麼,小弟真的不清楚,抱歉
ha-log:
heartbeat: 2006/06/22_09:47:23 WARN: Core dumps could be lost if multiple dumps occur
heartbeat: 2006/06/22_09:47:23 WARN: Consider setting /proc/sys/kernel/core_uses_pid (or equivalent) to 1 for maximum supportability
heartbeat: 2006/06/22_09:47:23 WARN: Logging daemon is disabled --enabling logging daemon is recommended
heartbeat: 2006/06/22_09:47:23 info: **************************
heartbeat: 2006/06/22_09:47:23 info: Configuration validated. Starting heartbeat 2.0.5
heartbeat: 2006/06/22_09:47:23 info: heartbeat: version 2.0.5
heartbeat: 2006/06/22_09:47:23 info: Heartbeat generation: 6
heartbeat: 2006/06/22_09:47:23 info: G_main_add_TriggerHandler: Added signal manual handler
heartbeat: 2006/06/22_09:47:23 info: G_main_add_TriggerHandler: Added signal manual handler
heartbeat: 2006/06/22_09:47:23 info: Removing /var/run/heartbeat/rsctmp failed, recreating.
heartbeat: 2006/06/22_09:47:23 info: glib: ucast: write socket priority set to IPTOS_LOWDELAY on eth0
heartbeat: 2006/06/22_09:47:23 info: glib: ucast: bound send socket to device: eth0
heartbeat: 2006/06/22_09:47:23 info: glib: ucast: bound receive socket to device: eth0
heartbeat: 2006/06/22_09:47:23 info: glib: ucast: started on port 694 interface eth0 to 192.168.0.10
heartbeat: 2006/06/22_09:47:23 info: G_main_add_SignalHandler: Added signal handler for signal 17
heartbeat: 2006/06/22_09:47:23 info: Local status now set to: 'up'
heartbeat: 2006/06/22_09:47:25 info: Link loadbalance:eth0 up.
heartbeat: 2006/06/22_09:47:25 info: Status update for node loadbalance: status active
harc: 2006/06/22_09:47:25 info: Running /etc/ha.d/rc.d/status status
heartbeat: 2006/06/22_09:47:25 info: Comm_now_up(): updating status to active
heartbeat: 2006/06/22_09:47:25 info: Local status now set to: 'active'
heartbeat: 2006/06/22_09:47:26 info: remote resource transition completed.
heartbeat: 2006/06/22_09:47:26 info: remote resource transition completed.
heartbeat: 2006/06/22_09:47:26 info: Local Resource acquisition completed. (none)
heartbeat: 2006/06/22_09:47:26 info: loadbalance wants to go standby
heartbeat: 2006/06/22_09:47:27 info: standby: acquire resources from loadbalance
heartbeat: 2006/06/22_09:47:27 info: acquire local HA resources (standby).
heartbeat: 2006/06/22_09:47:27 info: local HA resource acquisition completed (standby).
heartbeat: 2006/06/22_09:47:27 info: Standby resource acquisition done .
heartbeat: 2006/06/22_09:47:27 info: Initial resource acquisition complete (auto_failback)
heartbeat: 2006/06/22_09:47:27 info: remote resource transition completed.
[ 本帖最後由 Linuxcn.com 於 2006-6-23 09:46 編輯 ]
《解決方案》
最後,順便請教一下大家,
像/usr/bin/mon &這樣運行的服務,我何如把它停掉?
《解決方案》
目前我的能力可能幫不了你太多.
node name 一定要和 uname -n 一樣.
後面那個mon的好象可以自己寫一個script 來處理的.
《解決方案》
原帖由 q1208c 於 2006-6-23 13:03 發表
目前我的能力可能幫不了你太多.
node name 一定要和 uname -n 一樣.
後面那個mon的好象可以自己寫一個script 來處理的.
無論如何,還是要感謝你的建議啦
node name是和uname -n一樣的,也就是主機名
mon我自己已經"抄"+改動,已經可以以/etc/init.d/mon start的方式啟動了,而且監視realserver功能也正常
現在就是如何配雙機的問題
《解決方案》
想了半天,還是決定頂一下.
《解決方案》
ha.cf 里把 ucast eth0 192.168.0.11 換成 bcast eth0
haresources 變成 「Loadbalance 192.168.0.20"
你的 uname -n 的結果是 "loadbalance" 還是 "Loadbalance"? 大小寫要分清。
然後兩邊都起heartbeat. 看看192.168.0.20有沒有起來。
《解決方案》
原帖由 zhenh 於 2006-6-23 22:52 發表
ha.cf 里把 ucast eth0 192.168.0.11 換成 bcast eth0
haresources 變成 「Loadbalance 192.168.0.20"
你的 uname -n 的結果是 "loadbalance" 還是 "Loadbalance"? 大小寫要分清。
...
把haresources 變成 「Loadbalance 192.168.0.20",運行的結果是:
root@Loadbalance:/etc/ha.d# /etc/init.d/heartbeat start
Starting High-Availability services:
2006/06/25_05:56:05 INFO: IPaddr Resource is stopped
Done.
虛擬IP沒起來
而我單獨這樣
root@Loadbalance1:/etc/ha.d/resource.d# ./IPaddr 192.168.0.20 start
2006/06/25_07:15:13 INFO: /sbin/ifconfig eth0:0 192.168.0.20 netmask 255.255.255.0 broadcast 192.168.0.255
2006/06/25_07:15:13 INFO: Sending Gratuitous Arp for 192.168.0.20 on eth0:0
2006/06/25_07:15:13 INFO: /usr/lib/heartbeat/send_arp -i 500 -r 10 -p /var/run/heartbeat/rsctmp/send_arp/send_arp-192.168.0.20 eth0 192.168.0.20 auto 192.168.0.20 ffffffffffff
2006/06/25_07:15:13 INFO: IPaddr Success
INFO: IPaddr Success
再來看log,Loadbalance的log:
heartbeat: 2006/06/25_06:19:32 info: Configuration validated. Starting heartbeat 2.0.5
heartbeat: 2006/06/25_06:19:32 info: heartbeat: version 2.0.5
heartbeat: 2006/06/25_06:19:32 info: Heartbeat generation: 5
heartbeat: 2006/06/25_06:19:32 info: G_main_add_TriggerHandler: Added signal manual handler
heartbeat: 2006/06/25_06:19:32 info: G_main_add_TriggerHandler: Added signal manual handler
heartbeat: 2006/06/25_06:19:32 info: Removing /var/run/heartbeat/rsctmp failed, recreating.
heartbeat: 2006/06/25_06:19:32 info: glib: UDP Broadcast heartbeat started on port 694 (694) interface eth0
heartbeat: 2006/06/25_06:19:32 info: glib: UDP Broadcast heartbeat closed on port 694 interface eth0 - Status: 1
heartbeat: 2006/06/25_06:19:32 info: G_main_add_SignalHandler: Added signal handler for signal 17
heartbeat: 2006/06/25_06:19:32 info: Local status now set to: 'up'
heartbeat: 2006/06/25_06:19:33 info: Link loadbalance:eth0 up.
heartbeat: 2006/06/25_06:20:35 info: Link loadbalance1:eth0 up.
heartbeat: 2006/06/25_06:20:35 info: Status update for node loadbalance1: status up
harc: 2006/06/25_06:20:35 info: Running /etc/ha.d/rc.d/status status
heartbeat: 2006/06/25_06:20:36 info: Comm_now_up(): updating status to active
heartbeat: 2006/06/25_06:20:36 info: Local status now set to: 'active'
heartbeat: 2006/06/25_06:20:36 info: Status update for node loadbalance1: status active
harc: 2006/06/25_06:20:36 info: Running /etc/ha.d/rc.d/status status
heartbeat: 2006/06/25_06:20:47 info: remote resource transition completed.
heartbeat: 2006/06/25_06:20:47 info: remote resource transition completed.
heartbeat: 2006/06/25_06:20:47 info: Initial resource acquisition complete (T_RESOURCES(us))
IPaddr: 2006/06/25_06:20:49 INFO: IPaddr Resource is stopped
heartbeat: 2006/06/25_06:20:49 info: Local Resource acquisition completed.
harc: 2006/06/25_06:20:49 info: Running /etc/ha.d/rc.d/ip-request-resp ip-request-resp
ip-request-resp: 2006/06/25_06:20:49 received ip-request-resp 192.168.0.20 OK yes
ResourceManager: 2006/06/25_06:20:49 info: Acquiring resource group: loadbalance 192.168.0.20 lvs moon
Loadbalance1的log
heartbeat: 2006/06/25_07:33:23 info: Configuration validated. Starting heartbeat 2.0.5
heartbeat: 2006/06/25_07:33:23 info: heartbeat: version 2.0.5
heartbeat: 2006/06/25_07:33:23 info: Heartbeat generation: 13
heartbeat: 2006/06/25_07:33:23 info: G_main_add_TriggerHandler: Added signal manual handler
heartbeat: 2006/06/25_07:33:23 info: G_main_add_TriggerHandler: Added signal manual handler
heartbeat: 2006/06/25_07:33:23 info: Removing /var/run/heartbeat/rsctmp failed, recreating.
heartbeat: 2006/06/25_07:33:23 info: glib: UDP Broadcast heartbeat started on port 694 (694) interface eth0
heartbeat: 2006/06/25_07:33:23 info: glib: UDP Broadcast heartbeat closed on port 694 interface eth0 - Status: 1
heartbeat: 2006/06/25_07:33:23 info: G_main_add_SignalHandler: Added signal handler for signal 17
heartbeat: 2006/06/25_07:33:24 info: Local status now set to: 'up'
heartbeat: 2006/06/25_07:33:25 info: Link loadbalance1:eth0 up.
heartbeat: 2006/06/25_07:33:25 info: Link loadbalance:eth0 up.
heartbeat: 2006/06/25_07:33:25 info: Status update for node loadbalance: status up
heartbeat: 2006/06/25_07:33:25 info: Status update for node loadbalance: status active
heartbeat: 2006/06/25_07:33:25 info: Comm_now_up(): updating status to active
heartbeat: 2006/06/25_07:33:25 info: Local status now set to: 'active'
harc: 2006/06/25_07:33:25 info: Running /etc/ha.d/rc.d/status status
harc: 2006/06/25_07:33:25 info: Running /etc/ha.d/rc.d/status status
看起來應該是正常的啊
這樣是可以的,迷茫中
[ 本帖最後由 Linuxcn.com 於 2006-6-26 10:50 編輯 ]