[Pacemaker] failed actions after resource creation

[andreas graeper]

hi and thanks.
(better sentences: i will give my best)
on inactive node there is actually only /etc/init.d/nfs and neither
nfs-common nor nfs-kernel-server.
is monitor not only looking for the running service on active node, but for
the situation on inactive node, too ?
so i would have expected, that the missing nfs-kernel-server was reported,
too.


i guess, this can be handled only with a init-script 'nfs' (same name on
both nodes) that is starting/killing nfs-commo/nfs-kernel-server ?
or is there another solution ?

what is monitor in case of resource managed by lsb-script doing ?
is it calling `service xxx status` ?
what does the monitor expect on node where service is running / not running
?

thanks in advance
andreas


2013/6/6 Florian Crouzat <gentoo at floriancrouzat.net>

> Le 06/06/2013 15:49, andreas graeper a écrit :
>
>       p_nfscommon_monitor_0 (node=linag, call=189, rc=5,
>> status=complete): not installed
>>
>
> Sounds obvious: "not installed". Node "linag" is missing some
> daemons/scripts , probably nfs-related. Check your nfs packages and
> configuration on both nodes, node1 should be missing something.
>
>
>  what can i do ?
>>
>
> Better sentences.
>
> --
> Cheers,
> Florian Crouzat
>
> ______________________________**_________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/**mailman/listinfo/pacemaker<http://oss.clusterlabs.org/mailman/listinfo/pacemaker>
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/**doc/Cluster_from_Scratch.pdf<http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf>
> Bugs: http://bugs.clusterlabs.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20130606/cefd0820/attachment-0003.html>