From: Howard Arnold (arnoldh@celerent.com)
Date: Fri Aug 13 2004 - 11:21:29 EDT
I am having an issue with caa_start where if I run it on a different node
from where it is started it fails with the following error:
node2 # caa_start appstart
Remote start for `appstart` failed on member `node3`
Remote start for `appstart` failed on member `node1`
node2 : Resource appstart (application) cannot run on node2
node4 : Resource appstart (application) cannot run on node4
My caa profile:
caa_profile file
node3 #
node3 # cat appstart.cap
NAME=appstart
TYPE=application
ACTION_SCRIPT=/usr/users/test/failover/Startapp
ACTIVE_PLACEMENT=0
AUTO_START=1
CHECK_INTERVAL=60
DESCRIPTION=appstart failover
FAILOVER_DELAY=0
FAILURE_INTERVAL=0
FAILURE_THRESHOLD=0
HOSTING_MEMBERS=node3 node1
OPTIONAL_RESOURCES=
PLACEMENT=restricted
REBALANCE=
REQUIRED_RESOURCES=
RESTART_ATTEMPTS=1
SCRIPT_TIMEOUT=1200
node3 #
Startapp
#!/usr/bin/ksh
#
############################################################################
case "$1" in
'start')
/usr/sbin/ifconfig nr0 alias 10.10.10.62/23
;;
'stop')
ifconfig nr0 -alias 10.10.10.62
;;
*)
echo "usage: $0 {start|stop}"
;;
esac
As you can see it's a very simple script to test that caa is working
correctly. It is a 4 node cluster running 5.1b with pk3 installed.
Has anyone seen some like this before? Could or should I restart the clu_caa
service and see what that will do?
Thanks for any help that can be provided.
Howard Arnold
Consultant Engineer
Phone: (603) 685-6060 ext. 206
Email: arnoldh@celerent.com
www.celerent.com
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:50:06 EDT