First off, I would like to thank you for your time spent with this issue. > can you check to run it manually. Your ressource agent doesn't seem to > need any arguments so you should be able to do that: > > - stop heartbeat on node2 > - Wait a while until you see the state again > - Call /path/to/resource_samba_storage monito && echo Okay || echo > Failed > > I am pretty sure that this gives you a Failed. Than track it > down and get sure that it returns "Okay".
The steps I did were: -stop heartbeat on node2 -wait for resource to fully start on node1 -run "/etc/init.d/hb-vxvol monitor && echo Okay || echo Failed" on node2. You're correct that it showed up as 'Failed'. However, I thought this was the correct behavior. The 'monitor' action, according to the docs, and according to your Tomcat5.5 monitor from http://lists.linux-ha.org/pipermail/linux-ha/2008-January/029696.html is to return an exit code of 7 when the resource is 'stopped'. That's what the monitor function does: monitor() { fscount=`/bin/mount | /bin/grep "^/dev/vx/dsk" | wc -l` if [ "$fscount" -ge "4" ]; then return 0 fi dgcount=`/sbin/vxdg list | /bin/grep -- "vtq-fs.*enabled" | \ /usr/bin/wc -l` if [ "$dgcount" == "0" ]; then # if deported, it's stopped, and we're fine. return 7 fi if [ "$fscount" -ge "1" ]; then return 1 fi if [ "$dgcount" != "0" ]; then return 1 fi return 1 } FYI: I followed your suggestion to remove the crm/* files and run the 'cibadmin -U -X ...' commands. --Jason _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
