Jump to content

Scans duration.


NumberFive
 Share

Recommended Posts

Good morning.

We have all clients in X organization set to start a full scan every day at 21:00 (almost the at the same time for all)

The client is complaining that the scans are starting in the morning instead.

After checking the detailed info on the scans for the previous days, the scan times are widely inconsistents.
The scans all show that they started at the correct time (or so the console claims)
The machines in the organization are almost all identical.
Some scans are finishing in half an hour, others are taking 12 hours.

Scan settings have the "invoke ASAP if failed" flag checked out.
The only target to scan is C:\.

SCANS.png

Edited by NumberFive
Link to comment
Share on other sites

  • ESET Staff

Could you please select one specific client with this problem and open "execution history"? It is possible that scan is actually started at correct time, but maybe it takes so long? Is it possible that scan is started in different time due to timezone differences ? Are you actually using local or UTC time when defining task trigger.

Link to comment
Share on other sites

Hello MartinK, ty for your reply.

I can't check the execution history today, I'll check on Monday.
Regarding the time, we're using local time, and all the machines have the correct time.

Link to comment
Share on other sites

On 10/19/2018 at 10:35 AM, MartinK said:

Could you please select one specific client with this problem and open "execution history"? It is possible that scan is actually started at correct time, but maybe it takes so long? Is it possible that scan is started in different time due to timezone differences ? Are you actually using local or UTC time when defining task trigger.

The scans are starting at the correct times.
Set to use local time.
Client complained yesterday of the same thing.
Today @ 9am, the scan ins't over yet. It's been running for 8 hours.
Yesterday it started at 1am and it ended at 6pm, but that was because the user was forced to keep pausing the scan, or else he couldn't work.

If they're indeed taking this long, it's a serious problem.

configs.png.faa81ddf7b23f8c6867e51c54afe62a2.png

Edited by NumberFive
Link to comment
Share on other sites

UPDATE

Went to the client to check out the logs.
Tried to export, but probably missed something because it only exported :

<?xml version="1.0" encoding="utf-8" ?>
<ESET>
  <LOG>
    <RECORD>
      <COLUMN NAME="Hora">23-10-2018 01:00:00</COLUMN>
      <COLUMN NAME="Pastas rastreadas">C:\</COLUMN>
      <COLUMN NAME="Rastreadas">3072021</COLUMN>
      <COLUMN NAME="Infectadas">0</COLUMN>
      <COLUMN NAME="Limpas">0</COLUMN>
      <COLUMN NAME="Status">Concluído</COLUMN>
    </RECORD>
 </LOG>
</ESET>

But anyway, since the scan was running I checked the scan log, and there were alot of yellow messages all with info like:

I'll go back to the client late this afternoon and I'll get a screenshot of the messages (or part of them).

---edited---

Attached 2 new screenshots

The messages says "Archive is password protected" and the bottom one as messages like "Not possible to open" "extract error"

1772867213_SemTtulo.thumb.png.f4ed390069aba8e139428617a178d743.png899947432_SemTtulo2.thumb.png.f9c7471d0266d1efb2f22efd932bc0e8.png

Edited by NumberFive
Link to comment
Share on other sites

  • 2 weeks later...
  • ESET Staff

@NumberFive I am not good in Spanish, but it looks to me, that the amount of files scanned is 3+ million.

Can you maybe share some details about the affected machine? Size of the disk? Type of the drive? What is the configuration of the scan? Does it scan local drives only, or "all targets" is set?

Link to comment
Share on other sites

On 11/2/2018 at 11:07 AM, MichalJ said:

@NumberFive I am not good in Spanish, but it looks to me, that the amount of files scanned is 3+ million.

Can you maybe share some details about the affected machine? Size of the disk? Type of the drive? What is the configuration of the scan? Does it scan local drives only, or "all targets" is set?

It's Portuguese, but close enough:)..

The scan was set to full, I've changed it to smart scan to test (don't have feedback yet).
It's a standart 500gbs HDD.
Scanning for C:\ only.

Link to comment
Share on other sites

  • Administrators

Try disabling scanning of archives. Since they may contains gigabytes of data that needs to be unpacked and scanned, it obviously takes a lot of time.

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...