Mailing List Archive: Linux-HA: Users

disable probe (even better, ignore fail) , before start a resource

Index | Next | Previous | View Threaded

jandot at gmail

Oct 9, 2010, 10:46 PM

Post #1 of 3 (227 views)
Permalink

disable probe (even better, ignore fail) , before start a resource

Hi,

we got an application which fail to start just because the monitor
operation before "start" exit with return code different than 3.
Actually the rc is 127 which means "file not found" and this happens
because the master script in /etc/init.d is llnked to other scripts on
the shared storage which, of course, is not available on all cluster
nodes at the same time (file system is mounted only on the active node)
Using the LSB script here.

I thinking of writing a OCF script which can somehow "fool" the master
script, for instance, where the monitor operation does not really use
the master script but makes other checks.

Make sense? Any hints?

Is already there an OCF script of example which works in a similar way?

Thanks,
Jan
_______________________________________________
Linux-HA mailing list
Linux-HA [at] lists
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

misch at schwartzkopff

Oct 9, 2010, 11:31 PM

Post #2 of 3 (204 views)
Permalink

Re: disable probe (even better, ignore fail) , before start a resource [In reply to]

On Sunday 10 October 2010 07:46:18 Jan Kalcic wrote:
> Hi,
>
> we got an application which fail to start just because the monitor
> operation before "start" exit with return code different than 3.
> Actually the rc is 127 which means "file not found" and this happens
> because the master script in /etc/init.d is llnked to other scripts on
> the shared storage which, of course, is not available on all cluster
> nodes at the same time (file system is mounted only on the active node)
> Using the LSB script here.
>
> I thinking of writing a OCF script which can somehow "fool" the master
> script, for instance, where the monitor operation does not really use
> the master script but makes other checks.
>
> Make sense? Any hints?
>
> Is already there an OCF script of example which works in a similar way?

No, thins makes no sense. It would be better to rewrite your script to exit
with the appropriate return values.

--
Dr. Michael Schwartzkopff
Guardinistr. 63
81375 München

Tel: (0163) 172 50 98
Fax: (089) 620 304 13

Attachments:

signature.asc (0.19 KB)

misch at clusterbau

Oct 9, 2010, 11:32 PM

Post #3 of 3 (209 views)
Permalink

Re: disable probe (even better, ignore fail) , before start a resource [In reply to]

On Sunday 10 October 2010 07:46:18 Jan Kalcic wrote:
> Hi,
>
> we got an application which fail to start just because the monitor
> operation before "start" exit with return code different than 3.
> Actually the rc is 127 which means "file not found" and this happens
> because the master script in /etc/init.d is llnked to other scripts on
> the shared storage which, of course, is not available on all cluster
> nodes at the same time (file system is mounted only on the active node)
> Using the LSB script here.
>
> I thinking of writing a OCF script which can somehow "fool" the master
> script, for instance, where the monitor operation does not really use
> the master script but makes other checks.
>
> Make sense? Any hints?

No, this makes no sense. It would be better to rewrite your script to exit
with the appropriate return values.

--
Dr. Michael Schwartzkopff
Guardinistr. 63
81375 München

Tel: (0163) 172 50 98

Attachments:

signature.asc (0.19 KB)

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads