>>> Dejan Muhamedagic <[EMAIL PROTECTED]> 08.10.2007 17:23 >>>
> There is no special logging procedure--just echo whatever you
> want to say to stdout and it will find it's way to the logs.

Hi Dejan,

did a little test. I've implemented a can't-do-anything stonith plugin.
Trying to start it gives:
=======================================================================
Oct  9 11:45:38 db02 lrmd: [3682]: info: Try to start STONITH resource 
<rsc_id=r_stonith-db01> : Device=external/ibmrsa-telnet
Oct  9 11:45:38 db02 stonithd: [3636]: CRIT: external_run_cmd: stating 
/usr/lib/stonith/plugins/external/ibmrsa-telnet failed.
Oct  9 11:45:38 db02 stonithd: [3636]: CRIT: external_get_confignames: 
'ibmrsa-telnet getconfignames' failed with rc -1
Oct  9 11:45:38 db02 stonithd: [3636]: ERROR: Invalid config info for 
external/ibmrsa-telnet device.
Oct  9 11:45:38 db02 lrmd: [3682]: ERROR: sending stonithRA op to stonithd 
failed.
Oct  9 11:45:38 db02 lrmd: [3635]: WARN: mapped the invalid return code 254.
========================================================================

Yes, 'getconfignames' is not implemented. If I call it manually I get the 
following:
========================================================================
db01:/opt/ha # ./ibmrsa-telnet getconfignames
ERROR: ibmrsa-telnet : Not implemented. Has to be defined.
db01:/opt/ha # echo $?
1
db01:/opt/ha #
========================================================================

The problem is: I can't see the error message anywhere in the logs.
If such a thing hapens in real life, administrator doesn't have any
chance to find out what happened.

Why is the return code 1 interpreted as return code -1?

What does the line 'WARN: mapped the invalid return code 254' mean?

Is your initial statement concerning printing to stdout still true?


Best regards
Andreas Mock


_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to