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

[Zahid_Haseeb]

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

http://www.symantec.com/business/support/index?page=content&pmv=print&impressions=&viewlocale=&id=TE...

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

[Marianne]

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

Let us know what you have found...

[Zahid_Haseeb]

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.

[Zahid_Haseeb]

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

2002/12/06 11:01:57 VCS:17036:Notifier:SMTP error 17030
2002/12/06 11:01:57 VCS:17030:Notifier:cannot verify recipient

But in my Engine log and the NotifierMngr logs , both does not have any error like this so I can imagine that my SMTP Server support VERFY command.

[mikebounds]

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

[Zahid_Haseeb]

• 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

[Marianne]

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

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

[Zahid_Haseeb]

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

[Zahid_Haseeb]

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 :)

[stib]

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.

[Zahid_Haseeb · Accepted solution]

Thanks all. Problem near to resolved/resolved:

https://www-secure.symantec.com/connect/forums/v-16-1-17037-v-16-1-17013-notifier-resources-faulted-atleast-one-time-month