5.8
Table Of Contents
- Software Content Repository Tool 6.1 Guide
- Contents
- About This Book
- Introduction to the Software Content Repository Tool
- Preparing for SCR Tool Installation
- Installing the Prerequisite Software for the SCR Tool
- Configuring the Red Hat Host Machine
- Managing Patch Content with the SCR Tool
- Troubleshooting the SCR Tool
- Out of Memory Error
- Content Download Network Connection Error
- Cannot Connect to Red Hat Account
- Session Login to Red Hat Fails
- Download from Red Hat Fails
- HP-UX Service Authentication Fails
- Download from HP Fails
- Proxy Server Configuration Fails
- Mismatch in Number of Patches
- OS Vendor Does Not Accept Credentials
- OS Vendor Errors
- Patch Download Errors
- Obsolete Patches Cause the Download to Fail
- HTTP Errors Are Not Marked as SEVERE
- Connection Refused Errors
- Null Pointer Exception Errors
- Index
Set Logging Levels and Output File Names
The SCR Tool provides flexible logging settings and properties to customize your logging levels.
The logging levels and output file names reside in the individual <platform>-rt.properties file for
each platform type.
Platform Properties File Name
AIX
scr_root/conf/aix-rt.properties
CentOS
scr_root/conf/centos-rt.properties
HP-UX
scr_root/conf/hp-rt.properties
Mac OS X
scr_root/conf/osx-rt.properties
Oracle Enterprise Linux (OEL)
scr_root/conf/oracle-rt.properties
Red Hat
scr_root/conf/redhat-rt.properties
Solaris
scr_root/conf/solaris-rt.properties
SUSE
scr_root/conf/suse-rt.properties
Table 4–3. Property Files with Logging Levels and Output File Names
You can set the custom logging levels and output file names in these properties files for each run of the
SCRTool. You can use specific logging parameters for each specific patch distribution.
Procedure
1. Locate and open an individual <platform>-rt.properties file.
2. Set the following properties to the required level of logging.
java.util.logging.FileHandler.level
java.util.logging.ConsoleHandler.level
com.lumension.level
By default, all scripts log data to the same file name pattern at the INFO logging level. The logging
values include several levels.
n SEVERE
n WARNING (valid, but not used)
n INFO (recommended for production)
n CONFIG (valid, but not used)
n FINE (debug)
n FINER (debug)
n FINEST (debug)
3. To customize log file names, change the output java.util.logging.FileHandler.pattern=path
parameter.
Software Content Repository Tool 6.1 Guide
26
VMware, Inc.