Veritas Access Troubleshooting Guide

Last Published:
Product(s): Appliances (7.3.2)
Platform: 3340
  1. Introduction
    1.  
      About troubleshooting
    2.  
      General tips for the troubleshooting process
    3.  
      General techniques for the troubleshooting process
  2. General troubleshooting procedures
    1.  
      About general troubleshooting procedures
    2.  
      Viewing the Veritas Access log files
    3.  
      About event logs
    4.  
      About shell-activity logs
    5.  
      Setting the CIFS log level
    6.  
      Setting the NetBackup client log levels and debugging options
    7.  
      Retrieving and sending debugging information
    8.  
      Insufficient delay between two successive OpenStack commands may result in failure
  3. Monitoring Veritas Access
    1.  
      About monitoring Veritas Access operations
    2.  
      Monitoring processor activity
    3.  
      Generating CPU and device utilization reports
    4.  
      Monitoring network traffic
    5.  
      Exporting and displaying the network traffic details
  4. Common recovery procedures
    1.  
      About common recovery procedures
    2.  
      Restarting servers
    3. Bringing services online
      1.  
        Using the services command
    4.  
      Recovering from a non-graceful shutdown
    5.  
      Testing the network connectivity
    6.  
      Troubleshooting with traceroute
    7.  
      Using the traceroute command
    8.  
      Collecting the metasave image of a file system
    9.  
      Replacing an Ethernet interface card
    10. Speeding up replication
      1.  
        About synchronizing a replication job
      2.  
        Synchronizing an episodic replication job
    11.  
      Uninstalling a patch release or software upgrade
  5. Troubleshooting the Veritas Access cloud as a tier feature
    1.  
      Troubleshooting tips for cloud tiering
    2.  
      Issues when reading or writing data from the cloud tier
    3.  
      Log locations for checking for cloud tiering errors
  6. Troubleshooting Veritas Access installation and configuration issues
    1.  
      How to find the management console IP
    2.  
      Viewing the installation logs
    3.  
      Installation fails and does not complete
    4.  
      Excluding PCI IDs from the cluster
    5.  
      Cannot recover from root file system corruption
    6.  
      The storage disk list command returns nothing
  7. Troubleshooting Veritas Access CIFS issues
    1.  
      User access is denied on a CTDB directory share
  8. Troubleshooting Veritas Access GUI startup issues
    1.  
      Resolving GUI startup issues

Recovering from a non-graceful shutdown

In some cases, when a non-graceful shutdown of a node occurs (for example, during an unexpected system halt or power failure), you may receive an error message on the local node asking you to use the Linux fsck (file system check) command to repair files on the node.

Attempting to use the fsck command to repair the node is not recommended (and may not be possible). Instead, use a healthy node in the cluster to reinstall Veritas Access software on the damaged node.

To recover a node

  1. Use the master account to log into Veritas Access.
  2. Delete the failed node from the cluster. To delete the node, enter the following:
    Cluster> del nodename

    where nodename is the name of the failed node.

    For example:

    Cluster > del access_01

    Note:

    The failed node information is deleted from the cluster. When the failed node is rebooting, it will detect that it has been deleted and clean itself up.

  3. After the node is deleted from the cluster, reboot the deleted node and then it is reachable using its original physical IP address (before the node had been added to the cluster).
  4. Add the node back by entering the following:
    Cluster> add nodeip

    where nodeip is the reachable IP address of the deleted node.

    For example:

    Cluster > add 172.16.113.118