HP Xw460c HP Insight Control Environment User Guide - Page 149

HTTP 300 errors received during patch acquisition

Get HP Xw460c - ProLiant - Blade Workstation PDF manuals and user guides View all HP Xw460c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 149 highlights

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 VPM 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. This message occurs because the Microsoft information pertaining to the patch location is incorrect and the patch cannot be downloaded. HP is working to correct the metadata at the HP/Radia website for these older patches, however this is ongoing maintenance. These corrections will automatically be downloaded each time a patch acquisition is run. No updates are needed to Vulnerability and Patch Management. Patches appear in a scan report but are not successfully deployed This can occur in the following situations: • A vulnerability scan has identified vulnerabilities, patches were selected for deployment based on the scan, and one or more of the selected patches were not located in the patch repository. Generally, some of the patches will install successfully, while others do not install for an extended time. Patches might not be available in the patch repository because all necessary operating systems were not selected for patch acquisition, or only some patches have been acquired. • The VPM Patch Agent has not been successfully installed on the system being patched. • A patch deployment is attempted on a system for which the patch is not applicable. Vulnerability and Patch Management applies patches to target systems based on the operating system characteristics and patch vulnerabilities. For example, a patch cannot be deployed when a Red Hat patch is selected for deployment on a Windows target system. Check for missing patches Be sure that a patch acquisition has been selected for all operating systems in the server environment. Different Microsoft patches can exist for each operating system associated with an advisory. To validate if a patch has been acquired, click the advisory link to the operating system vendor. The patches for each operating system are listed. Check the \Radia\IntegrationServer\Data\Patch\Microsoft\ directory to see if each patch has been acquired. Check the file \Radia\IntegrationServer\Logs\patch-acquire.log for a history of the last patch acquisition, including any errors. Patches downloaded through HTTP might have been acquired successfully, but those requiring FTP are failing. If this occurs, validate the proxy and firewall settings to be sure they are configured properly to enable FTP traffic. Validating VPM Patch Agent installation Check the VPM events to see if a successful Installed VPM Patch Agent event exists for the system to be patched. If no event is present or if a Failed VPM Patch Agent Install event exists, select Deploy→Vulnerability and Patch Manager→VPM Patch Agent to deploy the agent. After the VPM Patch Agent installation and patch acquisition have been verified, reinitiate the patch installation by selecting Deploy→Vulnerability and Patch Manager→Validate Installed Patches. Patch installation status reports are not current or do not match information that appears in scan reports Information that appears in patch reports is obtained during the most recent patch deployment task. If this information is not current, update the patch installation status by validating installed patches. For information, see the "Validating installed patches" section in this guide. Vulnerability and Patch Management Pack troubleshooting 149

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
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 VPM 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
ht
tp://w
w
w
.mic
r
o
s
o
f
t
.com/tec
hn
et/sec
ur
it
y/
bull
etin/MS0
2
-0
5
0.msp
x
.
This message occurs because the Microsoft information pertaining to the patch location is incorrect and the
patch cannot be downloaded. HP is working to correct the metadata at the HP/Radia website for these older
patches, however this is ongoing maintenance. These corrections will automatically be downloaded each
time a patch acquisition is run. No updates are needed to Vulnerability and Patch Management.
Patches appear in a scan report but are not successfully deployed
This can occur in the following situations:
•
A vulnerability scan has identified vulnerabilities, patches were selected for deployment based on the
scan, and one or more of the selected patches were not located in the patch repository. Generally,
some of the patches will install successfully, while others do not install for an extended time. Patches
might not be available in the patch repository because all necessary operating systems were not selected
for patch acquisition, or only some patches have been acquired.
•
The VPM Patch Agent has not been successfully installed on the system being patched.
•
A patch deployment is attempted on a system for which the patch is not applicable. Vulnerability and
Patch Management applies patches to target systems based on the operating system characteristics
and patch vulnerabilities. For example, a patch cannot be deployed when a Red Hat patch is selected
for deployment on a Windows target system.
Check for missing patches
Be sure that a patch acquisition has been selected for all operating systems in the server environment. Different
Microsoft patches can exist for each operating system associated with an advisory. To validate if a patch
has been acquired, click the advisory link to the operating system vendor. The patches for each operating
system are listed. Check the
<VPM_installation_folder>\Radia\IntegrationServer\Data\Patch\Microsoft\<bulletin
number>
directory to see if each patch has been acquired.
Check the file
<VPM_installation_folder>\Radia\IntegrationServer\Logs\patch-acquire.log
for a
history of the last patch acquisition, including any errors. Patches downloaded through HTTP might have
been acquired successfully, but those requiring FTP are failing. If this occurs, validate the proxy and firewall
settings to be sure they are configured properly to enable FTP traffic.
Validating VPM Patch Agent installation
Check the VPM events to see if a successful Installed VPM Patch Agent event exists for the system to be
patched. If no event is present or if a Failed VPM Patch Agent Install event exists, select
Deploy
→
Vulnerability
and Patch Manager
→
VPM Patch Agent
to deploy the agent.
After the VPM Patch Agent installation and patch acquisition have been verified, reinitiate the patch installation
by selecting
Deploy
→
Vulnerability and Patch Manager
→
Validate Installed Patches
.
Patch installation status reports are not current or do not match information that appears in scan
reports
Information that appears in patch reports is obtained during the most recent patch deployment task. If this
information is not current, update the patch installation status by validating installed patches. For information,
see the “Validating installed patches” section in this guide.
Vulnerability and Patch Management Pack troubleshooting
149