I have noticed in 2.5 (and the earlier 2.0.2.x versions), that scheduled monthly scans ("the first Mon of each month") don't start - no log even of an attempt to run. They would run ones after one sets them up, but do not repeat the following month. Is there a known issue, or how can I troubleshoot the scheduled tasks?
On 12/4/2014 9:16 AM, ablovatskia wrote: > > I have noticed in 2.5 (and the earlier 2.0.2.x versions), that scheduled > monthly scans ("the first Mon of each month") don't start - no log even > of an attempt to run. They would run ones after one sets them up, but do > not repeat the following month. Is there a known issue, or how can I > troubleshoot the scheduled tasks? > > ablovatskia,
Do scans scheduled for other time intervals run automatically?
On 12/4/2014 9:16 AM, ablovatskia wrote: > > I have noticed in 2.5 (and the earlier 2.0.2.x versions), that scheduled > monthly scans ("the first Mon of each month") don't start - no log even > of an attempt to run. They would run ones after one sets them up, but do > not repeat the following month. Is there a known issue, or how can I > troubleshoot the scheduled tasks? > > ablovatskia,
Do scans scheduled for other time intervals run automatically?
Seems so, the daily scans never have a problem starting. I now moved the monthly scans from "every first" to "every second" to see if they start next week.
Re-scheduling to run on "every second" Mon, Tues, Wed had mixed results. Yesterday the scans started and completed successfully, but today there was a problem with the scan and it was never re-tried, just hanging in the "Waiting for Retry 1" state:
Log:
1156 \\SERVER\MEDIA Topaz_MEDIA_FS File System Data 12/10/2014 1:00:00 AM Waiting for Retry 1 12/10/2014 3:08:00 AM (-3) A C or O.S. exception occurred and was converted to an error.
Error 12/10/2014 1:08:58 AM (-3) A C or O.S. exception occurred and was converted to an error. Scan The scheduled data scan for storage path \\SERVER\MEDIA (Scan ID 1156) was unable to complete. The following error occurred: (-3) A C or O.S. exception occurred and was converted to an error. There are 3 retry attempts remaining. The next attempt will be made in 7142 seconds.
On 12/10/2014 9:56 AM, ablovatskia wrote: > > Re-scheduling to run on "every second" Mon, Tues, Wed had mixed results. > Yesterday the scans started and completed successfully, but today there > was a problem with the scan and it was never re-tried, just hanging in > the "Waiting for Retry 1" state: > > Log: > > 1156 \\SERVER\MEDIA Topaz_MEDIA_FS File System Data 12/10/2014 1:00:00 > AM Waiting for Retry 1 12/10/2014 3:08:00 AM (-3) A C or O.S. > exception occurred and was converted to an error. > > Error > 12/10/2014 1:08:58 AM (-3) A C or O.S. exception occurred and was > converted to an error. Scan The scheduled data scan for storage path > \\SERVER\MEDIA (Scan ID 1156) was unable to complete. The following > error occurred: (-3) A C or O.S. exception occurred and was converted > to an error. There are 3 retry attempts remaining. The next attempt will > be made in 7142 seconds. > > ablovatskia,
Was this from the Engine or Agent log? And if this is from the former, could you post (or email, if you prefer) the error from the Agent log? Thanks.
I figured out what might have caused the scan retry to fail: at 12/10/2014 2:42:23 AM the NFR server rebooted after installing Windows updates, interrupting the scheduled retry at 3:08:00 AM.
On 1/15/2015 2:16 PM, ablovatskia wrote: > > We are still having problems with monthly scans. > > See my earlier post: "... the daily scans never have a problem starting. > I now moved the monthly scans from "every first" to "every second" to > see if they start next week." > > The pattern seems to be that scheduled monthly scans on a first Monday, > Tuesday, so forth, run once after being scheduled on that Monday, > Tuesday, ..., but do _not_ repeat a month later. If I reschedule the > scans to the second Monday, Tuesday, ... , they will again run once, and > not the second time a month later, and so forth. > > Any suggestions re: fixing this issue? > > ablovatskia,
Could you email your Engine logs to filereporter@novell.com? We may need you to open a SR to look at this. Remember that if this is a bug, that SR will be credited back to you.
On 1/15/2015 2:16 PM, ablovatskia wrote: > > We are still having problems with monthly scans. > > See my earlier post: "... the daily scans never have a problem starting. > I now moved the monthly scans from "every first" to "every second" to > see if they start next week." > > The pattern seems to be that scheduled monthly scans on a first Monday, > Tuesday, so forth, run once after being scheduled on that Monday, > Tuesday, ..., but do _not_ repeat a month later. If I reschedule the > scans to the second Monday, Tuesday, ... , they will again run once, and > not the second time a month later, and so forth. > > Any suggestions re: fixing this issue? > > ablovatskia,