Problems with domain scan
Hi,
For the last couple of months we haven't done any scans & turned the automation off. This was due to some stability issues we had before Christmas. As these issues have been resolved now, we decided to implement the asset scanning again.
So after eventually getting through our change request procedures etc, I began today.
All was going well until approx 41% through the scan SDP through a bit of a hissy fit & kicked everyone out of SDP and the scan just froze.
Looked on the server, the SDP process java.exe had used 2GB memory before, it terminated & restarted itself.
Ran the scan again, in case this was a one off glitch. And pretty much the same thing happened again, the scan froze & was unusable after a couple of hours of scanning - it was scanning a different asset & failed this time on only 17%
We've got approx 6500 assets for the scan to deal with. Is there a size limit on the amount of assets that can be scanned through domain scan at any one time?
In addition, since these failed scans when I go to the domain scan module, on our domain the icon has changed to "scan in progress".
However, there is no real increased use in processor it's returned to it's normal range of 0 - 3%. And I'm a bit reluctant to start another scan, or anything really without knowing if the asset db is going to be screwed up or anything.
Thanks,
Carl
For the last couple of months we haven't done any scans & turned the automation off. This was due to some stability issues we had before Christmas. As these issues have been resolved now, we decided to implement the asset scanning again.
So after eventually getting through our change request procedures etc, I began today.
All was going well until approx 41% through the scan SDP through a bit of a hissy fit & kicked everyone out of SDP and the scan just froze.
Looked on the server, the SDP process java.exe had used 2GB memory before, it terminated & restarted itself.
Ran the scan again, in case this was a one off glitch. And pretty much the same thing happened again, the scan froze & was unusable after a couple of hours of scanning - it was scanning a different asset & failed this time on only 17%
We've got approx 6500 assets for the scan to deal with. Is there a size limit on the amount of assets that can be scanned through domain scan at any one time?
In addition, since these failed scans when I go to the domain scan module, on our domain the icon has changed to "scan in progress".
However, there is no real increased use in processor it's returned to it's normal range of 0 - 3%. And I'm a bit reluctant to start another scan, or anything really without knowing if the asset db is going to be screwed up or anything.
Thanks,
Carl