[Pacemaker] Problems setting up clone resource syslog-ng - I need help

[Pavlos Parissis]

On 17 November 2010 13:22, Michael Schwartzkopff <misch at clusterbau.com> wrote:
> On Wednesday 17 November 2010 13:09:01 Senftleben, Stefan, ITSC wrote:
>> Hi,
>>
>> okay, these infos I found in syslog. But no lrmd-log entries canbe found.
>>
>>
>> root at lxds05:~# cat /var/log/syslog|grep pengi|grep syslog
>> Nov 17 12:47:22 lxds05 pengine: [1089]: ERROR: unpack_rsc_op: Hard error -
>> syslog-ng:0_monitor_0 failed with rc=6: Preventing syslog-ng-clone from
>> re-starting anywhere in the cluster Nov 17 12:47:22 lxds05 pengine:
>> [1089]: ERROR: unpack_rsc_op: Hard error - syslog-ng:0_monitor_0 failed
>> with rc=6: Preventing syslog-ng-clone from re-starting anywhere in the
>> cluster Nov 17 12:47:22 lxds05 pengine: [1089]: notice: clone_print:
>> Clone Set: syslog-ng-clone Nov 17 12:47:22 lxds05 pengine: [1089]: notice:
>> short_print:      Stopped: [ syslog-ng:0 syslog-ng:1 ] Nov 17 12:47:22
>> lxds05 pengine: [1089]: info: native_color: Resource syslog-ng:0 cannot
>> run anywhere Nov 17 12:47:22 lxds05 pengine: [1089]: info: native_color:
>> Resource syslog-ng:1 cannot run anywhere Nov 17 12:47:22 lxds05 pengine:
>> [1089]: notice: LogActions: Leave resource syslog-ng:0  (Stopped) Nov 17
>> 12:47:22 lxds05 pengine: [1089]: notice: LogActions: Leave resource
>> syslog-ng:1  (Stopped) Nov 17 12:48:00 lxds05 pengine: [1089]: ERROR:
>> unpack_rsc_op: Hard error - syslog-ng:0_monitor_0 failed with rc=6:
>> Preventing syslog-ng-clone from re-starting anywhere in the cluster
>>
>>
>> Question:
>>       I executed following commands in /usr/lib/ocf/resource.d/heartbeat/ :
>> OCF_ROOT=/usr/lib/ocf
>> OCF_FUNCTIONS_DIR=${OCF_ROOT}/resource.d/heartbeat
>>
>>       Executing the RA manually:
>> root at lxds05:/usr/lib/ocf/resource.d/heartbeat# ./syslog-ng
>> ./syslog-ng: Zeile 27: /resource.d/heartbeat/.ocf-shellfuncs: No such file
>> or directory ./syslog-ng: Zeile 216: ocf_log: Kommando nicht gefunden.
>>
>> What command is needed to run the RA manually?
>>
>> Thanks
>> Stefan
>
> Hi,
>
> The lines above the ERROR messages in the syslog would be interesting. Please
> check on both nodes for output of the resource agent.
>
> export OCF_ROOT=/usr/lib/ocf
> /usr/lib/ocf/resource.d/heartbeat/syslog-ng meta-data
>
> this will tell you that the configfile parameter is mandatory.
>
> so have to set something like
> export OCF_RESKESY_configfile=/etc/syslog-ng.conf
>
> Greetings,

or look at which conditions it returns OCF_ERR_CONFIGURED, which is rc 6

[root at node-01 ~]# grep -B 4 OCF_ERR_CONFIGURED
/usr/lib/ocf/resource.d/heartbeat/syslog-ng

CONFIGFILE="${OCF_RESKEY_configfile}"
if [[ -z "$CONFIGFILE" ]]; then
        ocf_log err "undefined parameter:configfile"
        exit $OCF_ERR_CONFIGURED
--
SYSLOG_NG_EXE="${OCF_RESKEY_syslog_ng_binary-/sbin/syslog-ng}"
# why not default to /sbin/syslog-ng?
#if [[ -z "$SYSLOG_NG_EXE" ]]; then
#       ocf_log err "Undefined parameter:syslog_ng_binary"
#       exit $OCF_ERR_CONFIGURED
#fi
if [[ ! -x "$SYSLOG_NG_EXE" ]]; then
        ocf_log err "Invalid value:syslog_ng_binary:$SYSLOG_NG_EXE"
        exit $OCF_ERR_CONFIGURED
--

KILL_TERM_TIMEOUT="${OCF_RESKEY_kill_term_timeout-10}"
if ! ocf_is_decimal "$KILL_TERM_TIMEOUT"; then
        ocf_log err "Invalid value:kill_term_timeout:$KILL_TERM_TIMEOUT"
        exit $OCF_ERR_CONFIGURED