Update issue - getting Update failed (error: 12)
Reported by
asarac...@gmail.com,
Dec 15 2016
|
|||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:50.0) Gecko/20100101 Firefox/50.0
Steps to reproduce the problem:
1. Click on About Google Chrome
2. Tries to update automatically to latest version
3. Update fail error - see below for error details
What is the expected behavior?
Browser updates to new version without timing out or failing.
What went wrong?
Update failed (error: 12)
Error details:
2016-12-15 09:47:40.409 GoogleSoftwareUpdateAgent[6509/0x7fff7a4f4000] [lvl=3] -[KSAgentApp run] Unable to obtain Google Software Update Agent lock(another agent may be running):
<KSError:0x100300440
domain="com.google.UpdateEngine.CommonErrorDomain"
code=601
userInfo={
date = 2016-12-15 02:47:40 +0000;
line = 602;
filename = "KSLockFile.m";
function = "-[KSLockFile(PrivateMethods) flockFD:path:timeoutDate:]";
NSFilePath = "/var/folders/xz/376f1phx6x356_crrxqf1p400000gn/T/.keystoneAgentLock";
NSLocalizedDescription = "KSLockFile timed out.";
}
Did this work before? Yes 54.0.2840.98 (64-bit)
Chrome version: 54.0.2840.98 (64-bit) Channel: n/a
OS Version: OS X 10.11
Flash Version: Shockwave Flash 22.0 r0
,
Dec 15 2016
Failed three times. Restarted laptop. Failed once more. Then updated to current version: Version 55.0.2883.95 (64-bit) Google Chrome is up to date. So it's now working again. Thanks for your prompt email.
,
Dec 15 2016
The part of the error message "another agent may be running" is relevant. This may be normal, if the updater is downloading or installing something else in the background. Both downloading and installing may take some time. The fact that it failed one more time with the same error after the restart is a good indication that some processing still needed to be done. Unfortunately, this could also be an indication for a hang in the agent. Would you be able to run this command for us and attach the collected logs? 1. Open the Terminal app. 2. Copy and paste the command below and press enter: /Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/ksdiagnostics 3. Attach the generated .zip file to this bug. The collected logs will tell us which part took so long.
,
Dec 15 2016
One more note: if the command above fails with "No such file or directory", then please prefix it with "~": ~/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/ksdiagnostics
,
Dec 22 2016
,
Apr 11 2017
Resolving as won't fix, as there wasn't update to the bug. Please reopen if you encounter this problem and provide the diagnostics mentioned in comment #3. |
|||
►
Sign in to add a comment |
|||
Comment 1 by karandeepb@chromium.org
, Dec 15 2016Owner: borisv@chromium.org
Status: Assigned (was: Unconfirmed)