A.05.80 HP Insight Remote Support Advanced Managed Systems Configuration Guide (June 2013)

Table Of Contents
Managed Systems Configuration Guide
Chapter 14: Tru64 UNIX Server Configuration
Archiving and Cleaning the Error Log
System Event Analyzer (SEA) is a remote system event monitoring tool and is a WEBES component
running on the CMS. If you want SEA to automatically analyze a system's native error log, you must
install on a supported HP hardware platform or a machine that includes supported HP I/O devices. See the
WEBES Release Notes for the list of supported products.
After installation, WEBES will begin analyzing all events currently stored in the error log, gathering the
events using ELMC, which can result in high CPU usage over an extended period. To control this
operation, you are encouraged to archive and clean the error log as described in this section before
installing ELMC. This reduces the size of the log and the time required for the initial scan.
If WEBES is installed and running when you decide to clean the log, stop the Director process before
beginning this procedure (see the SEA User Guide for information on stopping the Director). Once you
have archived and cleared the error log, restart the Director using the procedure in the SEA User Guide,
which is installed on the CMS with WEBES.
Tru64 UNIX Version 4.0F
1. Stop the binlogd process: # /sbin/init.d/binlog stop
2. If desired, move the original error log to any appropriate name, for example:
# mv /var/adm/binary.errlog /var/adm/binary.errlog.2002_06_11
Saved logs can be analyzed at a later time.
3. If you skipped step 2, remove the original error log: # rm /var/adm/binary.errlog
4. Restart the system. During restart, the system creates a new binary.errlog file containing a new
configuration event. The system also restarts the binlogd process.
Tru64 UNIX Version 4.0G
1. Stop the binlogd process: # /sbin/init.d/binlog stop
2. If desired, move the original error log to any appropriate name, for example:
# mv /var/adm/binary.errlog /var/adm/binary.errlog.2002_06_11
Saved logs can be analyzed at a later time.
3. If you skipped step 2, remove the original error log: # rm /var/adm/binary.errlog
4. Restart the binlogd process: # /sbin/init.d/binlog start
Tru64 UNIX Version 5.A or Higher
A new feature can send a signal to binlogd to save the current log and create a new one without stopping
the process. Follow the steps in "Verify the binary.errlog CDSL" on the next page and "Clear the Log with
binlogd Running" on page 100.
HP Insight Remote Support Advanced (A.05.80)Page 98 of 204