AnsweredAssumed Answered

Scheduled Scan Duration Appears to be failing

Question asked by urbanindy on Mar 3, 2014
Latest reply on Mar 10, 2014 by Kelly Hammons

We've had several instances where our scheduled scans were not behaving as expected when pausing and resuming.


Today we had a scan that was supposed to have a duration of 2 hours run with the following times

"Start: 03/03/2014 at 11:07:44 (GMT-0500)  | Ended: 03/03/2014 at 13:45:04 (GMT-0500)  | Scan Paused (02:31:52)"

It was set as follows:



The scan used three appliances serial 23,###, 23,### and a 10,### which were all associated with the one asset group included in the scan.

We're testing to see if taking the older appliance out of the scan will help.


Has anyone else seen this type of behavior?


We're also finding, and this is probably by design, that if we manually pause these they will not resume automatically.  So once they go over (and they can't go over because we have a pre-approved change window), we then have to baby sit them for the rest of the week.