Veritas InfoScale™ 7.4.2 Installation Guide - Linux
- Section I. Planning and preparation
- Introducing Veritas InfoScale
- Licensing Veritas InfoScale
- System requirements
- Preparing to install
- Setting up the private network
- Setting up shared storage
- Planning the installation setup for SF Oracle RAC and SF Sybase CE systems
- Section II. Installation of Veritas InfoScale
- Installing Veritas InfoScale using the installer
- Installing Veritas InfoScale using response files
- Installing Veritas Infoscale using operating system-specific methods
- Completing the post installation tasks
- Section III. Uninstallation of Veritas InfoScale
- Section IV. Installation reference
- Appendix A. Installation scripts
- Appendix B. Tunable files for installation
- Appendix C. Troubleshooting installation issues
Setting the kernel.hung_task_panic tunable
The topic applies to SFHA, SFCFSHA, and VCS.
By default, in the Linux kernel the kernel.hung_task_panic tunable is enabled and the kernel.hung_task_timeout_secs tunable is set to a default non-zero value.
To ensure that the node does not panic, the kernel.hung_task_panic tunable must be disabled. If kernel.hung_task_panic is enabled, then it causes the kernel to panic when any of the following kernel threads waits for more than the kernel.hung_task_timeout_secs value:
The vxfenconfig thread in the vxfen configuration path waits for GAB to seed.
The vxfenswap thread in the online coordinator disks replacement path waits for the snapshot of peer nodes of the new coordinator disks.
To disable the kernel.hung_task_panic tunable:
Set the kernel.hung_task_panic tunable to zero (0) in the
/etc/sysctl.conf
file. This step ensures that the change is persistent across node restarts.Run the command on each node.
# sysctl -w kernel.hung_task_panic=0
To verify the kernel.hung_task_panic tunable value, run the following command:
# sysctl -a | grep hung_task_panic