Administer > Log files

Log files

SA components record events in log files. One of the most valuable tools for troubleshooting SA problems is these component log files. Understanding SA components and how they log information can help you troubleshoot and resolve problems quickly. When you file a support request, HPE Support may request you to send one or more log files or session data files.

This section describes log files, where they are located, and how you can use them for troubleshooting. It also describes how to create a session data file.

For a list of SA internal component names, see SA Core Component internal names.

Where log files are stored

Most SA log files are stored in /var/log/opsware. However, some components either log to their own directories (such as Oracle) or use syslog (such as NFS and DHCPD). The following table lists SA components and their log directories. This information can help you determine which components or log files may be helpful in troubleshooting your particular problem.

SA Log Files

Product Area

SA Component

Log File Directory

Database

Model Repository (truth or Oracle database)

Various directories under /u01/app/oracle, or as configured

Data Access,

API

Data Access Engine (spin)

/var/log/opsware/spin

Web Services Data Access Engine (twist)

/var/log/opsware/twist

 

Object Storage

Software Repository (word / wordcache)

/var/log/opsware/mm_wordbot

Tsunami

/var/log/opsware/tsunami

Memcached

/var/log/opsware/memcached

Job & Session Management

Command Engine (way)

/var/log/opsware/waybot

 

Global Shell,

APX

Global File System, OGFS (hub)

/var/log/opsware/hub

Global File System, OGFS (spoke)

/var/log/opsware/spoke

APX Proxy

/var/log/opsware/apxproxy

Other

/var/log/opsware/adapter

/var/log/opsware/ogfs

/var/log/opsware/agentproxy

/var/log (opswsshd)

 

Mesh Communication

Agent Gateway

/var/log/opsware/opswgw-agwsN-FACILITY

Core Gateway

/var/log/opsware/opswgw-cgwsN-FACILITY

Management Gateway

/var/log/opsware/opswgw-mgwsN-FACILITY

Front-End

SA Client

/var/log/opsware/occ

HTTPS Proxy

/var/log/opsware/httpsProxy

Mesh Replication

Model Repository Multimaster Component
(vault/OMB)

/var/log/opsware/vault

 

OS Provisioning

   

DHCPD

/var/log, or as configured by syslog

Samba

/var/log/samba

NFS

/var/log, or as configured by syslog

Agent Deployment

Agent Cache

/var/log/opsware/agentcache

Startup

SA Init Scripts

/var/log/opsware/startup

SA Agent

SA Agent

/var/log/opsware/agent

Product areas and related component log files

Understanding the functional purpose of each component listed in the following table can help you determine which components and logs to start with when troubleshooting. In many cases, the problem context including error messages or tracebacks can give you an idea of which logs to examine.

For example, when troubleshooting agent communication problems, a key step is to realize that one or more gateways are involved in all mesh communications and that if a gateway is down or not functioning properly, mesh communication will be impacted.

The following table lists SA product areas and log files to check when troubleshooting.

Product Areas and Related Component Log Files

Product Area

Data- base

Logs

Data Access Logs

Object Storage Logs

Job Mgmt Logs

Global Shell Logs

Mesh Comm Logs

Agent Logs

Agent Deployment

X

X

X

 

X

X

X

Audit and Compliance

X

X

X

X

X

X

X

Remediation for Software Management

X

X

X

X

 

X

X

Patching

X

X

X

X

 

X

X

Run Scripts

X

X

 

X

X

X

X

Application Configuration

X

X

 

X

 

X

X

OS Provisioning

X

X

 

X

X

X

X

Global Shell, APX

X

X

 

 

X

X

X

Ad hoc Device Management

X

X

 

 

X

X

X

Viewing log files

To view a log file in a terminal window, log into the server running the component and use a command-line utility such as more, less, grep, or vi. See the following sections for locations of specific SA component log files.

The log file for a component resides on the server where the component is installed.

Log file sizes

The default for the maximum log file size is 10 MB. When the specified maximum file size is reached, additional log files are created.

If you raise the log level for any components, the log files typically will grow significantly faster than the default log level. It is very important that you only raise the log level for a short period of time, long enough to gather log information about the problem you are troubleshooting, and then set the debug level back to the default value.

Send Help Center feedback