Veritas Access 7.3 Troubleshooting Guide

Last Published:
Product(s): Access (7.3)
Platform: Linux
  1. Introduction
    1.  
      About troubleshooting
    2.  
      General tips for the troubleshooting process
    3.  
      General techniques for the troubleshooting process
    4.  
      About the support user account
    5.  
      Configuring the support user account
    6.  
      Using the support login
  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 a 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

Using the support login

When you log in as support, you can access logs and other files that reside outside the CLISH. Some of the troubleshooting techniques in this guide require that you log in as the support user.

The support user account must be enabled by an administrator with the master role.

Note:

The support account is intended for Technical Support and advanced users only.

To use the support login

  1. Log in to the physical IP address of the cluster using the support account by entering:
    support

    Then enter the password. The default password is: 

    veritas

    For example, 

    login as: support
support@<ip_address>'s password:
Last login: Tue Apr 26 14:53:32 2016 from ip_address
***********************************************************
*                    Veritas Access                       *
*                                                         *
*                   Enterprise Edition                    *
*       Warning: Only Veritas Access distributed          *
*     patches & RPMs can be installed on this system!     *
*    Do not delete contents of lost+found directory of    *
*    filesystems as it may contain critical temporary     *
*          Veritas Access configuration data!             *
***********************************************************

WARNING: System configured with default password. It's recommended to 
change password now. Please proceed with changing the password :

Changing password for support.
New password:
Re-enter new password:
Password changed
Default password is changed successfully on all the nodes.
ACCESSRC2_01:~ #
  2. If you need to access the CLISH, you can use the following command:
    su - master

More Information

Configuring the support user account