+++ This bug was initially created as a clone of Bug #235178 +++ Description of problem: The metadata in the fs.sh resource agent suggests that the default poll interval is 2m: <!-- Checks to see if it's mounted in the right place --> <action name="status" interval="2m" timeout="10"/> <action name="monitor" interval="2m" timeout="10"/> <!-- Note: active monitoring is constant and supplants all check depths --> <!-- Checks to see if we can read from the mountpoint --> <action name="status" depth="10" timeout="30" interval="2m"/> <action name="monitor" depth="10" timeout="30" interval="2m"/> <!-- Checks to see if we can write to the mountpoint (if !ROFS) --> <action name="status" depth="20" timeout="30" interval="2m"/> <action name="monitor" depth="20" timeout="30" interval="2m"/> When debug is enabled, syslog seems to show the script polling around every 1m: Mar 12 09:20:26 testhost1 clurgmgrd[28859]: <debug> status on fs:test1_archiv returned 0 (success) Mar 12 09:21:27 testhost1 clurgmgrd[28859]: <debug> status on fs:test1_archiv returned 0 (success) Mar 12 09:22:27 testhost1 clurgmgrd[28859]: <debug> status on fs:test1_archiv returned 0 (success) Mar 12 09:22:37 testhost1 clurgmgrd[28859]: <debug> status on fs:test1_archiv returned 0 (success) Mar 12 09:23:29 testhost1 clurgmgrd[28859]: <debug> status on fs:test1_archiv returned 0 (success) Mar 12 09:24:28 testhost1 clurgmgrd[28859]: <debug> status on fs:test1_archiv returned 0 (success) Mar 12 09:24:39 testhost1 clurgmgrd[28859]: <debug> status on fs:test1_archiv returned 0 (success) Mar 12 09:25:29 testhost1 clurgmgrd[28859]: <debug> status on fs:test1_archiv returned 0 (success) Version-Release number of selected component (if applicable): 1.9.63-1 (hotfix) How reproducible: 100% Steps to Reproduce: 1. Configure a filesystem resource that uses the fs.sh agent in cluster.conf 2. Enable debug logging 3. Start cluster services and enable the service using the file system resource configured in 1. Actual results: Probe interval as logged to syslog appears to be 1m. Expected results: Probe interval matches configuration information in fs.sh
Created attachment 210411 [details] patch from Lon for the RHEL5 rgmanager
Created attachment 210551 [details] RHEL4 patch
*** Bug 310971 has been marked as a duplicate of this bug. ***
Patch in CVS [lhh@ayanami rgmanager]$ cvs commit -m "Fix #310981 - status check timers wrong" ChangeLog src/daemons/groups.c src/daemons/resrules.c src/daemons/restree.c Checking in ChangeLog; /cvs/cluster/cluster/rgmanager/ChangeLog,v <-- ChangeLog new revision: 1.5.2.32; previous revision: 1.5.2.31 done Checking in src/daemons/groups.c; /cvs/cluster/cluster/rgmanager/src/daemons/groups.c,v <-- groups.c new revision: 1.8.2.21; previous revision: 1.8.2.20 done Checking in src/daemons/resrules.c; /cvs/cluster/cluster/rgmanager/src/daemons/resrules.c,v <-- resrules.c new revision: 1.9.2.8; previous revision: 1.9.2.7 done Checking in src/daemons/restree.c; /cvs/cluster/cluster/rgmanager/src/daemons/restree.c,v <-- restree.c new revision: 1.10.2.17; previous revision: 1.10.2.16 done
Created attachment 210661 [details] ancillary patch to prevent all levels from checking sequentially
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2007-1000.html