Forum Discussion

Arut's avatar
17 years ago

monitor procedure did not complete within the expected time - Error with VCS 4.1

I am facing this unique issue with Solaris 10 and VCS 4.1 monitor procedure did not complete within the expected time and its brought Sybase Service group offline.
No spike in I/O, CPU/MEM - all was normal during this issue.
 
I suspected the MonitorReservation type and deleted it from the DiskGroup type.
 
I need what is the use of MonitorReservation attribute and did any one seen this issue and have fix for it.
 
 
Following is the Error log from the Engine_a.log
 
2008/03/04 17:11:52 VCS ERROR V-16-2-13027 (nodea) Resource(vxdg_DB03_datadg) - monitor procedure did not complete within the expected time.
2008/03/04 17:12:53 VCS ERROR V-16-2-13027 (nodea) Resource(vxdg_DB01_dumpdg) - monitor procedure did not complete within the expected time.
2008/03/04 17:13:05 VCS ERROR V-16-2-13027 (nodea) Resource(mnt_app_sybase_DB03) - monitor procedure did not complete within the expected time.
2008/03/04 17:13:54 VCS ERROR V-16-2-13027 (nodea) Resource(vxdg_DB01_datadg) - monitor procedure did not complete within the expected time.
2008/03/04 17:14:55 VCS ERROR V-16-2-13027 (nodea) Resource(vxdg_DB03_dumpdg) - monitor procedure did not complete within the expected time.
2008/03/04 17:19:06 VCS ERROR V-16-2-13210 (nodea) Agent is calling clean for resource(mnt_app_sybase_DB03) because 4 successive invocations of the monitor procedure did not complete within the expected time.
2008/03/04 17:19:19 VCS INFO V-16-2-13026 (nodea) Resource(vxdg_DB01_dumpdg) - monitor procedure finished successfully after failing to complete within the expected time for (2) consecutive times.
2008/03/04 17:19:21 VCS INFO V-16-2-13026 (nodea) Resource(vxdg_DB01_datadg) - monitor procedure finished successfully after failing to complete within the expected time for (2) consecutive times.
2008/03/04 17:19:23 VCS INFO V-16-2-13068 (nodea) Resource(mnt_app_sybase_DB03) - clean completed successfully.
2008/03/04 17:19:23 VCS ERROR V-16-2-13074 (nodea) The monitoring program for resource(mnt_app_sybase_DB03) has consistently failed to determine the resource status within the expected time. Agent is restarting (attempt number 1 of 3) the resource.
2008/03/04 17:19:27 VCS INFO V-16-2-13026 (nodea) Resource(mnt_app_sybase_DB03) - monitor procedure finished successfully afterfailing to complete within the expected time for (4) consecutive times.
2008/03/04 17:19:27 VCS NOTICE V-16-2-13076 (nodea) Agent has successfully restarted resource(mnt_app_sybase_DB03).
2008/03/04 17:19:52 VCS INFO V-16-2-13026 (nodea) Resource(vxdg_DB03_datadg) - monitor procedure finished successfully after failing to complete within the expected time for (3) consecutive times.
2008/03/04 17:20:10 VCS ERROR V-16-2-13067 (nodea) Agent is calling clean for resource(mnt_app_sybase_DB03_tempdb) because the resource became OFFLINE unexpectedly, on its own.
2008/03/04 17:20:15 VCS ERROR V-16-2-13067 (nodea) Agent is calling clean for resource(syb_DB03) because the resource became OFFLINE unexpectedly, on its own.
2008/03/04 17:20:15 VCS INFO V-16-2-13068 (nodea) Resource(mnt_app_sybase_DB03_tempdb) - clean completed successfully.
2008/03/04 17:20:15 VCS ERROR V-16-2-13073 (nodea) Resource(mnt_app_sybase_DB03_tempdb) became OFFLINE unexpectedly on its own. Agent is restarting (attempt number 1 of 3) the resource.
2008/03/04 17:20:16 VCS INFO V-16-2-13068 (nodea) Resource(syb_DB03) - clean completed successfully.
2008/03/04 17:20:17 VCS INFO V-16-1-10307 Resource syb_DB03 (Owner: unknown, Group: sg_DB03) is offline on nodea (Not initiated by VCS)
2008/03/04 17:20:17 VCS NOTICE V-16-1-10446 Group sg_DB03 is offline on system nodea