Node panics due to client process failure


Node panics due to client process failure
Prev	Troubleshooting Group Membership Services/Atomic Broadcast (GAB)	Next

If VCS daemon does not heartbeat with GAB within the configured timeout specified in VCS_GAB_TIMEOUT (default 30sec) environment variable, the node panics with a message similar to the following:

GAB Port h halting node due to client process failure at 3:109

GABs attempt (five retries) to kill the VCS daemon fails if VCS daemon is stuck in the kernel in an uninterruptible state or the system is heavily loaded that the VCS daemon cannot die with a SIGKILL.

Recommended Action:

In case of performance issues, increase the value of the VCS_GAB_TIMEOUT environment variable to allow VCS more time to heartbeat.

See VCS environment variables.
In case of a kernel problem, configure GAB to not panic but continue to attempt killing the VCS daemon.
Do the following:
- Run the following command on each node:
```
gabconfig -k
```
- Add the "-k" option to the gabconfig command in the /etc/gabtab file:
```
gabconfig -c -k -n 6
```
In case the problem persists, collect sar or similar output, collect crash dumps, run the Symantec Operations and Readiness Tools (SORT) data collector on all nodes, and contact Symantec Technical Support.

Prev	Up	Next
Delay in port reopen	Home	Troubleshooting VCS startup