Re: What does it means "rgmanager status 139"?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

I think your problem it's in the service definition

Il giorno 28 febbraio 2012 11:19, C. L. Martinez <carlopmart@xxxxxxxxx> ha scritto:
On Tue, Feb 28, 2012 at 11:14 AM, Digimer <linux@xxxxxxxxxxx> wrote:
> On 02/28/2012 05:06 AM, C. L. Martinez wrote:
>> On Tue, Feb 28, 2012 at 11:01 AM, Digimer <linux@xxxxxxxxxxx> wrote:
>>> On 02/28/2012 04:20 AM, C. L. Martinez wrote:
>>>> Hi all,
>>>>  What does it means?? I guess it is related to status check do it by
>>>> rgmanager, but executing status option from shell, result is 0
>>>> ...Then, why rgmanager returns this error??
>>>> Thanks.
>>> What version of the cluster? What is the cluster's configuration? What
>>> service is returning 139?
>>> You need to provide much more information than this for anyone to be
>>> able to help.
>> My rhcs verisons:
>> cman-
>> rgmanager-
>> cluster.conf relative to failed service:
>> <service autostart="0" domain="FirstCluster" exclusive="0"
>> name="splunksrv-svc" recovery="relocate">
>>                         <fs ref="splunksrvdata">
>>                                 <ip ref="">
>>                                         <script ref="splunksrv-cluster"/>
>>                                 </ip>
>>                         </fs>
>> </service>
> That is the service, but doesn't show the 'ref' entries.

<fs device="/dev/cludata/splunksrvdata" force_fsck="0"
force_unmount="1" fstype="ext4" mountpoint="/data/splunk/instance"
ksrvdata" self_fence="1"/>
<ip address="" monitor_link="yes" sleeptime="10"/>
<script file="/data/config/etc/init.d/splunksrv-cluster"

>> My service's script:
>> #!/bin/sh -x
> <snip>
>> Executing from command line:
>> [root@clunode01 init.d]# ./splunksrv-cluster mystatus
> <snip>
> rgmanager calls "status", so your script must work exactly like an
> init.d script in order for rgmanager to work (that is, responds as
> expected to 'start', 'stop' and 'status'). The "mystatus" is not what
> rgmanager will use.

Yes, I know ... I have changed "status" name to "mystatus" to do some
checks ... but when I change "mystatus" to "status" (the correct way),
then rgmanager fails with error code 139 and relocate the service to
the other node ...

esta es mi vida e me la vivo hasta que dios quiera
Linux-cluster mailing list

[Corosync Cluster Engine]     [Linux RAID]     [Fedora Users]     [Fedora Legacy List]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]

Add to Google Powered by Linux