On 2006-01-19T23:46:34, "Joachim Banzhaf (compuserve)" <[EMAIL PROTECTED]>
wrote:
> > > in my test (current cvs, 3 nodes) the heartbeat Filesystem RA monitor
> > > (not ocf) returns 0 (and prints "Running OK"). The filesystem actually
BTW, most heartbeat resource script calls now get mapped to OCF RAs in
the background, Filesystem is one of them.
> I am not 100% sure which processes said what, but I have seen output like
> this
> in /var/log/messages
> ... Filesystem: ... Running OK
> ... lrmd(?): output from RA: []
> ... RA output [] didn't match any pattern
>
> For me it seemed like the lrmd failed to catch the output of the RA.
> I can extract the relevant lines tomorrow.
Ah. I see.
Code reading provided the answer.
This message is printed from the filesystem agent via ocf_log, which
ends up calling ha_log. And the status message is, in hto-mapfuncs.in,
also "printed" via ha_log.
ha_log writes to stderr.
Now, observe lrmd.c:3115
rc = RAExec->map_ra_retvalue(exitcode, op_type, op-
> >first_line_ra_stdout);
Can anyone spot the difference between stdout and stderr, or is it just
me?
I'm filing a bugzilla, for the conversion code (to stay compliant with
heartbeat 1.x, that message ought to go to stdout). I'd fix it myself,
but it's past midnight here and I don't want to mess it up.
Sincerely,
Lars Marowsky-Brée
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business -- Charles Darwin
"Ignorance more frequently begets confidence than does knowledge"
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
