On Dec 18, 2007, at 6:28 AM, DAIKI MATSUDA wrote:
Hi, Andrew.
I am sorry for delay because I was not aware of requiring logs. And I
attached the hb_report log.
Best Regards
MATSUDA, Daiki
2007/12/12, Andrew Beekhof <[EMAIL PROTECTED]>:
On Dec 12, 2007, at 7:41 AM, DAIKI MATSUDA wrote:
Hi, All.
I recently make own RA and mentioned the odd behaviour for
monitor. It
is that without writing
<operations>
<op id="test1:monitor" name="monitor" interval="10s"
timeout="10s" start_delay="30s" on_fail="restart"/>
</operations>
for primitive directive in cib.xml, the RA does not monitor its
service.
In my thinking, the default value is decided in meta-data action,
e.g.
<action name="monitor" depth="0" timeout="30" interval="10" start-
delay="30" />
is the default value for monitoring for 10s intervals.
Or, have I to write the monitor operation in the cib.xml obviously?
I think I misunderstood the question.
the meta-data is not used by the cluster directly. it only provides
hints to GUIs.
if you want the cluster to monitor a resource's health, you need
specify a monitor action in the CIB - resource's are not monitored by
default.
does that answer your query?
looks right to me - it should wait 30s and then start performing
monitor ops.
probably worth logging a bug with a hb_report archive
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
<
monitor
.tar
.gz><nonmonitor.tar.gz>_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
