Veritas Access Troubleshooting Guide

Last Published:
Product(s): Access (7.3.1)
Platform: Linux
  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

Retrieving and sending debugging information

You can retrieve Veritas Access debugging information from a Veritas Access node and send the information to a server using an external FTP or SCP server.

See the following article for more information on how to provide data for Veritas Technical Support:

http://www.veritas.com/docs/000097935

To upload debugging information from a specified node to an external server

  • Upload debugging information from a specified node to an external server.
    Support> debuginfo upload nodename debug-URL module

    For example, to upload all debugging information to an FTP server:

    Support> debuginfo upload node1_1
ftp://admin@ftp.docserver.company.com/patches/ all

    For example, to upload CIFS-related debugging information to an SCP server:

    Support> debuginfo upload node1_1
scp://root@server.company.com:/tmp/node1_1-cifs-debuginfo.tar.gz

    nodename

    Specifies the nodename from which to collect the debugging information.

    debug-URL

    Specifies the remote file or directory for uploading debugging information.

    Depending on the type of server from which you upload debugging information, use one of the following example URL formats: 

    ftp://admin@ftp.docserver.company.com/
patches/
    scp://root@server.company.com:/tmp/

    If debug-URL specifies a remote file, the debuginfo file is saved by that name. If debug-URL specifies a remote directory, the debuginfo file name displays as the following:

    nas_debuginfo_nodename_modulename_timestamp.tar.gz

    module

    Specifies the values for module.

    Supported module values are the following:

    • all - use to collect all information for debugging

    • generic - use to collect all debugging information except for information related to Veritas products

    • cifs - use to collect CIFS-related debugging information

    • nas - use to collect Veritas Access related debugging information

    • netbackup - use to collect NetBackup client-related debugging information

    The Support> debuginfo command also collects information for the sosreport command for Red Hat Enterprise Linux (RHEL). The sosreport is collected for all the loaded modules except for the selinux module.