Issue 520135 in chromium: Update failed (error: 11) on Mac Chrome

[chro...@googlecode.com]

Status: Untriaged
Owner: ----
Labels: Type-Bug Pri-2 OS-Mac

New issue 520135 by ero...@chromium.org: Update failed (error: 11) on Mac
Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

Recently I am getting this error under About Google Chrome:
Update failed (error: 11)

Updates were working fine until now (and in fact the current version is
still the latest stable).
Restarting Chrome does not resolve the problem.

Attachments:
update-error.png 90.3 KB

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Comment #1 on issue 520135 by ecksj121...@gmail.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

I have been getting the exact error message on my Mac for at least a year.
It seems like the update installs, or at least the new version "number"
appears above the error message. Is the newest version really installed
and the error message an error in itself?? All of the suggested solutions
to eliminate the error 11 message on my Mac never work to eliminate it.
Can anyone provide a SIMPLE solution to my and eroman's problem??

[chro...@googlecode.com]

Updates:
Labels: Cr-Internals-Installer

Comment #3 on issue 520135 by pucchaka...@chromium.org: Update failed

(error: 11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

(No comment was entered for this change.)

[chro...@googlecode.com]

Updates:
Status: Unconfirmed
Owner: ---
Cc: ranjit...@chromium.org
Labels: Needs-Feedback

Comment #4 on issue 520135 by ranjit...@chromium.org: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

@ eroman: Thanks for filing this issue, but we are unable to reproduce the
issue from our end , attached screen shot for the same. Could you please
click on the button "Set up Automatic updates for all Users" button and
provide you credentials.

Please check once you provide the credentials and update us with your
observations.

Attachments:
Screen Shot 2015-08-17 at 11.11.28 AM.png 85.7 KB

[chro...@googlecode.com]

Comment #5 on issue 520135 by ero...@chromium.org: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

I am no longer getting the error. But before closing I would like to at
least better understand what was happening, and what this error means.

What logs of other data can I provide to diagnose this?

[chro...@googlecode.com]

Comment #6 on issue 520135 by ec...@cox.net: Update failed (error: 11) on
Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

I am still getting the " update failed error 11" message whenever I try and
download a chrome update. I am not a techie like all of you guys, so I will
need a simple explanation for how to fix this if there is one. Thanks in
advance for your help. John

[chro...@googlecode.com]

Comment #7 on issue 520135 by ranjit...@chromium.org: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

@ ecksj: Are you being prompted with button "Set up Automatic updates for
all Users", if yes please click on it and provide your system credentials
(username and password). It should get updated with no errors.

Please let us know with your observations.

[chro...@googlecode.com]

Comment #9 on issue 520135 by ecksj121...@gmail.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

No I'm not being prompted with "Set up AutomaticUpdates....". I just
receive notification that a new update version of Chrome is available. I
click on "update now." It seems to install because as I mentioned above,
the new version number appears when I click "About Chrome." However the
same "update failed: error 11" message appears just below the new version
number as shown in eroman's snapshot that began this issue.

[chro...@googlecode.com]

Comment #10 on issue 520135 by ranjit...@chromium.org: Update failed

(error: 11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

Could you please try a fresh installation of chrome by clearing data from
folder

/Users/<user>/Library/Application Support/Google/

Please let us know with your observations once you navigate back to
chrome://chrome page.

[chro...@googlecode.com]

Updates:
Cc: bor...@chromium.org

Comment #14 on issue 520135 by erikc...@chromium.org: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

+borisv, as this is likely a Keystone error.

[chro...@googlecode.com]

Comment #17 on issue 520135 by bor...@chromium.org: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

There are multiple bugs filed against Apple and to the best of my
knowledge, El Capitan (OS X 10.11) should be addressing the issues. I have
not seen a commitment from Apple to fix the problem on Yosemite (10.10).
The best resource for fixing the issue seems to be the Apple forums:

https://discussions.apple.com/thread/6995894?tstart=0

On the positive side, as the problem is somewhat intermittent, we have
noticed that the machines are typically kept up to date, due to the
automatic updates retry logic. This is why we have not pursued a more
aggressive fix that leverages the Chrome network stack.

[chro...@googlecode.com]

Comment #20 on issue 520135 by bor...@chromium.org: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

Yes, you are correct. Update error 11 is typically issued when Google
Software Update cannot talk to the update server and hence cannot confirm
if this is the latest version. So even if you are on the latest version,
you may see this error. The simplest way to see that is to disconnect your
network cable, disable Wifi and check for updates by going to
chrome://chrome.

[chro...@googlecode.com]

Comment #21 on issue 520135 by ecksj121...@gmail.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

Thank you very much

[chro...@googlecode.com]

Comment #22 on issue 520135 by harpreet...@gmail.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

After updating my Mac OSX to 10.11.1 I'm started getting this weird error
message:

Update failed (error: 11)

Tried reinstalling and everything I found on internet but no use. Need some
immediate solution to this. Attaching the screenshot as well for reference.

Attachments:
Screen Shot 2015-10-24 at 4.31.54 PM.png 92.3 KB

[chro...@googlecode.com]

Comment #26 on issue 520135 by Brian.Fu...@gmail.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

Hello, thank you very much for your help. I tried running ksadmin three
times. Each time, I was able to successfully load a page in Safari within
about 1 or 2 seconds after ksadmin timed out. I could not find “ksfetch” in
/var/log/system.log (“All Messages” on the console) - should I search
another log file?

I did find the following messages:

2015-11-24 4:06:44.738 PM ksadmin[6520]: KSOutOfProcessFetcher timeout
while waiting for fetch. [com.google.UpdateEngine.CommonErrorDomain:1502
- 'https://tools.google.com/service/update2?cup2hreq=8ce277548fabc51d93eec757a7f4ceaccd8b73efc4faccf0d997d4469d4a7056&cup2key=5:2675760806'
- 'KSOutOfProcessFetcher.m:618']
2015-11-24 4:06:44.739 PM ksadmin[6520]: KSServerUpdateRequest fetch
failed. (productID: com.google.Chrome)
[com.google.UpdateEngine.CoreErrorDomain:702
- 'https://tools.google.com/service/update2?cup2hreq=8ce277548fabc51d93eec757a7f4ceaccd8b73efc4faccf0d997d4469d4a7056&cup2key=5:2675760806']
(KSOutOfProcessFetcher timeout while waiting for fetch.
- 'https://tools.google.com/service/update2?cup2hreq=8ce277548fabc51d93eec757a7f4ceaccd8b73efc4faccf0d997d4469d4a7056&cup2key=5:2675760806'
[com.google.UpdateEngine.CommonErrorDomain:1502])

2015-11-24 4:13:28.999 PM ksadmin[6545]: KSOutOfProcessFetcher timeout
while waiting for fetch. [com.google.UpdateEngine.CommonErrorDomain:1502
- 'https://tools.google.com/service/update2?cup2hreq=8ab577f8d84903716bff8f9295a2dc21f943b8474e9049571303cf0543c4d5da&cup2key=5:1683868518'
- 'KSOutOfProcessFetcher.m:618']
2015-11-24 4:13:28.999 PM ksadmin[6545]: KSServerUpdateRequest fetch
failed. (productID: com.google.Chrome)
[com.google.UpdateEngine.CoreErrorDomain:702
- 'https://tools.google.com/service/update2?cup2hreq=8ab577f8d84903716bff8f9295a2dc21f943b8474e9049571303cf0543c4d5da&cup2key=5:1683868518']
(KSOutOfProcessFetcher timeout while waiting for fetch.
- 'https://tools.google.com/service/update2?cup2hreq=8ab577f8d84903716bff8f9295a2dc21f943b8474e9049571303cf0543c4d5da&cup2key=5:1683868518'
[com.google.UpdateEngine.CommonErrorDomain:1502])

2015-11-24 4:16:07.384 PM ksadmin[6556]: KSOutOfProcessFetcher timeout
while waiting for fetch. [com.google.UpdateEngine.CommonErrorDomain:1502
- 'https://tools.google.com/service/update2?cup2hreq=67d64942622077fb8eb75c471213ef4e65dad44ad78dfa2b6045aec31ec35f8c&cup2key=5:807660247'
- 'KSOutOfProcessFetcher.m:618']
2015-11-24 4:16:07.384 PM ksadmin[6556]: KSServerUpdateRequest fetch
failed. (productID: com.google.Chrome)
[com.google.UpdateEngine.CoreErrorDomain:702
- 'https://tools.google.com/service/update2?cup2hreq=67d64942622077fb8eb75c471213ef4e65dad44ad78dfa2b6045aec31ec35f8c&cup2key=5:807660247']
(KSOutOfProcessFetcher timeout while waiting for fetch.
- 'https://tools.google.com/service/update2?cup2hreq=67d64942622077fb8eb75c471213ef4e65dad44ad78dfa2b6045aec31ec35f8c&cup2key=5:807660247'
[com.google.UpdateEngine.CommonErrorDomain:1502])

[chro...@googlecode.com]

Comment #29 on issue 520135 by Brian.Fu...@gmail.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

Hi Boris, thanks again for your help. Per your request, I tried:

$ sudo killall -9 networkd

As expected, the daemon started up again automatically. Unfortunately, the
chrome update still fails with error: 11. Actually, I tried this three
times. On 3rd try, I quit and restarted chrome. The update still failed. So
far, from my experience, rebooting is the only thing that clears the update
error.

[chro...@googlecode.com]

Comment #30 on issue 520135 by j...@google.com: Update failed (error: 11)

on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

FYI, I was having this same problem, and `sudo killall -9 networkd` did fix
the problem for me.

[chro...@googlecode.com]

Comment #31 on issue 520135 by bor...@chromium.org: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

Thanks, jam. It sounds like restarting the network daemon resolves the
problem for most users.

Brian thank you for the additional information too. So far we have 2 users
reporting the same behavior of not recovering after daemon restart - e.g.
the last comments on
https://code.google.com/p/chromium/issues/detail?id=557593. If you happen
to have time, I would really appreciate if we can check if your machine can
reach to our update server network-wise. We have seen issues with some
proxies and unusual DNS settings that block such access:
Please download the attached request.xml file, navigate in the terminal to
the folder where it is downloaded (typically ~/Downloads) and execute the
command:
curl -d @request.xml https://tools.google.com/service/update2

You should see output starting with: <?xml version="1.0"
encoding="UTF-8"?>. This would confirm that there are no network-related
issues (proxies, bad DNS setup, malware). If you do not see it, please add
a --verbose and run the command again, looking for any errors:
curl -verbose -d @request.xml https://tools.google.com/service/update2

[chro...@googlecode.com]

Comment #35 on issue 520135 by bor...@chromium.org: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

I talked to pfeldman offline. Restarting the network daemon fixed the
connectivity issue. The following error 11 is due to a smaller issue
impacting only the user-initiated update checks on the Canary builds. We
have a fix ready for the latter and it will be released soon.

[chro...@googlecode.com]

Comment #36 on issue 520135 by ec...@cox.net: Update failed (error: 11) on
Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

Thanks Boris. I don't know what a "daemon" is and I don't know how to "run
the command" sudo killall -9 networks, that you mentioned. Could you
please give me precise instructions on how to do that? And will I need to
do it each time Chrome announces an update?? Sorry to be such a idiot about
all this stuff but you guys speak a language that I don't understand. I
really appreciate your help!---john

[chro...@googlecode.com]

Comment #39 on issue 520135 by bor...@chromium.org: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

Thank you, robertleeblairjr. Error 11 is somewhat generic, so your
experience probably does not match most of the users we have seen so far.
Also, you are not seeing this on a canary build are you? If not, would you
be able to run
~/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/ksdiagnostics

This command should collect the previous logs too - please send me the
generated diagnostics file to bor...@chromium.org. Please note that the
diagnostics .zip file will extract the local logs for the updater and hence
will contain your machine user name as part of the file paths - e.g.
/Users/johnsmith/..., so we do not want that data to be published in this
public bug.

[chro...@googlecode.com]

Comment #41 on issue 520135 by bor...@chromium.org: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

robertleeblairjr, thank you for sending over the diagnostic data. Yes,
unfortunately, your reason for error 11 is the same as the problem that
pfeldman experienced above after restarting networkd daemon. Symptom: after
setting Chrome to update for all users, user-initiated update check fails
with error 11. Apparently, as of this morning this issue impacts the stable
release as well.

The problem is benign - auto-updates for your case would work perfectly
fine if you "Set Up Automatic Updates for All Users". As such Chrome would
be updated every 5 hours. Only manual checking in Chrome fails
intermittently with such error 11. A fix of the updater is ready and being
actively tested. Unless we discover something major it should be out within
1-2 business days.

[chro...@googlecode.com]

Comment #43 on issue 520135 by rohi...@chromium.org: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

Issue 568712 has been merged into this issue.

[chro...@googlecode.com]

Comment #45 on issue 520135 by bor...@chromium.org: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

Thank you, Eve. Which part rings true with your machine? The problem
with "Set Up Updates for All Users" (issue 568712), experienced by
robertleeblairjr and pfeldman has been fixed.

[chro...@googlecode.com]

Comment #46 on issue 520135 by danishym...@gmail.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

Having the same issues on my mac (OS X 10.11.2) Update failed (error:11)

Attachments:
Screen Shot on 2015-12-18 at 20-54-22.png 338 KB

[chro...@googlecode.com]

Comment #47 on issue 520135 by bor...@chromium.org: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

Thank you, danishymemon. Please restart Chrome and check if it still
reports error 11 when you navigate to chrome://chrome. If yes, the next
step is to check if Safari is able to load any pages.

[chro...@googlecode.com]

Comment #48 on issue 520135 by ec...@cox.net: Update failed (error: 11) on
Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

I an weighing in again. I did everything you asked Boris 1) restarted
Chrome and error 11 message still there 2) typed chrome://chrome in the
chrome address bar, error 11 still there 3) opened Safari, and it worked
fine--opened any and all internet pages. Now What?? And what does Safari
have to do with the Chrome error 11 message problem??---John

