04-08-2013 09:12 PM
2013/04/08 01:12:02 VCS WARNING V-16-10031-4604 (abc-db2) IP:OracleIpRes:online:Address 2001:1b70:0200:1026:0000:0000:0131:0132 already exists: Res OracleIpRes will not go online.2013/04/08 01:12:03 VCS ERROR V-16-2-13066 (abc-db2) Agent is calling clean for resource(OracleIpRes) because the resource is not up even after online completed.2013/04/08 01:12:04 VCS INFO V-16-2-13716 (abc-db2) Resource(OracleIpRes): Output of the completed operation (clean)==============================================RTNETLINK answers: Cannot assign requested address==============================================2013/04/08 01:12:04 VCS INFO V-16-2-13068 (abc-db2) Resource(OracleIpRes) - clean completed successfully.
Solved! Go to Solution.
04-08-2013 11:18 PM
Hi kongzzzz,
State of any resource changes only after monitor reports state change.
After online/offline/clean generally monitor is scheduled immediately. Once monitor report state change then only resource state is updated.
In your case of IP resource,
2013/04/08 01:12:02 VCS WARNING V-16-10031-4604 (abc-db2) IP:OracleIpRes:online:Address 2001:1b70:0200:1026:0000:0000:0131:0132 already exists: Res OracleIpRes will not go online.
>> Online failed to bring IP online.
>> Monitor was invoked after online completed to check state of the resource.
2013/04/08 01:12:03 VCS ERROR V-16-2-13066 (abc-db2) Agent is calling clean for resource(OracleIpRes) because the resource is not up even after online completed.
>> Monitor correctly detected that IP is not online and reported resource offline.
>> Resrouce was expected to be online after online. However, it was detected offline, so clean was called.
2013/04/08 01:12:04 VCS INFO V-16-2-13716 (abc-db2) Resource(OracleIpRes): Output of the completed operation (clean)
==============================================
RTNETLINK answers: Cannot assign requested address
==============================================
2013/04/08 01:12:04 VCS INFO V-16-2-13068 (abc-db2) Resource(OracleIpRes) - clean completed successfully.
There is no added delay like sleep introduced by VCS, it only time taken by online + monitor or clean + monitor that may come up to one sec.
Hope this answers your query!
Thanks and Regards,
Paresh Bafna
04-08-2013 10:14 PM
New findings, not only IP resource, cleaning the other resources also takes 1 seconds, is it a regular pattern that VCS reports clean completed in next second and continue next actions?
04-08-2013 11:18 PM
Hi kongzzzz,
State of any resource changes only after monitor reports state change.
After online/offline/clean generally monitor is scheduled immediately. Once monitor report state change then only resource state is updated.
In your case of IP resource,
2013/04/08 01:12:02 VCS WARNING V-16-10031-4604 (abc-db2) IP:OracleIpRes:online:Address 2001:1b70:0200:1026:0000:0000:0131:0132 already exists: Res OracleIpRes will not go online.
>> Online failed to bring IP online.
>> Monitor was invoked after online completed to check state of the resource.
2013/04/08 01:12:03 VCS ERROR V-16-2-13066 (abc-db2) Agent is calling clean for resource(OracleIpRes) because the resource is not up even after online completed.
>> Monitor correctly detected that IP is not online and reported resource offline.
>> Resrouce was expected to be online after online. However, it was detected offline, so clean was called.
2013/04/08 01:12:04 VCS INFO V-16-2-13716 (abc-db2) Resource(OracleIpRes): Output of the completed operation (clean)
==============================================
RTNETLINK answers: Cannot assign requested address
==============================================
2013/04/08 01:12:04 VCS INFO V-16-2-13068 (abc-db2) Resource(OracleIpRes) - clean completed successfully.
There is no added delay like sleep introduced by VCS, it only time taken by online + monitor or clean + monitor that may come up to one sec.
Hope this answers your query!
Thanks and Regards,
Paresh Bafna
04-09-2013 02:00 AM
I guess you are only testing clean for one scenerio - IP already exists - there are 3 main reasons why clean can be called:
Clean time could vary for each of these and in particular for reason 3 and for each of these 3 reasons there are different reasons that could cause each of them, so clean time could vary for say different events causing reason 1. Also there are extenal factors such as the system is busy which could effect how long the clean runs.
Mike
04-09-2013 09:31 PM
Thanks all! My question is answered.