免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
最近访问板块 发新帖
查看: 3796 | 回复: 0

pacemaker + corosync + heardbeat不能设置IP的问题 [复制链接]

论坛徽章:
0
发表于 2012-09-21 17:46 |显示全部楼层
本帖最后由 ient 于 2012-09-21 17:54 编辑

OS版本:SUSE Linux 12.1
Hearbeat版本:3.0.5
pacemaker版本:1.0.12-1
corosync版本:1.4.1-2.1.3

在suse1节点,添加一个“vip”资源,无法设置IP,“vip”启动失败,“vip”资源自动到suse2节点上启动成功
  1. crm(live)configure# primitive vip ocf:heartbeat:IPaddr params ip=192.168.3.253
  2. crm(live)configure# commit
  3. crm(live)configure# show
  4. node suse1
  5. node suse2
  6. primitive vip ocf:heartbeat:IPaddr \
  7.         params ip="192.168.3.253"
  8. property $id="cib-bootstrap-options" \
  9.         dc-version="1.0.12-unknown" \
  10.         cluster-infrastructure="openais" \
  11.         expected-quorum-votes="2" \
  12.         stonith-enabled="false"
复制代码
添加一个“webserver”,用来启动apache,在suse1和suse2都可以启动成功
  1. crm(live)configure# primitive webserver lsb:apache2
  2. crm(live)configure# commit
  3. crm(live)configure# show
  4. node suse1
  5. node suse2
  6. primitive database ocf:heartbeat:IPaddr \
  7.         params ip="192.168.3.253"
  8. primitive webserver lsb:apache2
复制代码
  1. suse1:~ # crm status
  2. ============
  3. Last updated: Fri Sep 21 17:28:30 2012
  4. Stack: openais
  5. Current DC: suse1 - partition WITHOUT quorum
  6. Version: 1.0.12-unknown
  7. 2 Nodes configured, 2 expected votes
  8. 2 Resources configured.
  9. ============

  10. Online: [ suse1 ]
  11. OFFLINE: [ suse2 ]

  12. webserver      (lsb:apache2):  Started suse1

  13. Failed actions:
  14.     vip_start_0 (node=suse1, call=5, rc=1, status=complete): unknown error
复制代码
在suse2节点上,"vip"启动成功
  1. eth1:0    Link encap:Ethernet  HWaddr 00:1A:64:69:9B:02  
  2.           inet addr:192.168.3.253  Bcast:192.168.255.255  Mask:255.255.0.0
  3.           UP BROADCAST MULTICAST  MTU:1500  Metric:1
  4.           Interrupt:17 Memory:ca000000-ca012800

  5. suse1:~ # crm status
  6. ============
  7. Last updated: Fri Sep 21 17:34:24 2012
  8. Stack: openais
  9. Current DC: suse1 - partition with quorum
  10. Version: 1.0.12-unknown
  11. 2 Nodes configured, 2 expected votes
  12. 2 Resources configured.
  13. ============

  14. Online: [ suse1 suse2 ]

  15. webserver      (lsb:apache2):  Started suse1
  16. vip    (ocf::heartbeat:IPaddr):        Started suse2

  17. Failed actions:
  18.     vip_start_0 (node=suse1, call=5, rc=1, status=complete): unknown error