[chro...@googlecode.com]

Comment #49 on issue 520135 by hanna...@icloud.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

the same issue on (OS X 10.11.2). uninstalling and reinstalling 2 times has
not fixed it.
could this extension be to blame?
https://chrome.google.com/webstore/detail/shutterstock-image-search/ifejkfgmpbfbdpljbcefaeidphdpnlem

Attachments:
Untitled21.jpg 38.2 KB

[chro...@googlecode.com]

Comment #50 on issue 520135 by hanna...@icloud.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

here is the solution: from
https://support.google.com/chrome/answer/6315311?hl=en

Attachments:
g.jpg 503 KB

[chro...@googlecode.com]

Comment #51 on issue 520135 by bor...@chromium.org: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

Thank you, hannabou. This is a good solution. ecksj, please try it (commend
#50) and let us know what errors you see. Please sanitize that text before
posting it here, as it may contain your username,
e.g. 'path="/Users/JohnSmith/Library/..'. If you encounter your username in
the output of CheckForUpdatesNow.command, please replace your username
with "USER" before posting your response to this public issue tracker.

[chro...@googlecode.com]

Comment #52 on issue 520135 by diego.ca...@gmail.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

While I was at it, stuck since weeks with this bug in Google Chrome, I've
tried what you suggested, also trying a few things to help troubleshoot.

After executing the command as suggested, after a few minutes I've got:

{{{
$
/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/CheckForUpdatesNow.command ;
exit;
2015-12-21 23:20:01.250 GoogleSoftwareUpdateAgent[29305/0xb029b000] [lvl=3]
-[KSOutOfProcessFetcher(PrivateMethods) helperDidTimeout:]

KSOutOfProcessFetcher timeout while waiting for fetch.
[com.google.UpdateEngine.CommonErrorDomain:1502

- 'https://tools.google.com/service/update2?cup2hreq=c1eb92f95f7a2158dc854c212a187ab21af67d773207a55494b3d29ec179bf32&cup2key=5:2392026842'
- 'KSOutOfProcessFetcher.m:618']
2015-12-21 23:20:01.251 GoogleSoftwareUpdateAgent[29305/0xb029b000] [lvl=3]
-[KSServerUpdateRequest(PrivateMethods) fetcher:failedWithError:]
KSServerUpdateRequest fetch failed. (productID: com.google.GoogleDrive)
[com.google.UpdateEngine.CoreErrorDomain:702
- 'https://tools.google.com/service/update2?cup2hreq=c1eb92f95f7a2158dc854c212a187ab21af67d773207a55494b3d29ec179bf32&cup2key=5:2392026842']

(KSOutOfProcessFetcher timeout while waiting for fetch.

- 'https://tools.google.com/service/update2?cup2hreq=c1eb92f95f7a2158dc854c212a187ab21af67d773207a55494b3d29ec179bf32&cup2key=5:2392026842'
[com.google.UpdateEngine.CommonErrorDomain:1502])
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.
Deleting expired sessions...7 completed.

[Process completed]
}}}

which is basically what I got looking at the console (fetch timeout).

Then I've managed to retrieve another legitimate IP corresponding to
tools.google.com and put it into /etc/hosts, and tried again the command,
with the exact same result.

I can ping and curl to both IP's (obtaining a 404 but I think this works as
expected considering that curl isn't a legitimate ks client).

After restoring the previous state for domain mapping, I've closed all
Google apps (Chrome and Drive) and checked into Activity Monitor that
anything Google and KS* related wasn't there, then I've ran again the
command, and this time the output changed (not sure this is positive):

{{{
$
/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/CheckForUpdatesNow.command ;
exit;
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.
}}}


Then opened again Chrome (not Drive) and tried to update again: this time
it was stuck forever trying to update.

After some more minutes, I've checked and the ksadmin process was there:
I've killed it, suddenly a new ksadmin process started immediately followed
by ksfetch. I've checked again after a few more minutes and both were gone,
and -surprise- error: 11 was again there in Chrome.

Hope it helps.

[chro...@googlecode.com]

Comment #53 on issue 520135 by ec...@cox.net: Update failed (error: 11) on
Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

Boris--I followed the instructions. I copied the "location" from hannabou
into the "Go to Folder" in finder. (the 2nd location could not be found).
I double clicked the "CheckForUpdateNow.command"which took me terminal and
after a few seconds the message "process completed" appeared. i closed
terminal. When I reopened Chrome and clicked on "about Chrome'" the
same "update failed (error:11)" appeared as always. And as you suggested
my "username" was not in the "CheckForUpdateNow.command" Anything else to
try? Thanks again.

[chro...@googlecode.com]

Comment #54 on issue 520135 by hanna...@icloud.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

as a followup, the solution i posted seems to have resolved the problem for
me.

Attachments:
Untitled23.tiff 93.3 KB

[chro...@googlecode.com]

Comment #55 on issue 520135 by hanna...@icloud.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

as a followup, the solution i posted seems to have resolved the problem for
me.


Attachments:

Untitled23.jpg 133 KB

[chro...@googlecode.com]

Comment #56 on issue 520135 by robertle...@gmail.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

Thanks hannabou. After being informed that the new release of Chrome,
47.0.2526.0, would resolve this problem; I used the solution hannabou
posted and this seems to be a fix. I have not rebooted to see if it
persists. BTW. Did you discover this solution through troubleshooting the
problem locally or was this posted elsewhere that you had come upon?
We appreciate the help of the developers but don't jump the gun by
yelling "solution" until you know for certain.

[chro...@googlecode.com]

Comment #57 on issue 520135 by hanna...@icloud.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

As far as i am concerned that solution persists, Robert.
The link i provided is the source.

[chro...@googlecode.com]

Comment #58 on issue 520135 by bor...@chromium.org: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

I agree with hannabou - CheckForUpdatesNow.command is a script that we
distribute with Google Software Update product for manually checking for
updates. The link hannabou provided is the official Google support page. It
is a text file and you can all see it. The script runs the same command
that both Chrome and automated update checks execute
(GoogleSoftwareUpdateAgent).
robertleeblairjr, thanks again for sending me the diagnostics. The problem
on your machine was due to earlier version of the updater (not Chrome
itself) that we fixed last week with a new release of the updater, as
described by https://code.google.com/p/chromium/issues/detail?id=568712
(now marked as fixed). Hannabou, it is likely that you experienced the same
problem and it was resolved as soon as the updater self-updated on your
machine to its latest version as result of running manually the update
command. Else, it would typically take ~5 hours to auto-update.
Diego Caravana and others on this thread are experiencing different
problem - a persistent timeout in the attempts to talk to the update
server: "KSOutOfProcessFetcher timeout while waiting for fetch.".

Diego, please try the instructions in my comment #31 to see if 'curl' can
really download anything from our update server. We are suspecting an
antivirus or other process blocking ksfetch (our download helper). Also,
let us know if you use any antivirus software.

[chro...@googlecode.com]

Comment #59 on issue 520135 by diego.ca...@gmail.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

No antivirus/firewall in use on my machine (not even the OS firewall).

I'm sorry but I cannot find the request.xml file attached anywhere on this
bug, and if it's attached to
https://code.google.com/p/chromium/issues/detail?id=557593, I get a 403 (no
permission) error (I cannot even read your complete username since it's
shortened).

