5.7
Table Of Contents
- Software Content Repository Tool 5.0 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
Problem
When you attempt to download patch content, an error occurs on the OS vendor download Web site. For
example:
Mar 24, 2011 3:33:19 PM sun.net.www.protocol.http.HttpURLConnection
getInputStream
FINE: HYPERLINK "mailto:sun.net.www.MessageHeader@1a4e8a118"
sun.net.www.MessageHeader@1a4e8a118 pairs: {null: HTTP/1.1 401 Authorization
Required}{Date: Thu, 24 Mar 2011 21:35:03 GMT}{Server: Apache}{X-RHN-Fault-Code:
-33}
Cause
Errors might occur in the following cases.
n
You attempted to use the #channels parameter in a properties file but you are not entitled to use the
command.
n
At the time of download, an excessive number of concurrent logins are accessing the OS vendor site.
Solution
n
If multiple users in your environment are manually connected to the download Web sites, wait until
they are finished before you connect again.
n
Limit user connections to the OS vendor download Web site during patch replication, and restart the
patch replication process.
Patch Download Errors
When you run the startup script, the source of the problem does not appear when an error occurs.
Problem
A failure in the patch download process might occur because of various problems, but the source of the
problem is not obvious. When the patch content downloads, a severe error recorded in the logs might not
indicate an actual error. For example, if the CDN does not have the requested package, the non-entitled
content might display a SEVERE error.
Cause
The patch download process failed, and no message appeared to indicate the cause of the problem.
Solution
1. On the SCR Tool host machine, access the scr_root/logs directory.
2. View the platform specific log file.
3. Check the log file to confirm whether any SEVERE entries are logged.
Various types of errors can occur. For example:
Feb 23, 2011 4:42:45 PM com.lumension.scr.pojo.SCPackage download
SEVERE: Payload file URL to download
http://novell.cdn.lumension.com/novell/aix/ppc/IY76827.tar.gz
Software Content Repository Tool 5.0 Guide
38
VMware, Inc.