Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 1 subscriber
  • Views 2466 views
  • Users 0 members are here
Options
Suggested
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

Laptop hanging on auto-update when first switched on

RogueViper

Hi all,

One of my laptop users has been having issues with his laptop taking a long time to perform an auto-update first thing in the morning. Generally for the first 15 minutes the user cannot carry on working until the update completes. Outlook seems to freeze and other applications hang. The laptop is fairly old, but has plenty of memory and hard drive space. 

I've copied and pasted a snippet of the autoupdate log and it does seem to show the process hanging (from start to finish it takes 20 minutes):

Trace(2012-Sep-10 08:28:10): CIDUpdate(SyncProduct.Start): SAVXP, http://***********/sophos/CIDs/S001/SAVSCFXP/
Trace(2012-Sep-10 08:28:10): CIDUpdateLocation::Sync - Updating from http CID: http://************/sophos/CIDs/S001/SAVSCFXP/savxp
Trace(2012-Sep-10 08:28:10): CIDSync(CidSyncMessage):
Trace(2012-Sep-10 08:28:12): CIDSync(CidSyncMessage): zbot-ciw.ide
Trace(2012-Sep-10 08:28:12): CIDSync(CidSyncMessage): ranso-iq.ide

Trace(2012-Sep-10 08:32:57): CIDSync(CidSyncMessage): agen-xjp.ide
Trace(2012-Sep-10 08:32:57): CIDSync(CidSyncMessage): agen-xsa.ide

*************************************
Trace(2012-Sep-10 08:40:21): CIDSyncCallback, SynchronisationTerminated - Code = 0
Trace(2012-Sep-10 08:40:22): CIDSyncCallback, SynchronisationTerminated - MapFile = C:\Program Files\Sophos\AutoUpdate\cache\savxp.map
Trace(2012-Sep-10 08:48:16): CIDUpdateLocation::SyncProduct - Product Checksum: b931696e5aa9b1f3f8130e491d60d4be
Trace(2012-Sep-10 08:48:17): CIDUpdate(PrimarySuccess):
Trace(2012-Sep-10 08:48:18): UpdateLocationFacade::SyncProduct: Last Update Mechanism = CID
Trace(2012-Sep-10 08:48:18): CIDUpdateLocation::SyncProduct - Updating Product: Sophos AutoUpdate
Trace(2012-Sep-10 08:48:18): CIDUpdate(SyncProduct.Start): Sophos AutoUpdate, http://************/sophos/CIDs/S001/SAVSCFXP/
Trace(2012-Sep-10 08:48:19): Checksum found in master.upd matches cached cidsync.upd : bf9b3c06. Skipping download
Trace(2012-Sep-10 08:48:19): CIDUpdate(PrimarySuccess):
Trace(2012-Sep-10 08:48:20): ALUpdate(DownloadEnded):

:29307


This thread was automatically locked due to age.
Parents
  • 0

    Hello Mike,

    it seems to be slow during syncing the files (there's already a significant delay after the empty first CIDSync(CidSyncMessage):). Of course a sync is to be expected (i.e. new files have been added to the CID) after the computer is switched on,  but otherwise the "first update" is not special and thus I assume the almost-hang also happens once or twice during the day - the logs should show this. I notice that it takes another three seconds from the CIDUpdate(PrimarySuccess) to ALUpdate(DownloadEnded) - my desktop is in its 9th year but there it completes in less than a second. The SAVXP sync constantly takes about 20 seconds - this would be a factor of 60. Admittedly I have no explanation for this. Guess AutoUpdate is checksumming the cache files at this point - nevertheless this shouldn't monopolise the CPU (and AFAIK it's neither I/O- nor memory-demanding).       

    You didn't mention the machine to be generally slow and even if AutoUpdate syncing would expose some "hidden" hardware problem I'd expect it to show elsewhere as well.

    Thinking about it - if Outlook seems to freeze and other applications hang they must have been started already when AutoUpdate kicks in. If AutoUpdate is disabled (and then a manual requested)  or delayed for, say, 900 seconds - is the behaviour the same?

    Christian

    :29319
Reply
  • 0

    Hello Mike,

    it seems to be slow during syncing the files (there's already a significant delay after the empty first CIDSync(CidSyncMessage):). Of course a sync is to be expected (i.e. new files have been added to the CID) after the computer is switched on,  but otherwise the "first update" is not special and thus I assume the almost-hang also happens once or twice during the day - the logs should show this. I notice that it takes another three seconds from the CIDUpdate(PrimarySuccess) to ALUpdate(DownloadEnded) - my desktop is in its 9th year but there it completes in less than a second. The SAVXP sync constantly takes about 20 seconds - this would be a factor of 60. Admittedly I have no explanation for this. Guess AutoUpdate is checksumming the cache files at this point - nevertheless this shouldn't monopolise the CPU (and AFAIK it's neither I/O- nor memory-demanding).       

    You didn't mention the machine to be generally slow and even if AutoUpdate syncing would expose some "hidden" hardware problem I'd expect it to show elsewhere as well.

    Thinking about it - if Outlook seems to freeze and other applications hang they must have been started already when AutoUpdate kicks in. If AutoUpdate is disabled (and then a manual requested)  or delayed for, say, 900 seconds - is the behaviour the same?

    Christian

    :29319
Children
No Data
Cookie Information Banner