[chro...@googlecode.com]

Comment #60 on issue 520135 by robertle...@gmail.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

@borisv Which version are you talking about? If it's Chrome version
47.0.2526.106, then I had this version clean installed since yesterday.
This error 11 duplicated, as in previous versions, until I followed the
instructions provided by hannabou to resolve the error. I don't consider
the updated version of Chrome updater script,1.2.3.738, to be a resolution
if I have to follow the directions of initiating the update from the
command line by navigating to a particular directory. This should be
performed by the script if the function is selected by the user in the
chrome interface. Either way, I'm not experiencing this problem, thus far.
Perhaps, the problem will be resolved in a version in the future.

[chro...@googlecode.com]

Comment #61 on issue 520135 by ec...@cox.net: Update failed (error: 11) on
Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

Boris--Before I next update Chrome when I am informed that a new update is
available, should I first try hannabou's solution process, and then try the
update?? If so, I will do that each time a new chrome update is
avaialable.--John

[chro...@googlecode.com]

Comment #62 on issue 520135 by bor...@chromium.org: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

@Diego: apologies for the delayed response and the lack of of attachment in
that comment. I am reattaching the file now.
@robertleeblairjr, Chrome version shouldn't be related, as the Chrome
application calls the updater utilities that are returning an error. The
updater updates itself and these utilities on its own. Unfortunately, there
are multiple reasons for error 11. E.g. if you just installed Chrome and
check for updates immediately the reason could be that the updater is
self-updating at that exact time. Also, Chrome tends to cache the error, so
one would see this error until restarting Chrome. If hannabou's
instructions are working, I wouldn't be concerned too much. This means that
the updater is doing its job overall and the error in Chrome may be
transient. We are working on improving the error reporting, please stay
tuned.
@ecksj, I would not recommend manually checking for updates via the
hannabou's suggestion, unless your Chrome instance is visibly behind the
latest version (e.g. more than 1 day old and the machine has been on for
more than 1hr). Based on the diagnostic reports that I received from you,
auto-updating works on your machine and checks for updates every 5 hours as
expected.

