[SOLVED] R-series failover Installation failed

Hi, I’m trying to setup a R850, I’m following the R-series admin guide but when I try to update the configuration of pacemaker the system show this errors:

# crm configure load update configs/pacemaker/pacemaker.cfg lrmadmin[8658]: 2012/11/24_05:59:42 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[8667]: 2012/11/24_05:59:42 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:heartbeat:Filesystem: could not parse meta-data: lrmadmin[8669]: 2012/11/24_05:59:42 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:heartbeat:IPaddr2: could not parse meta-data: lrmadmin[8671]: 2012/11/24_05:59:42 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:pacemaker:ping: could not parse meta-data: lrmadmin[8673]: 2012/11/24_05:59:43 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 ERROR: ocf:heartbeat:Filesystem: could not parse meta-data: ERROR: ocf:heartbeat:Filesystem: no such resource agent ERROR: ocf:heartbeat:IPaddr2: could not parse meta-data: ERROR: ocf:heartbeat:IPaddr2: no such resource agent ERROR: ocf:pacemaker:ping: could not parse meta-data: ERROR: ocf:pacemaker:ping: no such resource agent ERROR: ocf:Digium:rseries: could not parse meta-data: ERROR: ocf:Digium:rseries: no such resource agent

Checking the messages log I see:

Nov 24 04:12:12 SMSOTG-SRV131 lrmd: [8166]: ERROR: get_resource_meta: pclose failed: Resource temporarily unavailable Nov 24 04:12:12 SMSOTG-SRV131 lrmd: [8166]: WARN: on_msg_get_metadata: empty metadata for ocf::Digium::asterisk. Nov 24 04:12:12 SMSOTG-SRV131 lrmd: [8166]: WARN: G_SIG_dispatch: Dispatch function for SIGCHLD was delayed 200 ms (> 100 ms) before being called (GSource: 0x163cea0) Nov 24 04:12:12 SMSOTG-SRV131 lrmd: [8166]: info: G_SIG_dispatch: started at 430103647 should have started at 430103627 Nov 24 04:12:12 SMSOTG-SRV131 lrmadmin: [8517]: 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. Nov 24 04:12:12 SMSOTG-SRV131 lrmd: [8166]: ERROR: get_resource_meta: pclose failed: Resource temporarily unavailable Nov 24 04:12:12 SMSOTG-SRV131 lrmd: [8166]: WARN: on_msg_get_metadata: empty metadata for ocf::heartbeat::Filesystem. Nov 24 04:12:12 SMSOTG-SRV131 lrmd: [8166]: WARN: G_SIG_dispatch: Dispatch function for SIGCHLD was delayed 200 ms (> 100 ms) before being called (GSource: 0x163cea0) Nov 24 04:12:12 SMSOTG-SRV131 lrmd: [8166]: info: G_SIG_dispatch: started at 430103670 should have started at 430103650 Nov 24 04:12:12 SMSOTG-SRV131 lrmadmin: [8526]: 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. Nov 24 04:12:12 SMSOTG-SRV131 lrmd: [8166]: ERROR: get_resource_meta: pclose failed: Resource temporarily unavailable Nov 24 04:12:12 SMSOTG-SRV131 lrmd: [8166]: WARN: on_msg_get_metadata: empty metadata for ocf::heartbeat::IPaddr2. Nov 24 04:12:12 SMSOTG-SRV131 lrmd: [8166]: WARN: G_SIG_dispatch: Dispatch function for SIGCHLD was delayed 200 ms (> 100 ms) before being called (GSource: 0x163cea0) Nov 24 04:12:12 SMSOTG-SRV131 lrmd: [8166]: info: G_SIG_dispatch: started at 430103690 should have started at 430103670 Nov 24 04:12:12 SMSOTG-SRV131 lrmadmin: [8528]: 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. Nov 24 04:12:12 SMSOTG-SRV131 lrmd: [8166]: ERROR: get_resource_meta: pclose failed: Resource temporarily unavailable Nov 24 04:12:12 SMSOTG-SRV131 lrmd: [8166]: WARN: on_msg_get_metadata: empty metadata for ocf::pacemaker::ping. Nov 24 04:12:12 SMSOTG-SRV131 lrmd: [8166]: WARN: G_SIG_dispatch: Dispatch function for SIGCHLD was delayed 200 ms (> 100 ms) before being called (GSource: 0x163cea0) Nov 24 04:12:12 SMSOTG-SRV131 lrmd: [8166]: info: G_SIG_dispatch: started at 430103711 should have started at 430103691 Nov 24 04:12:12 SMSOTG-SRV131 lrmadmin: [8530]: 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. Nov 24 04:12:13 SMSOTG-SRV131 lrmd: [8166]: ERROR: get_resource_meta: pclose failed: Resource temporarily unavailable Nov 24 04:12:13 SMSOTG-SRV131 lrmd: [8166]: WARN: on_msg_get_metadata: empty metadata for ocf::Digium::rseries. Nov 24 04:12:13 SMSOTG-SRV131 lrmd: [8166]: WARN: G_SIG_dispatch: Dispatch function for SIGCHLD was delayed 200 ms (> 100 ms) before being called (GSource: 0x163cea0) Nov 24 04:12:13 SMSOTG-SRV131 lrmd: [8166]: info: G_SIG_dispatch: started at 430103731 should have started at 430103711 Nov 24 04:12:13 SMSOTG-SRV131 lrmadmin: [8532]: 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. Nov 24 04:12:13 SMSOTG-SRV131 cib[8542]: info: crm_log_init_worker: Changed active directory to /var/lib/heartbeat/cores/root

The permission on files are 755:

[code]# stat -c “%a” /usr/lib/ocf/resource.d/Digium/asterisk
755

stat -c “%a” /usr/lib/ocf/resource.d/Digium/rseries

755
[/code]

The Resource Agents Exists in /usr/lib/ocf/resource.d/Digium. The only difference is that I’m using CentOS 6.3 instead CentOS 5.6 is that the issue?

Hi, I installed the suggested version and works like a charm.

I just have 2 erratas:

On Page 53 the repo link has changed from:

To

And finally On Page 64 the instructions say:

[code]
– If the Asterisk init script is installed (/etc/init.d/asterisk), it will need
to be disabled in order to not conflict with the automatic failover con-
figuration. This can be accomplished by executing chkconfig --del
asterisk on Red Hat based distributions and update-rc.d -f asterisk
remove on Debian based distributions.

– If the DAHDI init script is not already installed (/etc/init.d/dahdi),
execute make config in the DAHDI source directory to install it.

–Execute drbdadm secondary asterisk.
[/code]

Should be:

[code]
–If the Asterisk init script is installed (/etc/init.d/asterisk), it will need
to be disabled in order to not conflict with the automatic failover con-
figuration. This can be accomplished by executing chkconfig --del
asterisk on Red Hat based distributions and update-rc.d -f asterisk
remove on Debian based distributions.

–If the DAHDI init script is not already installed (/etc/init.d/dahdi),
execute make config in the DAHDI source directory to install it.

–Execute umount /mnt/asterisk

–Execute drbdadm secondary asterisk.
[/code]

The umount is missing and i cant run the “drbdadm secondary” command until the device is unmounted.

Howdy,

Thanks. I’ve forwarded this over to the product manager of the R-series products for his consideration.

Cheers