Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Running scan but not completing

Hi,

I'm running a full scan on my internal MacBook hard drive but the scan doesn't complete, I can't see any errors, and when I check the console it says the scan has never run.


Any ideas?

On 10.8, Sophos version 8.0.14C

TIA :smileyhappy:

:1012222


This thread was automatically locked due to age.
  • I downloaded Sophos yesterday and I am having the same problem- any suggestions?

    :1012470
  • Hi fajansp,

    See my post near the top of the board about the version 9.0 preview. It addresses an issue that sounds similar to the one described in this thread. Please let me know how it goes.

    :1012474
  • Hi bobcook - I downloaded v9 and tried it.  Seemed to run longer, but I tried it doing a full scan twice, and twice it hung and I found this error in the logs:

    6/28/13 10:50:57.593 PM SophosWebD[99878]: <SMENode: 0x7fa321610e60> localNode csc:1ERROR! encountered an error while writing to outputstream| error:Error Domain=NSPOSIXErrorDomain Code=32 "The operation couldn’’’’t be completed. Broken pipe"

    :1012480
  • Hi GeekZero,

    The error you mention isn't related to scanning. Its related to the web protection feature, and it means either the browser or the remote server closed the connection unexpectedly - it happens and its safe to ignore.

    As for a "hung" scan - what happens if you close and reopen the GUI? The scan isn't tied to the GUI being open, it runs in the background. Just speculating that maybe the scan got disconnected from the worker in the back end. Its a weird problem and we are really struggling to track it down.

    :1012492
  • I have experienced a problem with scanning local drives on my MAC, where the scan stops part way through, and nothing seems to restart it.
    If a scan is interrupted by an update it freezes.  I have proved this by setting the update frequency to 2 days, and the scan then continued to the end.

    I reset to 1 day for normal use, and temporarily extend to 2 days when I do a full local scan.

    Custom scans seem OK, as they run considerably fewer than the millions of files involved in a full local drive scan.

    :1012698
  • Hi Olde1,

    Thanks for the feedback and the diagnostics. Can you tell me which version you are using? We believe this type of issue is addressed in version 9, but want to check (nothing like real world experience to prove us right or wrong).

    :1012702
  • I've just downloaded the version 9 preview so will see how that goes! I like the fact that scans can now be scheduled. I've recently tested Comodo and that just crashed on Mountain Lion - wouldn't even run - so I'm hoping things are better in this release!

    :1012706
  • I am on V8.0.16C

    Will try V9.

    :1012708
  • Can I get V9 for the free version?

    :1012710