In 5.1SP1, a new behavior to the Application resource is introduced when the CleanProgram is not defined
| Article:TECH164781 | | | Created: 2011-07-15 | | | Updated: 2012-08-21 | | | Article URL http://www.symantec.com/docs/TECH164781 |
| NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made. |
Problem
When the CleanProgram attribute is not defined in the Application resource, the StopProgram will be called. This is a different behavior than versions prior to 5.1SP1 . In some cases the older behaviour may be desired.
Error
from VCS engine log (/var/VRTSvcs/log/engine_A.log
2011/06/14 13:56:03 VCS ERROR V-16-2-13027 (sdal562) Resource(febiccp_sdal562_APP_Oracle_ias10gR3) - monitor procedure did not complete within the expected time.
2011/06/14 14:02:03 VCS ERROR V-16-2-13210 (sdal562) Agent is calling clean for resource(febiccp_sdal562_APP_Oracle_ias10gR3) because 4 successive invocations of the monitor procedure did not complete within the expected time.
2011/06/14 14:03:04 VCS ERROR V-16-2-13006 (sdal562) Resource(febiccp_sdal562_APP_Oracle_ias10gR3): clean procedure did not complete within the expected time.
2011/06/14 14:04:21 VCS INFO V-16-2-13026 (sdal562) Resource(febiccp_sdal562_APP_Oracle_ias10gR3) - monitor procedure finished successfully after failing to complete within the expected time for (4) consecutive times.
2011/06/14 14:04:21 VCS ERROR V-16-2-13067 (sdal562) Agent is calling clean for resource(febiccp_sdal562_APP_Oracle_ias10gR3) because the resource became OFFLINE unexpectedly, on its own.
2011/06/14 14:05:00 VCS ERROR V-16-2-13069 (sdal562) Resource(febiccp_sdal562_APP_Oracle_ias10gR3) - clean failed.
2011/06/14 14:22:37 VCS ERROR V-16-2-13079 (sdal562) Resource(febiccp_sdal562_APP_Oracle_ias10gR3): The last 10 invocations of the clean procedure have failed.
Environment
Storage Foundation HA 5.1SP1
Solaris 10
This issue may be seen on other supported OS platforms.
Cause
Product design change.
Solution
Work-around:
Define CleanProgram that exits with true status.
Example shell script
=================================================
#! <location of sh binary>
exit 0
=================================================
The first line defines the location of the shell (bourne).
The second line exits with a successful exit code.
|
|
Article URL http://www.symantec.com/docs/TECH164781
Terms of use for this information are found in Legal Notices
Thank you.