1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

IP resource can't be started on OI with pacemaker+heartbeat

Discussion in 'Solaris, Nexenta, OpenIndiana, and napp-it' started by bob, Nov 26, 2013.

  1. bob

    bob New Member

    Hello Guys,
    I am trying to setup a HA cluster on openindiana(oi_151a7), with two heads, shared storage environment for some test,
    basically I followed the steps described on:
    Clustering/ High Availablity - OpenIndiana - OpenIndiana Wiki

    now it seems the heartbeat works as expected(I can see both the nodes online), while I try to add an IP resource to the cluster,
    I always got following errors, Does anyone tried this? Can you share your experience or give me some advice?
    thanks in advance!

    here is my configurations:( there are two nodes, build(172.16.1.114) and zhaodx.cc(172.16.1.225), each node has two nics)
    crm configure show
    node $id="00076d92-6c3b-cf3e-b7d9-ea4ed074429b" zhaodx.cc
    node $id="bdc65bf9-2822-e4c5-f4c3-8c8fb3240314" build
    primitive site_one_ip ocf:heartbeat:IPaddr \
    params ip="192.168.1.111" cidr_netmask="255.255.255.0" nic="e1000g1"
    primitive site_two_ip ocf:heartbeat:IPaddr \
    params ip="192.168.1.222" cidr_netmask="255.255.255.0" nic="e1000g1"
    location site_one_ip_pref site_one_ip 100: build
    location site_two_ip_pref site_two_ip 100: zhaodx.cc
    property $id="cib-bootstrap-options" \
    dc-version="1.0.11-6e010d6b0d49a6b929d17c0114e9d2d934dc8e04" \
    cluster-infrastructure="Heartbeat" \
    stonith-enabled="false" \
    no-quorum-policy="ignore"

    # crm resource status
    site_two_ip (ocf::heartbeat:IPaddr) Stopped
    site_one_ip (ocf::heartbeat:IPaddr) Stopped

    crm_mon -1
    ============
    Last updated: Wed Nov 27 14:33:29 2013
    Stack: Heartbeat
    Current DC: build (bdc65bf9-2822-e4c5-f4c3-8c8fb3240314) - partition with quorum
    Version: 1.0.11-6e010d6b0d49a6b929d17c0114e9d2d934dc8e04
    2 Nodes configured, unknown expected votes
    2 Resources configured.
    ============

    Online: [ build zhaodx.cc ]


    Failed actions:
    site_one_ip_start_0 (node=build, call=17, rc=5, status=complete): not installed
    ClusterIP_monitor_0 (node=build, call=11, rc=5, status=complete): not installed
    site_two_ip_start_0 (node=build, call=14, rc=5, status=complete): not installed
    site_one_ip_start_0 (node=zhaodx.cc, call=15, rc=5, status=complete): not installed
    ClusterIP_start_0 (node=zhaodx.cc, call=3, rc=5, status=complete): not installed
    site_two_ip_start_0 (node=zhaodx.cc, call=14, rc=5, status=complete): not installed

    some logs i cached:
    Nov 27 14:33:09 build pengine: [716]: info: determine_online_status: Node build is online
    Nov 27 14:33:09 build pengine: [716]: info: determine_online_status: Node zhaodx.cc is online
    Nov 27 14:33:09 build pengine: [716]: notice: unpack_rsc_op: Operation site_one_ip_monitor_0 found resourc
    e site_one_ip active on build
    Nov 27 14:33:09 build pengine: [716]: notice: unpack_rsc_op: Hard error - site_one_ip_start_0 failed with
    rc=5: Preventing site_one_ip from re-starting on build
    Nov 27 14:33:09 build pengine: [716]: WARN: unpack_rsc_op: Processing failed op site_one_ip_start_0 on bui
    ld: not installed (5)
    Nov 27 14:33:09 build pengine: [716]: notice: unpack_rsc_op: Hard error - ClusterIP_monitor_0 failed with
    rc=5: Preventing ClusterIP from re-starting on build
    Nov 27 14:33:09 build pengine: [716]: notice: unpack_rsc_op: Hard error - site_two_ip_start_0 failed with
    rc=5: Preventing site_two_ip from re-starting on build
    Nov 27 14:33:09 build pengine: [716]: WARN: unpack_rsc_op: Processing failed op site_two_ip_start_0 on bui
    ld: not installed (5)
    Nov 27 14:33:09 build pengine: [716]: notice: unpack_rsc_op: Hard error - site_one_ip_start_0 failed with
    rc=5: Preventing site_one_ip from re-starting on zhaodx.cc
    Nov 27 14:33:09 build pengine: [716]: WARN: unpack_rsc_op: Processing failed op site_one_ip_start_0 on zha
    odx.cc: not installed (5)
    Nov 27 14:33:09 build pengine: [716]: notice: unpack_rsc_op: Hard error - ClusterIP_start_0 failed with rc
    =5: Preventing ClusterIP from re-starting on zhaodx.cc
    Nov 27 14:33:09 build pengine: [716]: WARN: unpack_rsc_op: Processing failed op ClusterIP_start_0 on zhaod
    x.cc: not installed (5)
  2. bob

    bob New Member

    now the ip resource can be start/stop correctly, after mkdir /opt/ha/var/run/resource-agents
    however, even i stop the heart service on node1(the one which VIP installed), the node2 did not install the VIP automatically.
    and if i start heartbeat on node1 again, the VIP comes back, what steps do i missed?

Share This Page