VCS ERROR V-16-2-13067 VCS ERROR V-16-2-13073
Created: 18 Dec 2012 | Updated: 18 Dec 2012 | 8 comments
Environment
OS = Solaris10
HA/VCS = 6.0
Problem
Dec 18 14:26:29 PK1PRI AgentFramework[784]: [ID 702911 daemon.notice] VCS ERROR V-16-2-13067 Thread(3) Agent is calling clean for resource(NOTIFIER) because the resource became OFFLINE unexpectedly, on its own.
Dec 18 14:26:29 PK1PRI Had[485]: [ID 702911 daemon.notice] VCS ERROR V-16-2-13067 (PK1PRI) Agent is calling clean for resource(NOTIFIER) because the resource became OFFLINE unexpectedly, on its own.
Dec 18 14:26:29 PK1PRI AgentFramework[784]: [ID 702911 daemon.notice] VCS ERROR V-16-2-13068 Thread(3) Resource(NOTIFIER) - clean completed successfully.
Dec 18 14:26:30 PK1PRI AgentFramework[784]: [ID 702911 daemon.notice] 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.
TN
Extract of TN
[ Comment ] According to Amin Guide,
Set this value to 1 if your mail server does not support SMTP VRFY command.
If this sets with value to 1, the notifier does not send a SMTP VRFY request to the mail server specified in SmtpServer attribute while sending emails.
Type and dimension: boolean-scalar Default: 0
So therefore, if this parameter is "SmtpServerVrfyOff = 0", the notifier should send a SMTP VRFY request to the mail server specified in SmtpServer attribute while sending emails accordingly.
As of now, it is a question of verifying if SMTP server supports the VCS notifer service and the SMTP VRFY command.
I saw the above TN and it seems that TN is taking about SMTP verify. All things are as it is and did not changed at any side but I am looking in to it. Any comments will be appriciated
Discussion Filed Under:
Comments 8 Comments • Jump to latest comment
The TN contains some more troubleshooting steps and logs to examine, such as Notifier_A log.
Let us know what you have found...
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links
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.
Any comment will be appreciated. Mark as Solution if your query is resolved
__________________
Thanks in Advance
Zahid Haseeb
zahidhaseeb.wordpress.com
As per the TN
http://www.symantec.com/business/support/index?pag... there is another TN in it talks about below errors
2002/12/06 11:01:57 VCS:17030:Notifier:cannot verify recipient
Any comment will be appreciated. Mark as Solution if your query is resolved
__________________
Thanks in Advance
Zahid Haseeb
zahidhaseeb.wordpress.com
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
UK Symantec Consultant in VCS, GCO, SF, VVR, VxAT on Solaris, AIX, HP-ux, Linux & Windows
If this post has helped you, please vote or mark as solution
http://www.symantec.com/business/support/index?pag...
Any comment will be appreciated. Mark as Solution if your query is resolved
__________________
Thanks in Advance
Zahid Haseeb
zahidhaseeb.wordpress.com
Easy - find PID in 'ps -ef' output, then run 'kill <PID>'.
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links
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
Any comment will be appreciated. Mark as Solution if your query is resolved
__________________
Thanks in Advance
Zahid Haseeb
zahidhaseeb.wordpress.com
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 :)
Any comment will be appreciated. Mark as Solution if your query is resolved
__________________
Thanks in Advance
Zahid Haseeb
zahidhaseeb.wordpress.com
Would you like to reply?
Login or Register to post your comment.