HP Insight Vulnerability and Patch Manager Software - Manual (Page 22)

VPM Patch Agent installation fails
The VPM Patch Agent is automatically deployed when systems are licensed to allow patches to be applied
to the systems. If a server type is identified as Unknown or Unmanaged with no identified operating system
in the Systems Insight Manager console, Vulnerability and Patch Manager automatically attempts to deploy
the VPM Patch Agent for Windows systems. The VPM Patch Agent deployment fails on Linux systems, and
event details display an error.
Be sure that the Red Hat library, compat libstdc++, is installed on Red Hat target systems.
The VPM Patch Agent installation can also fail because the WBEM credentials are not configured properly
to allow Vulnerability and Patch Manager to access target systems. For information about configuring WBEM
credentials, see the
HP Insight Software Installation and Configuration Guide.
A patch acquisition was started, but no patches are visible
A patch acquisition can take quite a bit of time the first time it is run. It is not unusual for the acquisition to
take more than four hours, depending on how many operating systems are selected for download and the
speed of the Internet connection.
Progress of the acquisition can be monitored at:
<VPM_installation_folder>\Radia\IntegrationServer\logs\patch-acquire.log .
If the log file indicates that no patches are being acquired and there is a proxy server in the environment,
be sure you have properly configured Vulnerability and Patch Manager to access the proxy server by selecting
Options
→Vulnerability and Patch Management→Settings. In addition, the proxy server must be
configured to allow both HTTP and FTP traffic.
If the patch-acquire.log is not being updated, the acquisition process might be hung. Search the
patch-acquire.log for the start of the last logged process id. Stop the nvdkit.exe with that process id running
on your Vulnerability and Patch Manager server. This action terminates the current acquisition and allows
the next acquisition to run.
HTTP 300 errors received during patch acquisition
Patch acquisition can generate events containing HTTP 300 errors for some older Microsoft patches, such
as:
Error downloading patch data for Bulletin MS02-050 at URL http://www.microsoft.com/technet/security/
bulletin/MS02-050.mspx .
22 Troubleshooting