DriveScale Proprietary Information © 2016 Troubleshooting DriveScale Proprietary Information © 2016

Key locations to look for more information on DMS DriveScale Software Base Directory: /opt/drivescale /var/log/drivescale: DriveScale log file directory Most logs are named with the DriveScale process name in the filename /var/lib/drivescale: DMS Database base directory /var/run/drivescale: Running processes directory. Server inventory information in JSON format Compute Information (CPU, Memory, Manufacturer, Model, etc.) Networking Information (NIC’s, IP Addresses, Link information, etc.) DriveScale Management Server Software Version Information DMS Database (Zookeeper): Database location: /var/lib/drivescale-zookeeper/data/version-2 Tools Location: /opt/drivescale/tools/zookeeper zk_ls.py – Provides a path listing of all data objects stored in DMS DB zk_cat.py <PATH_TO_OBJECT> – Displays stored JSON data for a particular data object in DMS DB DriveScale Proprietary Information © 2016

Key locations to look for more information on Server Nodes DriveScale Software Base Directory: /opt/drivescale /var/log/drivescale: DriveScale log file directory Most logs are named with the DriveScale process name in the filename /var/lib/drivescale: Information for mapped and ingested drives Details on actively running configuration /var/run/drivescale: Running processes directory. Stores information about filesystems mounted on server nodes utilizing disks mapped by DriveScale Server inventory information in JSON format Compute Information (CPU, Memory, Manufacturer, Model, etc.) Networking Information (NIC’s, IP Addresses, Link information, etc.) DriveScale Server Software Version Information DriveScale Proprietary Information © 2016

Installation of DMS/DataNode/NameNode If any time the “yum install” fails, try “yum clean all” on the command line. If the drivescale service fails to start, check that “SELinux” is disabled. If the zookeeper fails to start while starting drivescale service, then check that “iptables” is turned off. Iptables must be disabled If the jumbo frames ping test fails, then make sure jumbo frames are enable on the switch and the data/name nodes. If the setup-mode fails on the DMS, then check for dsa install errors/messages in the /var/log/drivescale directory and ensure you are using the latest release build. To uninstall dm server or dms, run the following command: yum erase ds-server Yum erase ds-server-core DriveScale Proprietary Information © 2016

DriveScale Proprietary Information © 2016 DMS Dashboard Alerts When problems arise that may prevent your system from operating properly, Alerts may be generated and posted to the Status section of the DMS GUI in the Status section. Problems that can generate alerts, described in detail in the DriveScale User’s Guide 1.2 Alerts description, fall into a number of categories: A Server, DSA, Drive, or JBOD goes offline A Bandwidth domain is missing on the server A Data interface goes down on Server or DSA. An MTU on data interface is less than 9000 No Data interface redundancy exists iSCSI Target inconsistencies: No activity on drives Number of portals mismatch Target state is not running Orphaned bandwidth domain DriveScale Proprietary Information © 2016