Computer Drive User Manual

A server’s log policy can be modified to control the volume of messages to the chosen logging
destinations. Typically, during normal operations, the level of logging may be decreased to only Alarm,
Event, and Security to reduce overhead. However, while tracking an HPSS problem, it may be desirable
to include more log message types such as Debug, Request and Trace to obtain more information. As
stated previously, it is recommended that Trace not be selected except for short periods as an aid to
isolating a problem.
After a server’s log policy has been modified, the Log Client running on the same node as the server
must be reinitialized for it to reread the new log policy. If the server is a Mover, then that Mover itself
must be reinitialized in order for the new log policy to take effect.
9.2.4. Deleting a Log Policy
To delete a log policy, select the log policy from the Logging Policies window (Section 9.2.2: Logging
Policies Window on page 296) and click the Delete button. A log policy can also be deleted by opening
the Logging Policy window (Section 9.2.2.1: Logging Policy Configuration Window on page 297) for
the appropriate log policy and clicking the Delete button.
A third way to delete a log policy is to open the Log Policy tab of the Server Configuration window for
that server and push the Use Default Log Policy button. This removes the unique log policy configured
for that server and makes it revert to using the default policy.
Before deleting a log policy, ensure that no servers are configured to use it. Otherwise, the log policy
deletion could result in loss of important log messages. After deleting a log policy, the Log Clients
supporting any servers that were using the policy must be reinitialized or restarted. If the log policy was
used by a Mover, then that Mover itself must be reinitialized or restarted in order for the Mover to stop
using the deleted policy.
9.3. Managing the Central Log
This section describes configuring and viewing the central log file. Note that the central log is located on
the node with the Log Daemon and is in binary format.
9.3.1. Configuring Central Log Options
The central HPSS log is managed by the Log Daemon and consists of two log files, logfile01 and
logfile02. These log files can be controlled by changing the Archive Logfiles and the Switch Logfiles
flags on the Log Daemon Specific Configuration window (Section 5.1.1: Log Daemon Specific
Configuration on page 101). The Archive Logfiles flag dictates whether the log files will be
automatically archived when they are filled. The Switch Logfiles flag dictates whether a switch to the
second log file should be done if the archive of the second log file has not yet completed. The
administrator needs to consider whether archiving of the log files is needed and then set these flags
appropriately.
In addition to modifying the logging configuration to control logging, the HPSSLOG_SHMKEY,
HPSSLOG, and HPSSLOGGER environment variables described in the HPSS Installation
Guide, Section 5.6: Define HPSS Environment Variables can also be used.
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 299