[Pacemaker] /usr/lib/ocf/resource.d//heartbeat/IPaddr2: Cannot fork

Dejan Muhamedagic dejanmm at fastmail.fm
Wed Jun 4 04:49:34 EDT 2014


Hi,

On Tue, Jun 03, 2014 at 06:20:49PM +0530, ESWAR RAO wrote:
> Hi All,
> 
> I configured a resource on loopback interface and it was assigned correctly
> through pacemaker but after a while the ip address was
> removed and it was not being monitored.
> 
> Can someone help me out the reason for failure???
> I couldn't understand why the monitor is also failing.

There was some general condition which prevented the resource
agent from functioning correctly.

> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> primitive oc_nvp_vip ocf:heartbeat:IPaddr2 \
>         params ip="192.168.101.68" cidr_netmask="32" nic="lo" \
>         op monitor interval="15s"
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> # crm_mon -rf1 | grep oc_nvp_vip
> 
> Clone Set: oc_nvp_app_clone_nvp_vip [oc_nvp_vip]
>      Stopped: [ oc_nvp_vip:0 ]
> 
> Migration summary:
> * Node nvsd-59:
>    oc_nvp_vip:0: migration-threshold=1000000 fail-count=1
> 
> Failed actions:
>     oc_nvp_vip:0_monitor_15000 (node=nvsd-59, call=41, rc=2,
> status=complete): invalid parameter
> 
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 
> 
> 
> May 23 14:01:31 nvsd-59 lrmd: [15878]: info: operation monitor[41] on
> oc_nvp_vip:0 for client 15881: pid 6938 exited with return code 0
> May 23 15:01:44 nvsd-59 lrmd: [15878]: info: rsc:oc_nvp_vip:0 monitor[41]
> (pid 23891)
> May 23 15:01:44 nvsd-59 lrmd: [15878]: info: operation monitor[41] on
> oc_nvp_vip:0 for client 15881: pid 23891 exited with return code 0
> May 23 16:01:46 nvsd-59 lrmd: [15878]: info: rsc:oc_nvp_vip:0 monitor[41]
> (pid 13391)
> May 23 16:01:46 nvsd-59 lrmd: [15878]: info: operation monitor[41] on
> oc_nvp_vip:0 for client 15881: pid 13391 exited with return code 0
> May 23 16:19:01 nvsd-59 lrmd: [15878]: info: RA output:
> (oc_nvp_vip:0:monitor:stderr) /usr/lib/ocf/resource.d//heartbeat/IPaddr2:
> 71: /usr/lib/ocf/resource.d//heartbeat/IPaddr2: Cannot fork

This is a message from the shell (/bin/sh). It doesn't mention
the reason for not being able to fork, but it's definitely
hitting some limit (too many processes perhaps). You should check
the state of affairs on this host.

Thanks,

Dejan

> May 23 16:19:01 nvsd-59 crmd: [15881]: info: process_lrm_event: LRM
> operation oc_nvp_vip:0_monitor_15000 (call=41, rc=2, cib-update=179,
> confirmed=false) invalid parameter
> May 23 16:19:02 nvsd-59 attrd: [15880]: notice: attrd_trigger_update:
> Sending flush op to all hosts for: fail-count-oc_nvp_vip:0 (1)
> May 23 16:19:02 nvsd-59 lrmd: [15878]: info: cancel_op: operation
> monitor[41] on oc_nvp_vip:0 for client 15881, its parameters:
> cidr_netmask=[32] CRM_meta_timeout=[120000] CRM_meta_name=[monitor]
> crm_feature_set=[3.0.6] CRM_meta_notify=[false] CRM_meta_clone_node_max=[1]
> CRM_meta_clone=[0] CRM_meta_clone_max=[2] CRM_meta_interval=[15000]
> ip=[192.168.101.68] nic=[lo] CRM_meta_globally_unique=[false]  cancelled
> May 23 16:19:02 nvsd-59 lrmd: [15878]: info: rsc:oc_nvp_vip:0 stop[189]
> (pid 27111
> 
> 
> 
> 
> Thanks
> Eswar Rao

> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org





More information about the Pacemaker mailing list