Chrome is unable to self-update
Reported by
d...@phobos.io,
Mar 9 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36 Steps to reproduce the problem: 1. Install little snitch 2. Attempt to upgrade chrome 3. Tell little snitch to permit ksfetch and nsurlsesiond when they try to fetch the update 4. observe this error text: 2017-03-08 17:28:28.174 GoogleSoftwareUpdateAgent[19057/0xb0280000] [lvl=3] -[KSAgentApp(KeystoneThread) runKeystonesInThreadWithArg:] Failed to connect to system update engine from the system agent. 2017-03-08 17:28:28.176 GoogleSoftwareUpdateAgent[19057/0xb0280000] [lvl=3] -[KSUpdateEngine updateProductID:] KSUpdateEngine no ticket to update for the specified product ID. (productID: com.google.Chrome) [com.google.UpdateEngine.CoreErrorDomain:3003] 5. completely disable little snitch by shutting off the network filter 6. attempt to update chrome again 7. observe exact same error messages 8. attempt to reset my profile by following these steps: https://productforums.google.com/forum/#!topic/chrome/fcrGMglbxDE 9. observe exact same error messages. What is the expected behavior? Chrome should successfully connect to the update server, and pull the update down What went wrong? Chrome is unable to self-update Did this work before? N/A Chrome version: 55.0.2883.95 Channel: n/a OS Version: OS X 10.12.3 Flash Version: Shockwave Flash 24.0 r0 From what I can tell, Chrome used to use curl to do it's updating on OSX, and now it seems to use ksfetch and nsurlsessiond. This makes troubleshooting the process murky, as with curl you can simply "manually recreate the request attempt by hand", and with nsurlsessiond it would appear that chrome is "handing off to the operating system the request to go get the update". This seems to make it harder to troubleshoot.
,
Mar 13 2017
The error looks more like an issue with the updater's ticket for Chrome, rather than anything to do with the network.
,
Mar 13 2017
Yes, the problem is with the updater. The system updater is not present or in bad shape. To fix the problem, please download and reinstall the updater from here: https://dl.google.com/mac/install/googlesoftwareupdate.dmg Please, let me know if this fixes the issue. In the meanwhile, we are doing the following: 1. Future versions of Chrome will detect the problem and attempt to install user updater (needs new Chrome, though) 2. Next version of the updater provides a better error message with instructions to downloading it again. Again, requires new updater... 3. We are updating this help article accordingly: https://support.google.com/chrome/answer/111996?hl=en
,
Mar 13 2017
I've installed the google software updater, and will report in again if chrome continues to not have the ability to self update. I've been manually downloading the new versions of chrome in whole from google.com/chrome.
,
Mar 13 2017
I am sorry about that, Dan. For some reason the daemon for the updater was stopped on the machine. Do you recall when updates stopped working? Does the time correlate with the Little Snitch or other software installation?
,
Mar 13 2017
It's been in this state for months. If the cause for the problem is that there was a daemon not running properly, it's plausible it wasn't little snitch? Unless little snitch causing networking interruptions for the updater software caused the updater software to "stop trying for some reason" - maybe a crash or a lockfile problem. I'm just spitballing. I honestly can't remember.
,
Mar 13 2017
No worries. The firewall part of Little Snitch is unlikely to cause it, indeed. More likely root causes are A/V software 'cleaning' the machine or system/user restore that doesn't restore all files. It could also be a rare bug in our software. The issue is very hard for us investigate, as we see it only after it happened. Typically months later.
,
Mar 13 2017
It is plausible in that case, that this was because of a restore of some kind, because of a botched backup well over a year ago where the restore was done via rsync/ssh instead of using apples restore tools. Fun fact: sometimes filefault just "doesn't work", despite having the password. It just "wont decrypt". Thanks apple.
,
Mar 14 2017
,
Aug 9 2017
Dan, I am sorry to bother you, do you have updates working regularly now after re-installing the updater? If not, your case may be similar to another one that I just finished investigating. See the solution here: https://bugs.chromium.org/p/chromium/issues/detail?id=752353#c9
,
Aug 9 2017
The problem has been resolved on my end. I re-installed the chrome installer software per the recommendation and the problem went away.
,
Aug 9 2017
Perfect! Thanks, Dan. |
|||
►
Sign in to add a comment |
|||
Comment 1 by nyerramilli@chromium.org
, Mar 9 2017Labels: Needs-Milestone