VCS ERROR V-16-2-13067 VCS ERROR V-16-2-13073

The TN contains some more troubleshooting steps and logs to examine, such as Notifier_A log.

Let us know what you have found...

NotifierMngr_A.log

2012/12/18 13:56:29 VCS ERROR V-16-2-13067 Thread(3) Agent is calling clean for resource(NOTIFIER) because the resource became OFFLINE unexpectedly, on its own.
2012/12/18 13:56:29 VCS ERROR V-16-2-13068 Thread(3) Resource(NOTIFIER) - clean completed successfully.
2012/12/18 13:56:30 VCS ERROR V-16-2-13073 Thread(3) Resource(NOTIFIER) became OFFLINE unexpectedly on its own. Agent is restarting (attempt number 1 of 3) the resource.
2012/12/18 14:26:29 VCS ERROR V-16-2-13067 Thread(3) Agent is calling clean for resource(NOTIFIER) because the resource became OFFLINE unexpectedly, on its own.
2012/12/18 14:26:29 VCS ERROR V-16-2-13068 Thread(3) Resource(NOTIFIER) - clean completed successfully.
2012/12/18 14:26:30 VCS ERROR V-16-2-13073 Thread(3) Resource(NOTIFIER) became OFFLINE unexpectedly on its own. Agent is restarting (attempt number 1 of 3) the resource.
2012/12/18 14:28:30 VCS ERROR V-16-2-13067 Thread(3) Agent is calling clean for resource(NOTIFIER) because the resource became OFFLINE unexpectedly, on its own.
2012/12/18 14:28:30 VCS ERROR V-16-2-13068 Thread(3) Resource(NOTIFIER) - clean completed successfully.
2012/12/18 14:28:30 VCS ERROR V-16-2-13073 Thread(3) Resource(NOTIFIER) became OFFLINE unexpectedly on its own. Agent is restarting (attempt number 2 of 3) the resource.

As per the TN

http://www.symantec.com/business/support/index?page=content&pmv=print&impressions=&viewlocale=&id=TECH150538  there is another TN in it talks about below errors

If you think VRFY may be an issue, then just set SmtpServerVrfyOff=1 to disable VRFY and then generate an event that will send a notification (like fault a resource) and see if resource fails and if it doesn't then repeat test with SmtpServerVrfyOff=0 to confirm this is the problem.

If environment is live, then just create a dummy service group with a FileOnOff resource, so that you test.

Mike

• Suppose my SMTP Server support VRFY but I dont want to enable VRFY at Veritas Cluster notifier resource end. would that be a impact ?

• Second : As per the below TN . It says that """" As the error indicates, the resource stopped outside of VCS, meaning that the offline status was not initiated by the cluster. """" . My question here, how the Notifier Resource can stopped outside of VCS,

http://www.symantec.com/business/support/index?page=content&id=TECH189464

My question here, how the Notifier Resource can stopped outside of VCS,

Easy - find PID in 'ps -ef' output, then run 'kill <PID>'.

Thanks marianne I totally skipped this way :( ....

Any way/log to check if someone stopped Notifier outside from VCS ? As the last TN i shared says that this ERROR is just because the Resource stopped outside from VCS

I have shared the same with Symantec Support with VXexplorer logs but got a reply that they(Symantec Support) as well not able to find cause of this issue. Now as per Symantec Support suggesstion I enabled the DEBUG logs and waiting for reoccurance of same issue.

Meanwhile any response will be highly appriciated :)

This issue is being generated usually when NotifierMngr is unable to connect to Notifier engine port (had daemon is managing this port)

NotifierMngr resources are then existting and creating coredump in /opt/VRTSvcs/bin/NotifierMngr/ (Solaris 10, depends on your install location).

Issue can appear on the systems where had daemon is running for a long time. To resolve the issue, usually 'hastop -local -force; hastart'  can help. Then you should not receive the errors ;)

S.