Cluster Server 7.4.1 Administrator's Guide - Linux
- Section I. Clustering concepts and terminology
- Introducing Cluster Server
- About Cluster Server
- About cluster control guidelines
- About the physical components of VCS
- Logical components of VCS
- Types of service groups
- About resource monitoring
- Agent classifications
- About cluster control, communications, and membership
- About security services
- Components for administering VCS
- About cluster topologies
- VCS configuration concepts
- Introducing Cluster Server
- Section II. Administration - Putting VCS to work
- About the VCS user privilege model
- Administering the cluster from the command line
- About administering VCS from the command line
- About installing a VCS license
- Administering LLT
- Starting VCS
- Stopping the VCS engine and related processes
- Logging on to VCS
- About managing VCS configuration files
- About managing VCS users from the command line
- About querying VCS
- About administering service groups
- Modifying service group attributes
- About administering resources
- Enabling and disabling IMF for agents by using script
- Linking and unlinking resources
- About administering resource types
- About administering clusters
- Configuring applications and resources in VCS
- VCS bundled agents for UNIX
- Configuring NFS service groups
- About NFS
- Configuring NFS service groups
- Sample configurations
- About configuring the RemoteGroup agent
- About configuring Samba service groups
- About testing resource failover by using HA fire drills
- Predicting VCS behavior using VCS Simulator
- Section III. VCS communication and operations
- About communications, membership, and data protection in the cluster
- About cluster communications
- About cluster membership
- About membership arbitration
- About membership arbitration components
- About server-based I/O fencing
- About majority-based fencing
- About the CP server service group
- About secure communication between the VCS cluster and CP server
- About data protection
- Examples of VCS operation with I/O fencing
- About cluster membership and data protection without I/O fencing
- Examples of VCS operation without I/O fencing
- Administering I/O fencing
- About the vxfentsthdw utility
- Testing the coordinator disk group using the -c option of vxfentsthdw
- About the vxfenadm utility
- About the vxfenclearpre utility
- About the vxfenswap utility
- About administering the coordination point server
- About configuring a CP server to support IPv6 or dual stack
- About migrating between disk-based and server-based fencing configurations
- Migrating between fencing configurations using response files
- Controlling VCS behavior
- VCS behavior on resource faults
- About controlling VCS behavior at the service group level
- About AdaptiveHA
- Customized behavior diagrams
- About preventing concurrency violation
- VCS behavior for resources that support the intentional offline functionality
- VCS behavior when a service group is restarted
- About controlling VCS behavior at the resource level
- VCS behavior on loss of storage connectivity
- Service group workload management
- Sample configurations depicting workload management
- The role of service group dependencies
- About communications, membership, and data protection in the cluster
- Section IV. Administration - Beyond the basics
- VCS event notification
- VCS event triggers
- Using event triggers
- List of event triggers
- Virtual Business Services
- Section V. Veritas High Availability Configuration wizard
- Introducing the Veritas High Availability Configuration wizard
- Administering application monitoring from the Veritas High Availability view
- Administering application monitoring from the Veritas High Availability view
- Administering application monitoring from the Veritas High Availability view
- Section VI. Cluster configurations for disaster recovery
- Connecting clusters–Creating global clusters
- VCS global clusters: The building blocks
- About global cluster management
- About serialization - The Authority attribute
- Prerequisites for global clusters
- Setting up a global cluster
- About IPv6 support with global clusters
- About cluster faults
- About setting up a disaster recovery fire drill
- Test scenario for a multi-tiered environment
- Administering global clusters from the command line
- About global querying in a global cluster setup
- Administering clusters in global cluster setup
- Setting up replicated data clusters
- Setting up campus clusters
- Connecting clusters–Creating global clusters
- Section VII. Troubleshooting and performance
- VCS performance considerations
- How cluster components affect performance
- How cluster operations affect performance
- VCS performance consideration when a system panics
- About scheduling class and priority configuration
- VCS agent statistics
- About VCS tunable parameters
- Troubleshooting and recovery for VCS
- VCS message logging
- Gathering VCS information for support analysis
- Troubleshooting the VCS engine
- Troubleshooting Low Latency Transport (LLT)
- Troubleshooting Group Membership Services/Atomic Broadcast (GAB)
- Troubleshooting VCS startup
- Troubleshooting issues with systemd unit service files
- Troubleshooting service groups
- Troubleshooting resources
- Troubleshooting sites
- Troubleshooting I/O fencing
- Fencing startup reports preexisting split-brain
- Troubleshooting CP server
- Troubleshooting server-based fencing on the VCS cluster nodes
- Issues during online migration of coordination points
- Troubleshooting notification
- Troubleshooting and recovery for global clusters
- Troubleshooting licensing
- Licensing error messages
- Troubleshooting secure configurations
- Troubleshooting wizard-based configuration issues
- Troubleshooting issues with the Veritas High Availability view
- VCS message logging
- VCS performance considerations
- Section VIII. Appendixes
If a unit service has failed and the corresponding module is still loaded, systemd cannot unload it and so its package cannot be removed
A unit service may go into the Failed state during startup while the corresponding module is in the Loaded state due to some configuration issue. If this situation occurs, the module cannot be cleanly unloaded using systemd commands.
For example, you may encounter this message when you start the vxfen
service:
localhost]:~ # systemctl start vxfen Job for vxfen.service failed because the control process exited with error code. See "systemctl status vxfen.service" and "journalctl -xe" for details.
If you encounter this message, view the status of service:
localhost]:~ # systemctl status -l vxfen ? vxfen.service - VERITAS I/O Fencing (VxFEN) Loaded: loaded (/opt/VRTSvcs/vxfen/bin/vxfen; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Wed 2017-04-19 17:40:13 IST; 14s ago Process: 14721 ExecStart=/opt/VRTSvcs/vxfen/bin/vxfen start 2>&1 (code=exited, status=1/FAILURE) Apr 19 17:40:12 localhost] systemd[1]: Starting VERITAS I/O Fencing (VxFEN)... Apr 19 17:40:12 localhost] vxfen[14721]: Starting vxfen.. Apr 19 17:40:12 localhost] vxfen[14721]: Loaded 4.4.21-69-default on kernel 4.4.21-69-default Apr 19 17:40:13 localhost] vxfen[14721]: vxfen cannot generate vxfentab due to missing file /etc/vxfendg. Apr 19 17:40:13 localhost] systemd[1]: vxfen.service: Control process exited, code=exited status=1 Apr 19 17:40:13 localhost] systemd[1]: Failed to start VERITAS I/O Fencing (VxFEN). Apr 19 17:40:13 localhost] systemd[1]: vxfen.service: Unit entered failed state. Apr 19 17:40:13 localhost] systemd[1]: vxfen.service: Failed with result 'exit-code'.
Then, view the status of the module:
localhost]:~ # lsmod | grep vxfen vxfen 372992 0 veki 19214 4 gab,llt,vxfen localhost]:~ # /opt/VRTSvcs/vxfen/bin/vxfen status loaded
The systemd daemon does not accept a systemctl stop unitServiceFile command when the service is in the Failed state or the Inactive state.
For example, if the vxfen
service is in the Failed or the Inactive state, the following command fails to unload the module successfully:
systemctl stop vxfen
Additionally, if a module is in the Loaded state, the corresponding rpm package cannot be removed during uninstallation.
Recommended action
To cleanly stop and unload the module, run the stop command from the source script file as follows:
serviceSourceScript stop
For example:
localhost]:~ # /opt/VRTSvcs/vxfen/bin/vxfen stop VxFEN: Module already unconfigured. Only unloading localhost]:~ #/opt/VRTSvcs/vxfen/bin/vxfen status not loaded
To view the source path of any service, you can use the systemctl command as follows:
# systemctl show unitServiceFile -p SourcePath
For example:
# systemctl show vxfen -p SourcePath SourcePath=/opt/VRTSvcs/vxfen/bin/vxfen
After the module is cleanly unloaded, you can perform the next startup action or proceed to uninstall the associated package.