Attachments:
request.xml 539 bytes

[chro...@googlecode.com]

Comment #63 on issue 520135 by diego.ca...@gmail.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

Boris, I was able to run the command which returned:

<?xml version="1.0" encoding="UTF-8"?><gupdate
xmlns="http://www.google.com/update2/response" protocol="2.0"
server="prod"><daystart elapsed_days="3282" elapsed_seconds="63115"/><app
appid="com.google.Keystone" cohort="" cohortname="" status="ok"><ping
status="ok"/><updatecheck DisplayVersion="1.2.3.738"
codebase="http://dl.google.com/dl/keystone/googledummysoftwareupdate-1.2.3.738.dmg"
fp="1.903b5331c4ebe1cb8b32b616e9ffce13c3d3d46d114b8e3aba24aa3167d675c0"
hash="M0pkhPp0MQsGhybA+uQuVMC0WwI="
hash_sha256="903b5331c4ebe1cb8b32b616e9ffce13c3d3d46d114b8e3aba24aa3167d675c0"
needsadmin="false" size="734780" status="ok"/></app></gupdate>


Notwithstanding this result, Chrome is still stuck with the update.

May not be of help, but tried to kill ksadmin while the Chrome update tab
was open: it got respawned but nothing else, instead, after closing the
tab, ksadmin spawned ksfetch.