复制代码
suse1节点报错日志如下:

  1. Sep 21 17:40:02 suse1 cibadmin: [26136]: info: Invoked: cibadmin -Ql -o resources
  2. Sep 21 17:40:02 suse1 cibadmin: [26137]: info: Invoked: cibadmin -p -R -o resources
  3. Sep 21 17:40:02 suse1 cib: [25864]: info: log_data_element: cib:diff: - <cib admin_epoch="0" epoch="37" num_updates="2" >
  4. Sep 21 17:40:02 suse1 cib: [25864]: info: log_data_element: cib:diff: -   <configuration >
  5. Sep 21 17:40:02 suse1 cib: [25864]: info: log_data_element: cib:diff: -     <resources >
  6. Sep 21 17:40:02 suse1 crmd: [25868]: info: abort_transition_graph: need_abort:59 - Triggered transition abort (complete=1) : Non-status change
  7. Sep 21 17:40:02 suse1 cib: [25864]: info: log_data_element: cib:diff: -       <primitive id="vip" >
  8. Sep 21 17:40:02 suse1 crmd: [25868]: info: need_abort: Aborting on change to admin_epoch
  9. Sep 21 17:40:02 suse1 cib: [25864]: info: log_data_element: cib:diff: -         <meta_attributes id="vip-meta_attributes" >
  10. Sep 21 17:40:02 suse1 crmd: [25868]: info: do_state_transition: State transition S_IDLE -> S_POLICY_ENGINE [ input=I_PE_CALC cause=C_FSA_INTERNAL origin=abort_transition_graph ]
  11. Sep 21 17:40:02 suse1 cib: [25864]: info: log_data_element: cib:diff: -           <nvpair value="Stopped" id="vip-meta_attributes-target-role" />
  12. Sep 21 17:40:02 suse1 crmd: [25868]: info: do_state_transition: All 2 cluster nodes are eligible to run resources.
  13. Sep 21 17:40:02 suse1 cib: [25864]: info: log_data_element: cib:diff: -         </meta_attributes>
  14. Sep 21 17:40:02 suse1 crmd: [25868]: info: do_pe_invoke: Query 111: Requesting the current CIB: S_POLICY_ENGINE
  15. Sep 21 17:40:02 suse1 cib: [25864]: info: log_data_element: cib:diff: -       </primitive>
  16. Sep 21 17:40:02 suse1 cib: [25864]: info: log_data_element: cib:diff: -     </resources>
  17. Sep 21 17:40:02 suse1 cib: [25864]: info: log_data_element: cib:diff: -   </configuration>
  18. Sep 21 17:40:02 suse1 cib: [25864]: info: log_data_element: cib:diff: - </cib>
  19. Sep 21 17:40:02 suse1 cib: [25864]: info: log_data_element: cib:diff: + <cib admin_epoch="0" epoch="38" num_updates="1" >
  20. Sep 21 17:40:02 suse1 cib: [25864]: info: log_data_element: cib:diff: +   <configuration >
  21. Sep 21 17:40:02 suse1 cib: [25864]: info: log_data_element: cib:diff: +     <resources >
  22. Sep 21 17:40:02 suse1 cib: [25864]: info: log_data_element: cib:diff: +       <primitive id="vip" >
  23. Sep 21 17:40:02 suse1 cib: [25864]: info: log_data_element: cib:diff: +         <meta_attributes id="vip-meta_attributes" >
  24. Sep 21 17:40:02 suse1 cib: [25864]: info: log_data_element: cib:diff: +           <nvpair value="Started" id="vip-meta_attributes-target-role" />
  25. Sep 21 17:40:02 suse1 cib: [25864]: info: log_data_element: cib:diff: +         </meta_attributes>
  26. Sep 21 17:40:02 suse1 cib: [25864]: info: log_data_element: cib:diff: +       </primitive>
  27. Sep 21 17:40:02 suse1 cib: [25864]: info: log_data_element: cib:diff: +     </resources>
  28. Sep 21 17:40:02 suse1 cib: [25864]: info: log_data_element: cib:diff: +   </configuration>
  29. Sep 21 17:40:02 suse1 crmd: [25868]: info: do_pe_invoke_callback: Invoking the PE: query=111, ref=pe_calc-dc-1348220402-48, seq=152, quorate=1
  30. Sep 21 17:40:02 suse1 cib: [25864]: info: log_data_element: cib:diff: + </cib>
  31. Sep 21 17:40:02 suse1 cib: [25864]: info: cib_process_request: Operation complete: op cib_replace for section resources (origin=local/cibadmin/2, version=0.38.1): ok (rc=0)
  32. Sep 21 17:40:02 suse1 pengine: [25867]: notice: unpack_config: On loss of CCM Quorum: Ignore
  33. Sep 21 17:40:02 suse1 pengine: [25867]: info: unpack_config: Node scores: 'red' = -INFINITY, 'yellow' = 0, 'green' = 0
  34. Sep 21 17:40:02 suse1 pengine: [25867]: info: determine_online_status: Node suse1 is online
  35. Sep 21 17:40:02 suse1 pengine: [25867]: info: determine_online_status: Node suse2 is online
  36. [color=Red]
  37. Sep 21 17:40:02 suse1 pengine: [25867]: WARN: unpack_rsc_op: Processing failed op vip_start_0 on suse1: unknown error (1)
  38. Sep 21 17:40:02 suse1 pengine: [25867]: notice: native_print: webserver#011(lsb:apache2):#011Started suse1
  39. Sep 21 17:40:02 suse1 pengine: [25867]: notice: native_print: vip#011(ocf::heartbeat:IPaddr):#011Stopped
  40. Sep 21 17:40:02 suse1 pengine: [25867]: info: get_failcount: vip has failed INFINITY times on suse1
  41. Sep 21 17:40:02 suse1 pengine: [25867]: WARN: common_apply_stickiness: Forcing vip away from suse1 after 1000000 failures (max=1000000)
  42. Sep 21 17:40:02 suse1 crmd: [25868]: info: do_state_transition: State transition S_POLICY_ENGINE -> S_TRANSITION_ENGINE [ input=I_PE_SUCCESS cause=C_IPC_MESSAGE origin=handle_response ]
  43. Sep 21 17:40:02 suse1 pengine: [25867]: notice: LogActions: Leave   resource webserver#011(Started suse1)
  44. Sep 21 17:40:02 suse1 crmd: [25868]: info: unpack_graph: Unpacked transition 8: 1 actions in 1 synapses
  45. Sep 21 17:40:02 suse1 pengine: [25867]: notice: LogActions: Start   vip#011(suse2)
  46. Sep 21 17:40:02 suse1 crmd: [25868]: info: do_te_invoke: Processing graph 8 (ref=pe_calc-dc-1348220402-48) derived from /var/lib/pengine/pe-input-196.bz2
  47. Sep 21 17:40:02 suse1 crmd: [25868]: info: te_rsc_command: Initiating action 7: start vip_start_0 on suse2
  48. Sep 21 17:40:02 suse1 crmd: [25868]: info: match_graph_event: Action vip_start_0 (7) confirmed on suse2 (rc=0)
  49. [/color]
  50. Sep 21 17:40:02 suse1 crmd: [25868]: info: run_graph: ====================================================
  51. Sep 21 17:40:02 suse1 crmd: [25868]: notice: run_graph: Transition 8 (Complete=1, Pending=0, Fired=0, Skipped=0, Incomplete=0, Source=/var/lib/pengine/pe-input-196.bz2): Complete
  52. Sep 21 17:40:02 suse1 crmd: [25868]: info: te_graph_trigger: Transition 8 is now complete
  53. Sep 21 17:40:02 suse1 crmd: [25868]: info: notify_crmd: Transition 8 status: done - <null>
  54. Sep 21 17:40:02 suse1 crmd: [25868]: info: do_state_transition: State transition S_TRANSITION_ENGINE -> S_IDLE [ input=I_TE_SUCCESS cause=C_FSA_INTERNAL origin=notify_crmd ]
  55. Sep 21 17:40:02 suse1 crmd: [25868]: info: do_state_transition: Starting PEngine Recheck Timer
  56. Sep 21 17:40:02 suse1 cib: [26138]: info: write_cib_contents: Archived previous version as /var/lib/heartbeat/crm/cib-21.raw
  57. Sep 21 17:40:02 suse1 pengine: [25867]: info: process_pe_message: Transition 8: PEngine Input stored in: /var/lib/pengine/pe-input-196.bz2
  58. Sep 21 17:40:02 suse1 cib: [26138]: info: write_cib_contents: Wrote version 0.38.0 of the CIB to disk (digest: 18f31baf095b7a5f9eb06a486d4bc7e5)
  59. Sep 21 17:40:02 suse1 cib: [26138]: info: retrieveCib: Reading cluster configuration from: /var/lib/heartbeat/crm/cib.vjh5yt (digest: /var/lib/heartbeat/crm/cib.hkgFLS)

