Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 13 subscribers
  • Views 14463 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

An update lock is already held; cannot start another update now

AndyR

I received an alert today for a device that has missed two updates. Looking at the susvc.log file on the machine I see lots of "An update lock is already held; cannot start another update now".

A restart of the AutoUpdate service didnt fix the issue, is there something extra I would have needed to do to resolve the problem please? A reboot did sort the issue, however, if there is a quick fix for next time that avoids the necessity of a reboot then great.

Regards
Andy



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

    Hi

    Could you please check under Autoupdate logs(C:\ProgramData\Sophos\AutoUpdate\logs) and check if you see any specific error? If the version of the endpoint is updated it will require a reboot. 

    Shweta

    Community Support Engineer | Sophos Technical Support
    Are you a Sophos Partner? | Product Documentation | @SophosSupport | Sign up for SMS Alerts
    If a post solves your question use the 'Verify Answer' link.
    The New Home of Sophos Support Videos! - Visit Sophos Techvids
  • 0 in reply to Shweta

    There were no error or failure messages in the SophosUpdate.Log for that day. However, following a reboot it did show this:

    ERROR su-setup output:
    ERROR Error parsing su-setup output: err=1 offset=0
    INFO  Processing install failed Health event for: {E17FE03B-0501-4aaa-BC69-0129D965F311} (Sophos Anti-Virus for Windows)
    INFO  Saving intermediate state after installing E17FE03B-0501-4aaa-BC69-0129D965F311

    Not a problem, I was just hoping there was an easy way to kill what looked like a stuck update event without having to reboot. This happened on a  laptop so no great problem asking the user to reboot it. I was looking for an easy fix in case this happened on a Server as these are obviously more difficulty to reboot.

    Regards

    Andy.

Reply
  • 0 in reply to Shweta

    There were no error or failure messages in the SophosUpdate.Log for that day. However, following a reboot it did show this:

    ERROR su-setup output:
    ERROR Error parsing su-setup output: err=1 offset=0
    INFO  Processing install failed Health event for: {E17FE03B-0501-4aaa-BC69-0129D965F311} (Sophos Anti-Virus for Windows)
    INFO  Saving intermediate state after installing E17FE03B-0501-4aaa-BC69-0129D965F311

    Not a problem, I was just hoping there was an easy way to kill what looked like a stuck update event without having to reboot. This happened on a  laptop so no great problem asking the user to reboot it. I was looking for an easy fix in case this happened on a Server as these are obviously more difficulty to reboot.

    Regards

    Andy.

Children
Unfiltered HTML