Then if I keep the tab closed, both processes go away after a number of
minutes (didn't measure) - looking at the system log, ksfetch timed out and
failed.

The sequence is repeatable.

While looking at the system log, I've noticed a few weird things like:
- ksfetch timeout errors are always related only to Chrome
- apparently, Drive updates work (I don't have enough knowledge about ks,
but the update XML is there and definitely similar to what you posted)
- KSAgentApp can successfully upload ks stats
- I've found the Keystone.ticketstore.lock file in
/Library/Google/GoogleSoftwareUpdate/TicketStore/ and since it was quite
old I thought it was stale and tried removing it, but without any luck:

-rw-r--r-- 1 root wheel 1827 16 Dic 13:34 Keystone.ticketstore
-rw-r--r--@ 1 root wheel 0 13 Nov 17:43 Keystone.ticketstore.lock

- there's also an error (by Drive) complaining about not being able to get
a lock on /tmp/.keystone_install_lock, which again seems stale

-rw-rw-rw- 1 diego wheel 0 9 Dic 10:34 .keystone_install_lock

- in /tmp I've found also folders like:

drwx------ 3 root wheel 102 28 Dic 01:18
KSOutOfProcessFetcher.0.sAglCyxY5lzPoNgfmEvv-ZqGl-w=
drwx------ 3 diego wheel 102 28 Dic 02:01
KSOutOfProcessFetcher.501.sAglCyxY5lzPoNgfmEvv-ZqGl-w=

both contain only the ksfetch executable, both same length but the one
belonging to my user has the little @ sign at the end of the ls -l command:

-rwx------@ 1 diego wheel 163472 28 Dic 02:01 ksfetch

which in the OSX world means extended attributes, so looking at them prints:

$ sudo xattr -l
KSOutOfProcessFetcher.501.sAglCyxY5lzPoNgfmEvv-ZqGl-w\=/ksfetch
com.apple.quarantine: 0000;568097fd;Google Chrome.app;

The com.apple.quarantine attribute is related to the automatic blocking of
execution that OSX applies to files downloaded from the Internet; after
removing the attribute, apparently anything didn't change, looking at /tmp
instead I've found 4 folders related to ks, the new ones containing
a "download" executable:

drwx------ 3 root wheel 102 28 Dic 02:23
KSOutOfProcessFetcher.0.sAglCyxY5lzPoNgfmEvv-ZqGl-w=
drwx------ 3 diego wheel 102 28 Dic 02:23
KSOutOfProcessFetcher.501.sAglCyxY5lzPoNgfmEvv-ZqGl-w=
drwx------ 3 root wheel 102 28 Dic 02:23
KSOutOfProcessFetcher.bFHhEmnEsS
drwx------@ 3 diego wheel 102 28 Dic 02:23
KSOutOfProcessFetcher.q2Aey4k8hJ

As you can see, the last one has the @ sign which again means
com.apple.quarantine, which is also attached to the download file in it,
and to the ksfetch on the folder owned by my user (which makes sense
keeping into account root and normal user behavior of OSX).

Chrome update still didn't work and, after removing all the folders, error
11 is still there.

I've tried disabling Gatekeeper from System Preferences (Allow apps
downloaded from anywhere) with no luck (after closing and reopening Chrome).

Apparently all this leads to the obvious conclusion that Chrome/ks have a
bad relation with OSX/Gatekeeper, which seems weird to me but who knows,
this makes definitely sense as it explains why ksfetch times out and
matches your suspect about an antivirus issue.

[chro...@googlecode.com]

Comment #64 on issue 520135 by chase.wi...@gmail.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

I'm still having the same issue on my OSX. All the tips above I've tried.

[chro...@googlecode.com]

Comment #65 on issue 520135 by ec...@cox.net: Update failed (error: 11) on
Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

Once again my question is: How does one tell if the latest chrome update
really did update?? If the message "Update failed (error: 11)" which is
below the latest update version: "Version 47.0.2526.106 (64-bit)" is a
false "error message," I am satisfied that I have the latest Chrome
update. Can anyone tell me if that is the case.

[chro...@googlecode.com]

Comment #66 on issue 520135 by bor...@chromium.org: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

Issue 557593 has been merged into this issue.

[chro...@googlecode.com]

Comment #67 on issue 520135 by wmangl...@gmail.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

I can second that some reports of this issue are due to aggressive outbound
firewalls. On a Mac OS X system experiencing this symptom, and running
10.9.5 (Mavericks):

$
/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/MacOS/ksadmin
-S -l -P com.google.Chrome
The operation couldn’t be completed. Operation not permitted
[NSPOSIXErrorDomain:1]
KSServerUpdateRequest fetch failed. (productID: com.google.Chrome)
[com.google.UpdateEngine.CoreErrorDomain:702
- 'https://tools.google.com/service/update2?cup2hreq=ae181407f447dfdbf701b7add225a95f0fd773dc882fc2b4099fbcfeeafbf8cd&cup2key=5:3781726665']
(The operation couldn’t be completed. Operation not permitted
[NSPOSIXErrorDomain:1])
Done checking for updates (errors=1).

Disabling the outbound firewall resolved the update issue.

My Mom was not happy.

[chro...@googlecode.com]

Comment #68 on issue 520135 by agafon...@gmail.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

I'm running into this issue on OS X (without firewalls) as well. The output
of the command above is:

/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/CheckForUpdatesNow.command
2016-01-01 22:50:07.215 GoogleSoftwareUpdateAgent[46553/0xb029b000] [lvl=3]
-[KSAgentApp(KeystoneThread) runKeystonesInThreadWithArg:] Failed to
connect to system engine.

[chro...@googlecode.com]

Comment #69 on issue 520135 by bor...@chromium.org: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

@ecksj: for the latest version, please look at the release calendar:
https://www.chromium.org/developers/calendar. If you scroll to the bottom
of the page ("OmahaProxy CSV Viewer") and check the stable version for mac,
you can see which build is the current one and when the distribution
started.
@agafonkin: The error you are experiencing is different - it appears that
the updater daemon is not properly installed. If you consistently see this
problem, then I would recommend reinstalling Keystone:
1. Manually download the latest version of Chrome and install it,
overriding the currently installed one.
2.Manually remove GoogleSoftwareUpdate.bundle - open "terminal" application
and execute:
sudo rm -rf /Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle
3. Relaunch Chrome. Chrome should display a yellow bar that warns about
updates not being setup properly and a button to fix it. Press this button
and supply credentials. This will reinstall Google Software Update,
hopefully fixing the problem
@wmangley3: yes, in your case it sounds like the firewall is blocking the
connection to Google Updater servers. However, the error in this case
("Operation not permitted") is different than the error the others
experienced. I would not recommend disabling the firewall, but rather
looking more closely at the firewall settings. I assume that you use the
standard OS X firewall, is this correct? If yes, I would recommend enabling
the setting "Automatically allow signed software to receive incoming
connections".
@diego.caravana: I will follow up separately, as it sounds like on your
machine the update checks succeed when you quit Chrome and run
CheckForUpdatesNow.command. This points to internal locking in the OS
management of network connections.

[chro...@googlecode.com]

Comment #70 on issue 520135 by agafon...@gmail.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

Thanks! I did just that a few days ago (removing software update,
installing Chrome again, launching and clicking on "set up auto updates"),
and it didn't fix the problem initially, but today I checked again and
miraculously the problem is gone. No idea why. :)

[chro...@googlecode.com]

Comment #71 on issue 520135 by ec...@cox.net: Update failed (error: 11) on
Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

