Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Words and Phrases
| Search for | Example | Results |
|---|---|---|
| A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
|
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Using Boolean Operators
| Search for | Operator | Example |
|---|---|---|
|
Two or more words in the same topic |
|
|
| Either word in a topic |
|
|
| Topics that do not contain a specific word or phrase |
|
|
| Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
| A combination of search types | ( ) parentheses |
|
Component log levels
By default, most SA components are configured to log-only errors and warnings. Temporarily raising the log level on individual components can reveal more detailed messages and help you understand what is going wrong with a particular component.
Raising the log level may cause additional overhead and performance loss, so do not keep the logging level raised for an extended period of time. Raise it only when actively diagnosing a problem, then restore it when you are finished.
Before changing log levels, save the original log level for easier reversion when you are finished. Back up the original configuration file prior to editing it, then restore it when you are finished.
Log levels typically follow a common format for naming:
- Trace
- Debug
- Info
- Warn or Warning
- Error
- Fatal
- Finest
Log-level naming can vary from component to component, but it mostly follows the standardized naming practices.
Changing component log levels
This section discusses how to change logging levels for the various SA components that support it. Because multiple component instances may exist in a mesh, it may be necessary to perform these steps on multiple servers, such as SA slices or SA satellites.
- Boot server logs
- Build Manager logs
- Command Engine logs
- Data Access Engine logs
- Media server logs
- Model Repository logs
- Model Repository Multimaster component logs
- Software Repository logs
- Web Services Data Access Engine logs
- Global File System logs
The Boot Server does not generate its own logs. The Boot Server uses these services: TFTP with INETD, NFS server, and ISC DHCPD. All of these services log with syslog. Consult your vendor documentation for more information. See also the syslog.conf file that was used to configure the Boot Server to determine how the logging has been configured for this component.
These logs are in the following file:
/var/log/opsware/buildmgr/buildmgr.log
These logs are in the following files:
/var/log/opsware/waybot/waybot.err*
/var/log/opsware/waybot/waybot.log*
To change the log level for the Command Engine, edit the file /etc/opt/opsware/waybot/waybot.args and add the following line with the desired log level:
loglevel: DEBUG
You must restart the Command Engine for this change to take effect.
These logs are in the following files:
/var/log/opsware/spin/spin.err*
/var/log/opsware/spin/spin.log*
In a core with multiple Data Access Engines, each server running an engine has a set of these log files.
HPE Live Network (HPELN) logs
These logs are in the following location:
/var/log/opsware/hpln
These logs are in the following files:
/var/log/opsware/samba/log.smbd
/var/log/opsware/samba/log.nmbd
Solaris and Linux OS provisioning use of vendor-provided services such as NFSD. These services typically log through syslog. Consult your vendor documentation for more information on these log files.
The Model Repository is an Oracle database. The location logs the database is specific to your installation. For more information, see the "Monitoring Oracle Log Files" section in the SA 10.51
Model Repository Multimaster component logs
These logs are in the following files:
/var/log/opsware/vault/err*
/var/log/opsware/vault/vault.n.log
To configure the log file name, log file size, or logging level for the Model Repository Multimaster component, in the SA Client select the Administration tab, select System Configuration in the navigation panel, then select the Model Repository Multimaster Component. This displays the log file, log level, and log size system configuration parameters available for the model repository multimaster component. After setting the desired values, select the Revert button to discard your changes or the Save button to save your changes.
Alternatively, to change the log level for the Model Repository Multimaster component, edit the file /etc/opt/opsware/vault/logging.properties and change the following line.
.level=INFO
The default log level value is INFO.
You must restart the Model Repository Multimaster Component for this change to take effect. For instructions, see Starting individual SA Core components.
Agents logs
The Agents create the following log files on managed servers:
UNIX:
/var/log/opsware/agent/agent.log*
/var/log/opsware/agent/agent.err*
Windows:
%ProgramFiles%Common Files\opsware\log\agent\agent.log*
%ProgramFiles%Common Files\opsware\log\agent\agent.err*
SA Client logs
The SA Client does not generate its own logs. The SA Client uses the JBoss server, which writes to the following log files:
/var/log/opsware/occ/server.log*
/var/log/opsware/httpsProxy/*log*
To change the log level for the SA Client, edit the /opt/opsware/occ/occ/conf/log4j.xml file and change the org.jboss.logging.XLevel attribute value for the desired namespace. The default value is INFO.
You must restart the SA Client for this change to take effect.
These logs are in the following files:
/var/log/opsware/mm_wordbot/wordbot.err*
/var/log/opsware/mm_wordbot/wordbot.log*
To change the log level for the Software Repository, edit the file /etc/opt/opsware/mm_wordbot/mm_wordbot.args and change the following property to the desired log level:
logLevel: logging.Level.INFO
For example, to set logging to debug, set this value to the following:
logLevel: logging.Level.DEBUG
You must restart the Software Repository for this change to take effect. For instructions, see Starting individual SA Core components.
Web Services Data Access Engine logs
The Web Services Data Access Engine contains the following log files:
/var/log/opsware/twist/stdout.log*
/var/log/opsware/twist/twist.log
/var/log/opsware/twist/access.log
/var/log/opsware/twist/server.log*
/var/log/opsware/twist/boot.log
/var/log/opsware/twist/watchdog.log
The stdout.log file contains debug output and logging of every exception that the server generates. The file does not conform to a specific format. * indicates the files are 1og.1, log.2, log.3, and so forth. The number of files and the size of each file can both be configured using twist.conf. Additional logs are created when the specified maximum file size is reached. The stdout.log is the most recent, and stdout.log.1 through 5 are progressively older files. The file is also rotated on startup. This file also contains the output of any System.out.println(), System.err.println(), and e.printStackTrace() statements.
The twist.log file contains JBoss-specific error or informational messages and Weblogic specific messages. These files are rotated on startup.
The access.log file contains access information in common log format. These files are rotated when the file reaches 5MB in size.
The server.log file contains debug messages generated from the Web Services Data Access Engine. The debug messages are controlled by the log level set at the package or class level in the twist.conf file. * indicates the files are 1og.1, log.2, log.3, and so forth. The number of files and the size of each file can both be configured via twist.conf. The server.log.0 is always the current file, while server.log.9 is the oldest.
The boot.log file contains information on the initial stdout and stderr messages generated when the Web Services Data Access engine starts. In addition, the boot.log file contains the output from Kill –QUIT commands.
The watchdog.log file records the status of the Web Services Data Access Engine once every minute.
To change the log level for the Web Services Data Access Engine edit the file /etc/opt/opsware/twist/twist.conf. Change the log level from WARNING to FINEST or another value for the default log level or for another logger namespace you are interested in. There are multiple namespaces in this file. You can change the log level for all namespaces or for individual namespaces.
Gateway logs
These logs are in the following files:
/var/log/opsware/<gateway-name>/opswgw.log*
where <gateway-name> is the directory of a specific gateway component.
To change the log level for any of the gateway components, create or edit the file /etc/opt/opsware/<gateway-name>/opswgw.custom and set the log level in the following line:
opswgw.LogLevel=INFO
You must restart the gateway after changing the log level. For instructions, see Restarting or stopping a gateway process.
The OGFS log files are in the following files:
/var/log/opsware/hub/OPSWhub.log*
/var/log/opsware/ogfs/ogsh.err*
/var/log/opsware/adapter/adapter.err*
/var/log/opsware/agentcache/agentcache.log
/var/log/opsware/spoke/spoke-*.log
/var/log/opsware/spoke/stdout.log
To change the log level for the hub component of the OGFS:
- Log in to the global shell (OGSH) as an administrative user. For instructions, see the SA 10.51
- To determine the current log level, examine the file
/opsw/sys/hub/loglevel. For example, run the following OGSH command:more /opsw/sys/hub/loglevel - To change the log level, enter the following OGSH commands:
echo "MESSAGE ON" > /opsw/sys/hub/loglevelecho "LEVEL FINE" > /opsw/sys/hub/loglevel
The default values are “MESSAGE OFF” and “LEVEL INFO.”
To change the log level for the OGFS Spoke component, edit the file /etc/opt/opsware/spoke/spoke_custom.conf. Modify or add the following to this file and set the desired log level:
.level=INFO
You must restart the OGFS spoke component after changing the log level. For instructions, see Starting individual SA Core components.
HTTPS server proxy logs
These logs are found in:
/cust/apache/servers/https-Proxy/logs
The log file ssl_request_log can grow quite large and should be inspected if you are concerned about disk space availability.
APX proxy logs
The APX proxy log files are in /var/log/opsware/apxproxy/.
To change the log level for the APX proxy component, create or edit the file /etc/opt/opsware/apxproxy/apxProxyOverides.conf. Add or modify the following lines and set the desired log level:
.level = INFO
com.opsware.level=INFO
com.opsware.apxproxy.level=CONFIG
You must restart APX proxy after changing the log level. For instructions, seeStarting individual SA Core components.
The possible values for these properties are listed in the file /etc/opt/opsware/apxproxy/apxProxy.conf.
SSHD logs
The SSHD log files are in the location configured by syslog, typically /var/log.
To change the log level for the SSHD component, edit the file /etc/opt/opsware/sshd/sshd_conf. Modify the following and set the desired log level:
LogLevel INFO
You must restart SSHD after changing the log level. For instructions, see Starting individual SA Core components.
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to hpe_sa_docs@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: