Jump to content

Scheduled scan early after time change


j-gray
 Share

Recommended Posts

Recently changed time due to Daylight Savings Time. Schedule scans are now starting one hour earlier than intended.

The CRON expression is as follows:

Wednesdays at 4:30pm
CRON: 0 30 16 ? * WED; Local time; Invoke ASAP If Event Missed: Yes; Random Delay Interval: 0 second(s)
 
What adjustment is needed to have the systems scan at the correct specified time?
Link to comment
Share on other sites

44 minutes ago, janoo said:

Hi, are all your machines located (and set) in the same timezone?

Thanks for the reply. Yes, all workstations and server are in the same time zone. Time and time zone are correct on all devices.

Link to comment
Share on other sites

  • ESET Staff

When AGENT is starting, there should be something like this:

Local time is 2017-Nov-10 09:17:54

in trace.log (even with default trace log severity). Could you verify that time is correct? Also is there any change AGENT has not been restarted since time change? Not sure we will recognize change of local time (UTC changes are registered).

What version if AGENT is used, 6.5?

Edited by MartinK
Link to comment
Share on other sites

On 11/10/2017 at 8:52 AM, MartinK said:

When AGENT is starting, there should be something like this:


Local time is 2017-Nov-10 09:17:54

in trace.log (even with default trace log severity). Could you verify that time is correct? Also is there any change AGENT has not been restarted since time change? Not sure we will recognize change of local time (UTC changes are registered).

What version if AGENT is used, 6.5?

Appears to be correct, though I have no idea if this was logged at the actual time, or a time derived by another means:

2017-11-09 17:02:35 Information: Kernel [Thread 0xa6f4a1c0]: Local time is 2017-11-09 10:02:35

It appears that this event is logged randomly once every 7 days. It's quite possible some systems did not reboot immediately after the time change. 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...