LINUX.ORG.RU
ФорумAdmin

Digium R850 + pacemaker + corosync

 , ,


0

1

Добрый день! Не получается корректно настроить pacemaker по этой инструкции : http://habrahabr.ru/post/160521/ Дошел до пункта обновления конфига pacemaker.cfg.

В логах выдает ошибку:

[root@astnode01 pacemaker]# crm configure load update pacemaker.cfg
lrmadmin[6560]: 2014/12/25_12:40:37 ERROR: lrm_get_rsc_type_metadata(578): got a return code HA_FAIL from a reply message of rmetadata with function get_ret_from_msg.
ERROR: ocf:Digium:asterisk: could not parse meta-data:
lrmadmin[6594]: 2014/12/25_12:40:37 ERROR: lrm_get_rsc_type_metadata(578): got a return code HA_FAIL from a reply message of rmetadata with function get_ret_from_msg.
ERROR: ocf:Digium:rseries: could not parse meta-data:
ERROR: ocf:Digium:asterisk: could not parse meta-data:
ERROR: ocf:Digium:asterisk: no such resource agent
WARNING: Asterisk_drbd: default timeout 20s for start is smaller than the advised 240
WARNING: Asterisk_drbd: default timeout 20s for stop is smaller than the advised 100
WARNING: Asterisk_drbd: action monitor not advertised in meta-data, it may not be supported by the RA
WARNING: Asterisk_fs: default timeout 20s for start is smaller than the advised 60
WARNING: Asterisk_fs: default timeout 20s for stop is smaller than the advised 60
WARNING: GatewayStatus: default timeout 20s for start is smaller than the advised 60
WARNING: GatewayStatus: specified timeout 10 for monitor is smaller than the advised 60
ERROR: ocf:Digium:rseries: could not parse meta-data:
ERROR: ocf:Digium:rseries: no such resource agent

Сам конфиг:

node astnode01
node astnode02
primitive Asterisk ocf:Digium:asterisk \
        op monitor interval="5"
primitive Asterisk_drbd ocf:linbit:drbd \
        params drbd_resource="asterisk" \
        op monitor start-delay="10" interval="5"
primitive Asterisk_fs ocf:heartbeat:Filesystem \
        params device="/dev/drbd/by-res/asterisk" directory="/mnt/asterisk/" fstype="ext3"
primitive ClusterIP ocf:heartbeat:IPaddr2 \
        params ip="10.4.2.151" cidr_netmask="32" \
        op monitor interval="5"
primitive GatewayStatus ocf:pacemaker:ping \
        params host_list="10.4.2.1" multiplier="100" \
        op monitor interval="5" timeout="10"
primitive rseries0 ocf:Digium:rseries \
        params tty="/dev/rseries0" \
        op monitor interval="10" role="Master" \
        op monitor interval="60" role="Slave"
ms Asterisk_ms Asterisk_drbd \
        meta master-max="1" master-node-max="1" clone-max="2" clone-node-max="1" notify="true"
ms rseries0_ms rseries0 \
        meta master-max="1" master-node-max="1" clone-max="2" clone-node-max="1" target-role="Master"
clone GatewayStatusClone GatewayStatus
location Asterisk-with-ping Asterisk \
        rule $id="Asterisk-with-ping-rule" -inf: not_defined pingd or pingd lte 0
colocation Everything-with-Asterisk inf: ( rseries0_ms:Master Asterisk_ms:Master ) ( ClusterIP Asterisk_fs ) Asterisk
order Asterisk-after-Everything inf: ( rseries0_ms:promote Asterisk_ms:promote ) ( ClusterIP Asterisk_fs ) Asterisk:start
property $id="cib-bootstrap-options" \
        cluster-infrastructure="openais" \
        expected-quorum-votes="2" \
        stonith-enabled="false" \
        no-quorum-policy="ignore"
rsc_defaults $id="rsc-options" \
        resource-stickiness="99"

В чем может быть проблема?

Elastix 2.5

Конфиг corosync:

totem {
    version: 2
    token: 3000
    token_retransmits_before_loss_const: 10
    join: 60
    consensus: 5000
    vsftype: none
    max_messages: 20
    clear_node_high_bit: yes
        secauth: off
        threads: 0
        rrp_mode: none

        interface {
        ringnumber: 0
        bindnetaddr: 10.4.2.0
        broadcast: yes
        mcastport: 5405
        member {
            memberaddr: 10.4.2.101
        }
        member {
            memberaddr: 10.4.2.102
        }
    }
}

aisexec {
    user:       root
    group:      root
}

logging {
    fileline: off
    to_stderr: yes
    to_logfile: no
    to_syslog: yes
    syslog_facility: daemon
    debug: off
    timestamp: on
    logger_subsys {
        subsys: AMF
        debug: off
        tags: enter|leave|trace1|trace2|trace3|trace4|trace6
    }
}

amf {
    mode: disabled
}



Последнее исправление: mkondratev (всего исправлений: 1)
ERROR: ocf:Digium:rseries: no such resource agent

По-моему всё вполне ясно написано - пейсмейкер не может найти у себя ресурс агента такого. Почему он не установлен - читай статью, может что-то не сделал. Лежит это добро обычно в /usr/lib/ocf/resource.d

blind_oracle ★★★★★
()
Ответ на: комментарий от mkondratev
[root@astnode01 ~]# ls -l /usr/lib/ocf/resource.d/linbit/
total 32
-rwxr-xr-x 1 root root 29082 Mar 27  2013 drbd
mkondratev
() автор топика
Вы не можете добавлять комментарии в эту тему. Тема перемещена в архив.