Using 11.2 clusterware to protect third party apps

Question

Has anyone successfully used CRS to protect third party applications?
Has anyone successfully used the scripts from the 11.2 Clusterware Reference manual, B-15, to test CRS with xclock or Apache?
After registering the resource and verifying status within CRS, crsctl start res xclock generates the following messages;
[root@node1 ~]# crsctl start res xclock
CRS-2672: Attempting to start 'xclock' on 'node1'
CRS-2674: Start of 'xclock' on 'node1' failed
CRS-2679: Attempting to clean 'xclock' on 'node1'
CRS-2678: 'xclock' on 'node1' has experienced an unrecoverable failure
CRS-0267: Human intervention required to resume its availability.
CRS-4000: Command Start failed, or completed with errors.
[root@node1 ~]#
What am I missing or not seeing?
Here is the Action script
#!/bin/bash
# start/stop/check script for xclock example
# To test this change BIN_DIR to the directory where xclock is based
# and set the DISPLAY variable to a server within your network.
BIN_DIR=/usr/X11R6/bin
LOG_DIR=/tmp
BIN_NAME=xclock
DISPLAY=yourhost.domain.com:0.0
export DISPLAY
if [ ! -d $BIN_DIR ]
then
echo "start failed"
exit 2
fi
PID1=`ps -ef | grep $BIN_NAME | grep -v grep | grep -v xclock_app | awk '{ print $2 }'`
case $1 in
'start')
if [ "$PID1" != "" ]
then
status_p1="running"
else
if [ -x $BIN_DIR/$BIN_NAME ]
then
umask 002
${BIN_DIR}/${BIN_NAME} & 2>${LOG_DIR}/${BIN_NAME}.log
status_p1="started"
else
echo `basename $0`": $BIN_NAME: Executable not found"
fi
fi
echo "$BIN_NAME: $status_p1"
'stop')
if [ "${PID1}" != "" ]
then
kill -9 ${PID1} && echo "$BIN_NAME daemon killed"
else
echo "$BIN_NAME: no running Process!"
fi
'check')
if [ "$PID1" != "" ]
then
echo "running"
exit 0
else
echo "not running"
exit 1
fi
echo "Usage: "`basename $0`" start"
esac
Resource profile
ACTION_SCRIPT=/app01/clstr_rsrc/res_scripts/xclock-clstr.sh
HOSTING_MEMBERS=node1 node2
PLACEMENT=favored
CHECK_INTERVAL=30
RESTART_ATTEMPTS=12
Thanks in advance,
T
Edited by: user8948362 on May 7, 2010 12:10 PM

Answer 1

Hi all, i have solved the problem. It was because of an erratic editing technique of the script. Infact, we edited the script on a PC, using NOTEPAD++, and transferred the script via binary FTP to AIX.
This introduced some abnormal characters inside the script.
Instead, by using VI editor on AIX, it works fine.