None of our devices are able to run security and patch manager scans.
When running a manualy scan locally with the UI, it times out awaiting connection and we get these errors:
Verifying Device ID with core SERVER Failed: Core returned error
Updating settings: Failed: No response from core
Checking for updates on core SERVER Failed: No response from core
In the IIS log, there are loads of 503 errors:
2008-06-25 08:38:51 W3SVC1 10.100.4.213 POST /WSVulnerabilityCore/VulCore.asmx - 80 - 10.211.1.150 Microsoft-ATL-Native/8.00 503 0 0
2008-06-25 08:38:51 W3SVC1 10.100.4.213 POST /WSVulnerabilityCore/VulCore.asmx - 80 - 10.32.112.94 Microsoft-ATL-Native/8.00 503 0 0
2008-06-25 08:38:52 W3SVC1 10.100.4.213 POST /WSVulnerabilityCore/VulCore.asmx - 80 - 10.193.7.78 Microsoft-ATL-Native/8.00 503 0 0
2008-06-25 08:38:52 W3SVC1 10.100.4.213 POST /WSVulnerabilityCore/VulCore.asmx - 80 - 10.211.6.71 Microsoft-ATL-Native/8.00 503 0 0
2008-06-25 08:38:52 W3SVC1 10.100.4.213 POST /WSVulnerabilityCore/VulCore.asmx - 80 - 192.168.164.183 Microsoft-ATL-Native/8.00 503 0 64
2008-06-25 08:38:52 W3SVC1 10.100.4.213 POST /WSVulnerabilityCore/VulCore.asmx - 80 - 10.204.1.101 Microsoft-ATL-Native/8.00 503 0 0
2008-06-25 08:38:52 W3SVC1 10.100.4.213 POST /WSVulnerabilityCore/VulCore.asmx - 80 - 192.168.197.153 Microsoft-ATL-Native/8.00 503 0 0
2008-06-25 08:38:52 W3SVC1 10.100.4.213 POST /WSVulnerabilityCore/VulCore.asmx - 80 - 192.168.57.134 Microsoft-ATL-Native/8.00 503 0 0
2008-06-25 08:38:52 W3SVC1 10.100.4.213 POST /WSVulnerabilityCore/VulCore.asmx - 80 - 191.203.4.20 Microsoft-ATL-Native/8.00 503 0 0
2008-06-25 08:38:52 W3SVC1 10.100.4.213 POST /WSVulnerabilityCore/VulCore.asmx - 80 - 191.203.4.60 Microsoft-ATL-Native/8.00 503 0 0
2008-06-25 08:38:52 W3SVC1 10.100.4.213 POST /WSVulnerabilityCore/VulCore.asmx - 80 - 10.211.6.71 Microsoft-ATL-Native/8.00 503 0 0
2008-06-25 08:38:52 W3SVC1 10.100.4.213 POST /WSVulnerabilityCore/VulCore.asmx - 80 - 10.100.43.118 Microsoft-ATL-Native/8.00 503 0 0
2008-06-25 08:38:52 W3SVC1 10.100.4.213 POST /WSVulnerabilityCore/VulCore.asmx - 80 - 10.100.42.99 Microsoft-ATL-Native/8.00 503 0 0
2008-06-25 08:38:52 W3SVC1 10.100.4.213 POST /WSVulnerabilityCore/VulCore.asmx - 80 - 191.200.201.66 Microsoft-ATL-Native/8.00 503 0 0
2008-06-25 08:38:52 W3SVC1 10.100.4.213 POST /WSVulnerabilityCore/VulCore.asmx - 80 - 10.100.102.63 Microsoft-ATL-Native/8.00 503 0 0
2008-06-25 08:38:52 W3SVC1 10.100.4.213 POST /WSVulnerabilityCore/VulCore.asmx - 80 - 10.100.22.24 Microsoft-ATL-Native/8.00 503 0 0
2008-06-25 08:38:52 W3SVC1 10.100.4.213 POST /WSVulnerabilityCore/VulCore.asmx - 80 - 10.100.33.4 Microsoft-ATL-Native/8.00 503 0 0
2008-06-25 08:38:52 W3SVC1 10.100.4.213 POST /WSVulnerabilityCore/VulCore.asmx - 80 - 10.100.76.12 Microsoft-ATL-Native/8.00 503 0 0
2008-06-25 08:38:52 W3SVC1 10.100.4.213 POST /WSVulnerabilityCore/VulCore.asmx - 80 - 10.100.59.76 Microsoft-ATL-Native/8.00 503 0 0
2008-06-25 08:38:52 W3SVC1 10.100.4.213 POST /WSVulnerabilityCore/VulCore.asmx - 80 - 10.100.40.46 Microsoft-ATL-Native/8.00 503 0 0
2008-06-25 08:38:52 W3SVC1 10.100.4.213 POST /WSVulnerabilityCore/VulCore.asmx - 80 - 192.168.63.51 Microsoft-ATL-Native/8.00 503 0 64
2008-06-25 08:38:52 W3SVC1 10.100.4.213 POST /WSVulnerabilityCore/VulCore.asmx - 80 - 192.168.93.73 Microsoft-ATL-Native/8.00 503 0 0
When i run http://localhost/wsvulnerabilitycore/vulcore.asmx on the core server, the page i get simply says:
Server is too busy
I have verified
the permissions to *WSVulnerabilityCore
LDLogon\VulnerabilityData* and LDLogon\vulscanresults
in IIS (basically they are set as per the attached document that another user
posted).
We are running 8.8
with the hotfix and patch installed. The core and db servers are brand
new (introduced 2nd June). They are both 4x quad CPU 16gb machines and the load
on them (12000 nodes) is barely noticeable. I beleive LDSS has been working since it was setup by ourselves/Pangea but has since stopped working
This has completely stumped us - any ideas?