Thanks Boris. So I did what you said, clicked on the release calendar
link, went to the stable mac version and saw that the current version
listed "Version 47.0.2526.106 (64-bit)" is the version that I have when I
click on "about google chrome." Below it is the same " Update failed
(error: 11)" message that I've always had. Again I'm OK with this as long
as I know I really have the current version listed, and that the "error
message" is an "error" itself and a "bug" that hasn't been fixed yet by
google for macs. Am I correct?? Thanks.

[chro...@googlecode.com]

Comment #72 on issue 520135 by timmisht...@gmail.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

This solved my problem
(src:https://support.google.com/chrome/answer/6315311?hl=en):
Open Finder.

At the top, select Go > Go to Folder.

Enter either of the locations below. If one doesn’t appear, try the other:
/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/

Double click "CheckForUpdatesNow.command".

In Terminal, wait for the message "[Process completed]"

Exit Terminal.
--------
After that I was able to update Chrome.

[chro...@googlecode.com]

Comment #73 on issue 520135 by ec...@cox.net: Update failed (error: 11) on
Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

Thanks timmisht. I've done that numerous times but as indicated in my
comment 71, the error message still appears even though the latest chrome
version is just above it. This makes me believe that the latest chrome
version updated successfully, and the error message is an "error" itself.

[chro...@googlecode.com]

Comment #74 on issue 520135 by bor...@chromium.org: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

Thank you, agafonkin. The problem that you showed above is sometimes
intermittent. E.g. if auto-updating is being performed at the same time and
it is taking longer, CheckForUpdatesNow.command will report that it cannot
connect to system engine. An example of "taking longer" is downloading
large update payload. CheckForUpdatesNow.command will have better error for
this case in the next released build.

ecksj, I am sorry that you still experience error 11. It is possible that
the problem is the network timeout error ("KSOutOfProcessFetcher timeout
while waiting for fetch."), which is typically intermittent. Would you be
able to run the updater diagnostics utility and send the generated .zip
file to bor...@chromium.org? Please note that the .zip file will contain
the user name with which you log on the machine (e.g. "johnsmith") and this
is why we do not want it to be attached in this public bug. Please send it
over only if you feel comfortable with disclosing this username with me.
Steps:
1. Open spotlight (typically by pressing Command-Space) and
type "terminal". Press enter once the Terminal application shows up in the
results.
2. In the terminal copy and paste the command below and press enter:

/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/ksdiagnostics
||
~/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/ksdiagnostics
3. Press enter. Supply credentials (username/password) for an admin, if
prompted.
4. After the process completes, it creates a .zip file and opens a Finder
window, selecting the file. Please send this file to bor...@chromium.org

[chro...@googlecode.com]

Comment #75 on issue 520135 by farsc...@gmail.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

I have been getting the same failed update error:11 for my Google Chrome
installation for a while and finally decided to fix it instead manually
reinstalling to get the latest version of chrome on my MAC. Anyway here is
the fix that I did instead of the above which looks like a lot of
diagnostics and commands.

*prerequisite you need to know how to use sudo (because the /Library/Google
folder is only accessable by the user and even admins will get permission
violations due to lack of rights).
To enable sudo for your standard user namedwhatever on your MAC in terminal
as an Admin
sudo visudo
enter YOUR admin password to get in.
use arrows to scroll to "# User privilege specification" section.
Put the cursor on the next empty line below the %admin entry and then press
the “A” key to insert text, then type the following on a new line,
replacing ‘namedwhatever’ with the users short name of the account you wish
to grant privilege to (hit tab between username and ALL):
namedwhatever ALL=(ALL) ALL
Now hit the “ESC” (escape) key to stop editing the file
Hit the : key (colon) and then type “wq” followed by the Return key to save
changes and exit vi
ESC type :wq to exit and save

THE FIX:
Now login as the user that is having the chrome trouble.
Close Chrome (if it is open)
Open terminal
sudo rm -r /Library/Google
enter YOUR PASSWORD to use sudo
sudo rm -r ~/Library/Google

Then open chrome and try the Chrome -> About Google Chrome

Chrome will recreate the /Library/Google folder and it should clear-up the
problem.

[chro...@googlecode.com]

Comment #76 on issue 520135 by bor...@google.com: Update failed (error: 11)

on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

Thank you, farschon. You end up reinstalling the updater (see comment #69
and my response to agafonkin). The approach indeed fixes the problem for
users with broken updater installation. However, this approach would not
restore updates for users who are experiencing the network timeout error in
the updater. The root cause of this error is in the Apple's higher level
network libraries (the issue impacts Safari and OS updates too) and the
problem is not restored by reinstalling.
That said, I am still curious why the updater was failing on your machine.
If you don't mind could you send your diagnostics data (see comment #74) to
bor...@chromium.org. Please note that your real machine userid will be in
the logs (e.g. "johnsmith"), so send it to me only if you are ok with
sharing this data to me. Please do not post the diagnistic logs in this
public forum.

[chro...@googlecode.com]

Updates:
Status: Untriaged

Comment #77 on issue 520135 by bor...@chromium.org: Update failed (error:

[chro...@googlecode.com]

Updates:
Owner: bor...@chromium.org

Comment #78 on issue 520135 by bor...@chromium.org: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

(No comment was entered for this change.)

[chro...@googlecode.com]

Comment #79 on issue 520135 by ashraful...@gmail.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

Thank you fraschon.. Your method worked perfectly .. Bravo !!

[chro...@googlecode.com]

Comment #80 on issue 520135 by nae...@gmail.com: Update failed (error: 11)

on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

Remove the /Library/Google folder works for me. Before the removal, I tried
command line

/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/MacOS/ksadmin
-S -l -P com.google.Chrome

which gives following errors:
KSLockFile unable to open() lock file.
[com.google.UpdateEngine.CommonErrorDomain:602
- '/Library/Google/GoogleSoftwareUpdate/TicketStore/Keystone.ticketstore.lock'
- 'KSLockFile.m:431'] (The operation couldn’t be completed. Permission
denied [NSPOSIXErrorDomain:13])
KSKeyedPersistentStore lock file error.
[com.google.UpdateEngine.CommonErrorDomain:502
- '/Library/Google/GoogleSoftwareUpdate/TicketStore/Keystone.ticketstore.lock'
- 'KSKeyedPersistentStore.m:329'] (KSLockFile unable to open() lock file.
- '/Library/Google/GoogleSoftwareUpdate/TicketStore/Keystone.ticketstore.lock'
[com.google.UpdateEngine.CommonErrorDomain:602])
KSPersistentTicketStore could not store ticket. (productID:
com.google.Chrome) [com.google.UpdateEngine.CoreErrorDomain:1051
- '/Library/Google/GoogleSoftwareUpdate/TicketStore/Keystone.ticketstore']
(KSKeyedPersistentStore lock file error.
- '/Library/Google/GoogleSoftwareUpdate/TicketStore/Keystone.ticketstore.lock'
[com.google.UpdateEngine.CommonErrorDomain:502])
KSOmahaServer cannot save the updated ticket: '<KSTicket:0x200f6b0
productID=com.google.Chrome
version=45.0.2454.93
xc=<KSPathExistenceChecker:0x21030b0 path=/Applications/Google Chrome.app>
serverType=Omaha
url=https://tools.google.com/service/update2
creationDate=2014-08-12 04:48:33
tagPath=/Applications/Google Chrome.app/Contents/Info.plist
tagKey=KSChannelID
brandPath=/Library/Google/Google Chrome Brand.plist
brandKey=KSBrandID
versionPath=/Applications/Google Chrome.app/Contents/Info.plist
versionKey=KSVersion
cohort=1:5m:1...@0.05
cohortName=Stable
> ' (productID: com.google.Chrome)
> [com.google.UpdateEngine.CoreErrorDomain:602
> - 'https://tools.google.com/service/update2'] (KSPersistentTicketStore
> could not store ticket.
> - '/Library/Google/GoogleSoftwareUpdate/TicketStore/Keystone.ticketstore'
> [com.google.UpdateEngine.CoreErrorDomain:1051])

Done checking for updates (errors=1).

Seems there are some issues
with '/Library/Google/GoogleSoftwareUpdate/TicketStore/Keystone.ticketstore'.

[chro...@googlecode.com]

Comment #81 on issue 520135 by pfeld...@chromium.org: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

@borisv: this happened to me again, on a brand new box now.

"/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/MacOS/ksadmin
-l"
was just hanging there forever for me, killing networkd helped again.

Do we know how big this is? Can we get this triaged and assigned even
though there is no actual work, but just investigation involved? My peers
also see this, but don't flag it since networkd workaround is an easy
workaround.

[chro...@googlecode.com]

Comment #82 on issue 520135 by bor...@chromium.org: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

@naecot: I am afraid that you were experiencing the symptoms of this bug:
https://code.google.com/p/chromium/issues/detail?id=568712. We fixed it a
few weeks ago, so my assumption is that your Google Software Update
installation was not self-updating. Do you mind sending me diagnostics data
to bor...@chromium.org, as per comment #74. As mentioned before, be aware
that the collected logs will contain your real username on the machine.
@pfeldman: we have an internal bug for the updater to implement a
workaround, which was previously reprioritized due to the workaround
available. Additionally, there was an early indication that Apple had fixed
the radar bug (the bug's state is 'escalated to engineering') in El
Capitan. Now we are aware that the problem is not fixed and we are seeing
more and more reports on it. We are actively investigating internally ways
to fix it this quarter.

[chro...@googlecode.com]

Comment #83 on issue 520135 by bor...@chromium.org: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

#82 bor...@chromium.org

@naecot: I am afraid that you were experiencing the symptoms of this bug:
https://code.google.com/p/chromium/issues/detail?id=568712. We fixed it a
few weeks ago, so my assumption is that your Google Software Update
installation was not self-updating. Do you mind sending me diagnostics data
to bor...@chromium.org, as per comment #74. As mentioned before, be aware
that the collected logs will contain your real username on the machine.

@pfeldman: we have an internal bug for the updater to implement automatic
workaround (use lower level APIs), which was previously reprioritized due
to the user workaround available. Additionally, there was an early
indication that Apple had fixed the radar bug in El Capitan. Now we are

aware that the problem is not fixed and we are seeing more and more reports

on it. We are actively investigating internally ways to implement such
workaround this quarter.

[chro...@googlecode.com]

Updates:
Status: Assigned

Comment #84 on issue 520135 by bor...@chromium.org: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

(No comment was entered for this change.)

[chro...@googlecode.com]

Comment #85 on issue 520135 by m.go...@gmail.com: Update failed (error: 11)

on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

I followed the workaround from
https://code.google.com/p/chromium/issues/detail?id=520135#c75, i.e. I
removed /Library/Google & ~/Library/Google & run Chrome again but the issue
has not been fixed; the update spins forever and in the end finishes with
the error 11.

BTW, I had it setup as a global update (the updater lied under
/Library/Google, not ~/Library/Google) but it recreated itself locally
(under ~/Library/Google) and no longer asks to make it global on the update
screen.

I don't have other internet problems, Safari loads pages correctly.

I'm on OS X 10.11.3 (15D21), the latest one.

Running:

~/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/MacOS/ksadmin
-l

finishes with an error:

KSOutOfProcessFetcher timeout while waiting for fetch.

[com.google.UpdateEngine.CommonErrorDomain:1502
- 'https://tools.google.com/service/update2?cup2hreq=04801b8c47cd614e0acb59e0b2f4547df71c064af9c02d92fb66b777afdf1edf&cup2key=5:1720181573'
- 'KSOutOfProcessFetcher.m:618']
KSServerUpdateRequest fetch failed. (productID: com.google.Keystone)
[com.google.UpdateEngine.CoreErrorDomain:702
- 'https://tools.google.com/service/update2?cup2hreq=04801b8c47cd614e0acb59e0b2f4547df71c064af9c02d92fb66b777afdf1edf&cup2key=5:1720181573']
(KSOutOfProcessFetcher timeout while waiting for fetch.
- 'https://tools.google.com/service/update2?cup2hreq=04801b8c47cd614e0acb59e0b2f4547df71c064af9c02d92fb66b777afdf1edf&cup2key=5:1720181573'
[com.google.UpdateEngine.CommonErrorDomain:1502])

Done checking for updates (errors=1).

What else can I do to fix it locally?

I've sent ksdiagnostics logs to bor...@chromium.org as described in comment
#74.

[chro...@googlecode.com]

Comment #86 on issue 520135 by m.go...@gmail.com: Update failed (error: 11)

on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

Even worse now, I wanted to see if re-downloading Chrome fixes anything but
the official Google sites still offers Chrome 47 instead of 48. So I'm on
an insecure & outdated Chrome version with no way to update.

This seems serious to me, any way to work around this problem?

[chro...@googlecode.com]

Comment #87 on issue 520135 by m.go...@gmail.com: Update failed (error: 11)

on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

Restarting the computer seems to help, at least temporarily, so I was able
to update. It will most likely come back, though as I've been experiencing
this bug for longer than the time from a previous computer reboot.

[chro...@googlecode.com]

Comment #88 on issue 520135 by boshulin...@gmail.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

how to solut it?

[chro...@googlecode.com]

Comment #89 on issue 520135 by bor...@chromium.org: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

@m.goleb: please try restarting of the network daemon:
1. Open the "Terminal" app
2. Copy and paste the command below and press enter. This will restart the
daemon:
sudo killall -9 networkd
3. Wait for 2-3 minutes and then try to check for updates in Chrome
4. If the updating still fails, close all Chrome tabs, quit Chrome (from
Chrome/Quit Google Chrome menu)
5. Wait for 2-3 minutes, re-launch Chrome and try update check again.

Unfortunately, comment #75 applies only to a small subclass of problems. I
looked at the diagnostic data that you kindly provided and all the errors I
see are network stack timeout issues. You may see my other comments in this
bug about the root cause. It is suspicious that Safari still loads pages in
your case, but I am still curious if restarting the network daemon works as
a temporary workaround.

[chro...@googlecode.com]

Comment #90 on issue 520135 by alessand...@gmail.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

Thank you so much for your suggestion, but I cannot I apply it because I
solved the problem yesterday after several attempts find on different
blogs.

[chro...@googlecode.com]

Comment #91 on issue 520135 by rahul.te...@gmail.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

I've started seeing this issue recently and definitely and issue.
Uninstalling and installing Chrome made me come back on v47. I'm on Mac...

[chro...@googlecode.com]

Comment #92 on issue 520135 by rahul.te...@gmail.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

sudo rm -r ~/Library/Google and then sudo rm -r ~/Library/Google resolved
the problem. Got the solution from other thread. Should help everyone,
seems some issue in Caches of Google, should be fixed by Google in longer
run. Above commands help in shorter run.

[chro...@googlecode.com]

Comment #93 on issue 520135 by tl...@fernandomiguel.net: Update failed

(error: 11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

I had Dev v.13 installed.
saw that .23 was available
when to check on updates, and got this error again. (i'm subbed here via a
duplicate issue).
closed chrome, run the manual cli upgrade without success. deleted the
mentioned library dirs, started chrome, checked for updates and still got
the error.
resorted to download chrome offline and manually upgrade chrome.

I would like to point out that this issue is hitting stable releases too,
and that will mean a considerable number of users will stop having the
latest security updates

[chro...@googlecode.com]

Comment #94 on issue 520135 by tl...@fernandomiguel.net: Update failed

(error: 11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

@m.go
Beta channel
https://www.google.com/chrome/browser/desktop/index.html?extra=betachannel&standalone=1
Dev channel
https://www.google.com/chrome/browser/desktop/index.html?extra=devchannel&standalone=1

[chro...@googlecode.com]

Comment #95 on issue 520135 by modernit...@gmail.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

#72 timmisht...@gmail.com

Thanks, timmisht...@gmail.com. Your method solved my problem.

---

This solved my problem
(src:https://support.google.com/chrome/answer/6315311?hl=en):
Open Finder.

At the top, select Go > Go to Folder.

Enter either of the locations below. If one doesn’t appear, try the other:
/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/

Double click "CheckForUpdatesNow.command".

In Terminal, wait for the message "[Process completed]"

Exit Terminal.

[chro...@googlecode.com]

Comment #97 on issue 520135 by tl...@fernandomiguel.net: Update failed

(error: 11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

I also have little snitch, but it's not showing any outbound block.
I'll will set to open and retest

[chro...@googlecode.com]

Comment #98 on issue 520135 by warwi...@gmail.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

#72 fixed my problem running Mac on 10.11.3

[chro...@googlecode.com]

Comment #99 on issue 520135 by ju.blanc...@gmail.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

#72 fixed my problem too on Mac 10.11.3 !

[chro...@googlecode.com]

Comment #100 on issue 520135 by leo...@gmail.com: Update failed (error: 11)

on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

It tooks very long time to find out solution.
But simple and clear instruction by #72 cleaned up my problem.
Thanks. (10.11.3).

[chro...@googlecode.com]

Comment #105 on issue 520135 by 9231...@gmail.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

I've been struggling with this error for it seems like years.
100s and 100s of other apps update with no problems.

I've read this entire thread and tried all sorts of solutions to no avail.

Why does Chrome present such issues?

[chro...@googlecode.com]

Comment #106 on issue 520135 by tl...@fernandomiguel.net: Update failed

(error: 11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

all i know is that i keep to have to do updates by hand, downloading the
latest version, closing chrome, updating.
really poor process and makes me run unsecure versions for weeks, till i
notice there are newer versions

/Users/Fernando/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/CheckForUpdatesNow.command ;
exit;
2016-02-04 15:33:47.483 GoogleSoftwareUpdateAgent[27758/0xb031d000] [lvl=3]
-[KSAgentApp(KeystoneThread) runKeystonesInThreadWithArg:] Caught exception
checking for updates name=NSPortTimeoutException, reason=Distributed
objects message send timed out (timeout: 476292827.478204 at time:
476292827.483353) 1, userinfo=(null)

[chro...@googlecode.com]

Comment #107 on issue 520135 by m.go...@gmail.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

Re #89: I've tried the following:
1. Close all Chromes (stable & Canary).
2. `sudo killall -9 networkd` in the terminal
3. Open Chromes again after ~15 minutes.
4. Go to chrome://chrome in both of them.

It still spins forever in both Chromes. So this workaround doesn't work for
me.

I think last time a full reboot of the computer helped. It seems I'll have
to do that for the time being to be able to stay on current Chromes...

Note that Chrome is literally the only browser that has this problem for
me. I've tried Firefox (stable, Beta, Developer Edition & Nightly), WebKit
nightly, Opera Beta & Developer, Yandex.Browser & Vivaldi; all update
without any problem.

[chro...@googlecode.com]

Comment #108 on issue 520135 by m.go...@gmail.com: Update failed (error:

11) on Mac Chrome
https://code.google.com/p/chromium/issues/detail?id=520135

I have an impression this usually starts happening when I'm at work. We
have a custom VPN which may theoretically break some things (although all
other apps/browsers update fine). But sometimes I can update even at work,
especially shortly after arriving at it and only if it worked at home
before. The main problem is that when I return home, it doesn't fix itself;
once the problem happens once, only a reboot fixes it. One bad network
shouldn't influence future behavior.