复制代码
suse2节点成功设置“vip”的日志:

  1. Sep 21 17:31:20 suse2 IPaddr(vip)[32317]: [32346]: INFO: Using calculated nic for 192.168.3.253: eth1
  2. Sep 21 17:31:20 suse2 IPaddr(vip)[32317]: [32352]: INFO: Using calculated netmask for 192.168.3.253: 255.255.0.0
  3. Sep 21 17:31:20 suse2 IPaddr(vip)[32317]: [32374]: INFO: eval ifconfig eth1:0 192.168.3.253 netmask 255.255.0.0 broadcast 192.168.255.255
  4. Sep 21 17:31:20 suse2 avahi-daemon[1004]: Registering new address record for 192.168.3.253 on eth1.IPv4.
  5. Sep 21 17:31:20 suse2 avahi-daemon[1004]: Withdrawing address record for 192.168.3.253 on eth1.
  6. Sep 21 17:31:20 suse2 avahi-daemon[1004]: Registering new address record for 192.168.3.253 on eth1.IPv4.
  7. Sep 21 17:31:20 suse2 lrmd: [32273]: info: operation start[4] on vip for client 32276: pid 32317 exited with return code 0
  8. Sep 21 17:31:20 suse2 crmd: [32276]: info: process_lrm_event: LRM operation vip_start_0 (call=4, rc=0, cib-update=9, confirmed=true) ok
复制代码
suse2节点,"vip"和"webserver"都可以启动:

  1. suse1:~ # crm status
  2. ============
  3. Last updated: Fri Sep 21 17:48:19 2012
  4. Stack: openais
  5. Current DC: suse1 - partition with quorum
  6. Version: 1.0.12-unknown
  7. 2 Nodes configured, 2 expected votes
  8. 1 Resources configured.
  9. ============

  10. Online: [ suse1 suse2 ]

  11. Resource Group: web
  12.      vip        (ocf::heartbeat:IPaddr):        Started suse2
  13.      webserver  (lsb:apache2):  Started suse2

  14. Failed actions:
  15.     vip_start_0 (node=suse1, call=5, rc=1, status=complete): unknown error
复制代码
请问,在suse2节点可以成功设置虚拟IP,在suse1节点不能设置IP的原因是什么?

您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们:huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP