I think your problem it's in the service definition<br><br><div class="gmail_quote">Il giorno 28 febbraio 2012 11:19, C. L. Martinez <span dir="ltr"><<a href="mailto:carlopmart@gmail.com">carlopmart@gmail.com</a>></span> ha scritto:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Tue, Feb 28, 2012 at 11:14 AM, Digimer <<a href="mailto:linux@alteeve.com">linux@alteeve.com</a>> wrote:<br>
> On 02/28/2012 05:06 AM, C. L. Martinez wrote:<br>
>> On Tue, Feb 28, 2012 at 11:01 AM, Digimer <<a href="mailto:linux@alteeve.com">linux@alteeve.com</a>> wrote:<br>
>>> On 02/28/2012 04:20 AM, C. L. Martinez wrote:<br>
>>>> Hi all,<br>
>>>><br>
>>>> What does it means?? I guess it is related to status check do it by<br>
>>>> rgmanager, but executing status option from shell, result is 0<br>
>>>> ...Then, why rgmanager returns this error??<br>
>>>><br>
>>>> Thanks.<br>
>>><br>
>>> What version of the cluster? What is the cluster's configuration? What<br>
>>> service is returning 139?<br>
>>><br>
>>> You need to provide much more information than this for anyone to be<br>
>>> able to help.<br>
>>><br>
>><br>
>> My rhcs verisons:<br>
>> cman-3.0.12.1-23.el6.x86_64<br>
>> rgmanager-3.0.12.1-5.el6.x86_64<br>
>><br>
>> cluster.conf relative to failed service:<br>
>> <service autostart="0" domain="FirstCluster" exclusive="0"<br>
>> name="splunksrv-svc" recovery="relocate"><br>
>> <fs ref="splunksrvdata"><br>
>> <ip ref="192.168.44.4"><br>
>> <script ref="splunksrv-cluster"/><br>
>> </ip><br>
>> </fs><br>
>> </service><br>
><br>
> That is the service, but doesn't show the 'ref' entries.<br>
<br>
</div></div><fs device="/dev/cludata/splunksrvdata" force_fsck="0"<br>
force_unmount="1" fstype="ext4" mountpoint="/data/splunk/instance"<br>
name="splun<br>
ksrvdata" self_fence="1"/><br>
<ip address="192.168.44.4" monitor_link="yes" sleeptime="10"/><br>
<script file="/data/config/etc/init.d/splunksrv-cluster"<br>
name="splunksrv-cluster"/><br>
<div class="im"><br>
<br>
><br>
>> My service's script:<br>
>> #!/bin/sh -x<br>
><br>
> <snip><br>
><br>
>> Executing from command line:<br>
>><br>
>> [root@clunode01 init.d]# ./splunksrv-cluster mystatus<br>
><br>
> <snip><br>
><br>
> rgmanager calls "status", so your script must work exactly like an<br>
> init.d script in order for rgmanager to work (that is, responds as<br>
> expected to 'start', 'stop' and 'status'). The "mystatus" is not what<br>
> rgmanager will use.<br>
><br>
<br>
</div>Yes, I know ... I have changed "status" name to "mystatus" to do some<br>
checks ... but when I change "mystatus" to "status" (the correct way),<br>
then rgmanager fails with error code 139 and relocate the service to<br>
the other node ...<br>
<div class="HOEnZb"><div class="h5"><br>
--<br>
Linux-cluster mailing list<br>
<a href="mailto:Linux-cluster@redhat.com">Linux-cluster@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/linux-cluster" target="_blank">https://www.redhat.com/mailman/listinfo/linux-cluster</a></div></div></blockquote></div><br><br clear="all"><br>-- <br>esta es mi vida e me la vivo hasta que dios quiera<br>