Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.

Service group concurrency violation

Created: 15 Oct 2012 • Updated: 04 Dec 2012 | 3 comments
This issue has been solved. See solution.

I have two groups for the VCS cluster, App_Cluster & App_Notifier setup in an active/passive setup. The App_Notifier runs the vcs notifer server and send out e-mail on Error level events. The App_Cluster contains all the service to be monitored. Everything is running fine, but recently with all our appliances in development we have seen an issue when we reboot the standby box we get a VCS SevereError. I am trying to track down what suddenly is causing this e-mail to be triggered.

--- Email sent ---

Sent: Sunday, October 14, 2012 11:41 PM
Subject: VCS SevereError for Service Group App_Cluster, Service group concurrency violation

Event Time: Sun 14 Oct 2012 11:41:06 PM PDT
Entity Name: App_Cluster
Entity Type: Service Group
Entity Subtype: Failover
Entity State: Service group concurrency violation
Traps Origin: Veritas_Cluster_Server
System Name: app-49-59
Entities Container Name: App
Entities Container Type: VCS

Thanks

 

 

Comments 3 CommentsJump to latest comment

Satish K. Pagare's picture

Please check whether the standby node has its init scripts set up in away to start your application services during boot time. If it is so, you need to disable it. So that whenever the standby nodes boot up, the services do not get automatically started. The automatic startup of the same services across all the nodes during boot time may lead to concurrency violation.

SOLUTION
mkruer's picture

Yep that was it, someone enabled the services to start by default.

 

Satish K. Pagare's picture

Thanks mkruer. You may want to mark the above comment as solution.