Veritas InfoScale™ 7.3.1 Troubleshooting Guide - Solaris
- Introduction
- Section I. Troubleshooting Veritas File System
- Section II. Troubleshooting Veritas Volume Manager
- Recovering from hardware failure
- Failures on RAID-5 volumes
- Recovery from failure of a DCO volume
- Recovering from instant snapshot failure
- Recovering from failed vxresize operation
- Recovering from boot disk failure
- Hot-relocation and boot disk failure
- Recovery from boot failure
- Repair of root or /usr file systems on mirrored volumes
- Replacement of boot disks
- Recovery by reinstallation
- Managing commands, tasks, and transactions
- Backing up and restoring disk group configurations
- Troubleshooting issues with importing disk groups
- Recovering from CDS errors
- Logging and error messages
- Troubleshooting Veritas Volume Replicator
- Recovery from configuration errors
- Errors during an RLINK attach
- Errors during modification of an RVG
- Recovery on the Primary or Secondary
- Recovering from Primary data volume error
- Primary SRL volume error cleanup and restart
- Primary SRL header error cleanup and recovery
- Secondary data volume error cleanup and recovery
- Troubleshooting issues in cloud deployments
- Recovering from hardware failure
- Section III. Troubleshooting Dynamic Multi-Pathing
- Section IV. Troubleshooting Storage Foundation Cluster File System High Availability
- Troubleshooting Storage Foundation Cluster File System High Availability
- Troubleshooting CFS
- Troubleshooting fenced configurations
- Troubleshooting Cluster Volume Manager in Veritas InfoScale products clusters
- Troubleshooting Storage Foundation Cluster File System High Availability
- Section V. Troubleshooting Cluster Server
- 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 service groups
- Troubleshooting resources
- Troubleshooting I/O fencing
- System panics to prevent potential data corruption
- Fencing startup reports preexisting split-brain
- Troubleshooting CP server
- Troubleshooting server-based fencing on the Veritas InfoScale products cluster nodes
- Issues during online migration of coordination points
- Troubleshooting notification
- Troubleshooting and recovery for global clusters
- Troubleshooting licensing
- Licensing error messages
- VCS message logging
- Troubleshooting and recovery for VCS
- Section VI. Troubleshooting SFDB
Task logs
The tasks that are created on the system are logged for diagnostic purposes in the tasklog
file in the /etc/vx/log/
directory. This file logs an entry for all task-related operations (creation, completion, pause, resume, and abort). The size of the task log is checked after an entry has been written, so the actual size may be slightly larger than the size specified. When the log reaches the maximum size, the current task log file, tasklog
, is renamed as the next available historic log file. Historic task log files are named tasklog.1
, tasklog.2
, and so on up to tasklog.5
. A maximum of five historic log files are tracked.
Each log file contains a header that records the host name, host ID, and the date and time that the log was created. The following are sample entries from a task log file:
# 159571211, 16905, Thu Aug 21 02:54:18 2014 184 - SNAPSYNC Starting 00.00% 0/65536/0 SNAPSYNC full1-v1 vvrdg # 455972214, 16929, Thu Aug 21 02:54:24 2014 184 - SNAPSYNC Finishing 96.88% 0/65536/63488 SNAPSYNC full1-v1 vvrdg
Each entry contains two lines. The first line contains the following:
The client ID that identifies the connection to the vxconfigd daemon.
The process ID of the command that causes the task state to change.
A timestamp.
The client ID is the same as the one recorded for the corresponding command and transactions in command log and transaction log respectively.
The second line contains task-related information in the following format:
<id> <parent_id> <type> <state> <progress status> <desc> <nodename> <additional_flags> <id> : task id <parent_id> : task id of parent task. If the task does not have parent then '-' is reported <type> : The Type of Task <state> : Starting/Pausing/Resuming/Aborting/Finishing <progress status> : % progress followed by the triplet (start_offset/end_offset/current_offset) or for parent task (total_child_tasks/finished_child_tasks/active_child_tasks). <desc> : Description of the task and objects involved. <nodename> : optional nodedname. <additional_flags> : optional flags such as auto-throttled, smartmove.