VCS ERROR V-16-1-10205 Group Mediation_NFS is faulted on system com1em03

[Ayan1987]

Jul 25 04:09:23 com1em03 AgentFramework[24423]: VCS ERROR V-16-2-13067 Thread(139826997139200) Agent is calling clean for resource(nfsmount2) because the resource became OFFLINE unexpectedly, on its own.
Jul 25 04:09:23 com1em03 Had[5789]: VCS ERROR V-16-2-13067 (com1em03) Agent is calling clean for resource(nfsmount2) because the resource became OFFLINE unexpectedly, on its own.
Jul 25 04:09:24 com1em03 AgentFramework[24423]: VCS ERROR V-16-2-13068 Thread(139826997139200) Resource(nfsmount2) - clean completed successfully.
Jul 25 04:09:36 com1em03 Had[5789]: VCS ERROR V-16-1-10205 Group Mediation_NFS is faulted on system com1em03

[frankgfan]

Please consult with the two technotes below for the VCS errors enounterred.

https://www.veritas.com/support/en_US/article.100008146

https://sort.veritas.com/ecls/umi/V-16-1-10205

The most common causes for the VCS error "... resource became OFFLINE unexpectedly, on its own."

1.  high system load (not enough resources to run all the applications during peak load (like DB reporting, scheduled backup etc)

2. VCS controlled resources were accidentally offlined (by someone) outside VCS

recommendation - review system load patterns/resources, patch up all Veirtas software, load balances among the nodes

[meuhassan]

The error message V-16-1-10205 Group Mediation_NFS is faulted on system com1em03 indicates that the Group Mediation_NFS service on the system com1em03 has failed. This service is responsible for mediating access to NFS shares between Veritas Cluster Server (VCS) nodes. If this service fails, then NFS shares will not be accessible to VCS nodes.

There are a few things that you can check to try to fix this error:

• Make sure that the Group Mediation_NFS service is running on the system com1em03. You can check the status of the service by running the following command:

service GroupMediation_NFS status

• If the service is not running, then you can start it by running the following command:

service GroupMediation_NFS start

• If the service is running, but it is still failing, then you can try restarting the service by running the following command:

service GroupMediation_NFS restart

• If restarting the service does not fix the problem, then you may need to contact Veritas support for assistance.

Here are some additional things you can try:

• Check the VCS logs for any errors that may be related to the Group Mediation_NFS service.
• Check the NFS server logs for any errors that may be related to the Group Mediation_NFS service.
• Try restarting the NFS server.

I hope this helps! Let me know if you have any other questions.

[meuhassan]

The error messages you have provided indicate that the NFS mount on the system com1em03 has become offline unexpectedly. This could be due to a number of reasons, such as a network issue, a problem with the NFS server, or a problem with the NFS client.

The first two messages, V-16-2-13067 and V-16-2-13068, indicate that the agent is calling clean for the resource nfsmount2 because the resource became offline unexpectedly. The third message, V-16-1-10205, indicates that the Group Mediation_NFS service on the system com1em03 has faulted. This service is responsible for mediating access to NFS shares between Veritas Cluster Server (VCS) nodes. If this service fails, then NFS shares will not be accessible to VCS nodes.

To troubleshoot this issue, you will need to check the following:

• The network: Make sure that the network is up and running and that there are no problems with the network connectivity between the NFS server and the NFS client.
• The NFS server: Make sure that the NFS server is running and that it is accessible from the NFS client.
• The NFS client: Make sure that the NFS client is configured correctly and that it is able to connect to the NFS server.
• The Group Mediation_NFS service: Make sure that the Group Mediation_NFS service is running and that it is not failing.

If you have checked all of these things and you are still having problems, then you may need to contact Veritas support for assistance.

Here are some additional things you can try:

• Check the VCS logs for any errors that may be related to the NFS mount.
• Check the NFS server logs for any errors that may be related to the NFS mount.
• Try restarting the NFS server.
• Try restarting the Group Mediation_NFS service.

I hope this helps! Let me know if you have any other questions.

[frankgfan]

you need to do the followings:

1. open a support case with Veritas

2. collect and send Veritas a DataCollector report   (https://sort.veritas.com/data_collectors)

3. a detailed problem description\

with the above info, Veritas tech support should be able to determine the RCA and provide a solution